From: Oleksij Rempel <linux@rempel-privat.de>
To: Pascal Vizeli <pascal.vizeli@syshack.ch>,
Roland Hieber <r.hieber@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: RaspberryPi 1/2(/3)
Date: Tue, 22 May 2018 20:24:15 +0200 [thread overview]
Message-ID: <fa2ffd7d-d8f6-260c-5176-c4dfc33161b1@rempel-privat.de> (raw)
In-Reply-To: <CACvFaDe8CAyQyJwSfu3AUcZhqi3PKmsBBcvMna705xMw4nJGUA@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2885 bytes --]
Am 22.05.2018 um 19:38 schrieb Pascal Vizeli:
> With debug modus it works perfect :) Look like the Serial console is
> not exists (PL011).
> Is that a problem with changed/updated DTS files?
>
> =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.05.22 19:33:41 =~=~=~=~=~=~=~=~=~=~=~=
> uart-pl011 3f201000.serial: probe failed: No such file or directory
this uart driver would exit in two cases:
1. regulator is present, but can't enable it
2. no clock is provided.
I assume we have here a second case.
Is it not define in devicetree?
> bcm2835-gpio 3f200000.gpio: probed gpiochip-1 with base 0
> malloc space: 0x1f9fcdc0 -> 0x1fdfcdbf (size 4 MiB)
> no /dev/disk0.0. using default env
> environment load /dev/env0: No such file or directory
> Maybe you have to create the partition.
> running /env/bin/init...
> - Hit m for menu or wait for autoboot -
> bootchooser: Cannot get state 'state'
> Nothing bootable found on 'bootchooser'
> Nothing bootable found
> HassOS boot Menu: 1: Autoboot 2: Boot System 0 3: Boot
> System 1 4: Shell
>
> 2018-05-22 10:16 GMT+02:00 Roland Hieber <r.hieber@pengutronix.de>:
>> On Mon, May 21, 2018 at 05:51:33PM +0200, Pascal Vizeli wrote:
>>> Hi,
>>>
>>> I try to build a bootable barebox for raspberry with 2018.05.00 and buildroot:
>>> https://github.com/home-assistant/hassos/tree/dev/buildroot-external
>>>
>>> I build the origin rpi_defconfig but I'm was not able to boot the
>>> 'barebox.bin' and become a output on UART. I can boot the linux kernel
>>> from rpi loader. If I try the barebox, it will be flash the green
>>> light and if I disable the LED support, only the red power light is
>>> seen.
>>>
>>> I try also the RPi3 patches and end in same result.
>>> I follow also this guide:
>>> https://www.barebox.org/doc/latest/boards/bcm2835.html
>>>
>>> Have anyone a idea what will be the problem or what I doing wrong?
>>
>> Which version of the RPi firmware are you using? I wrote that section
>> while using the git tag 1.20171029, maybe they changed something
>> again...
>>
>> What you can try to do is enable "low level debug messages" make
>> menuconfig under "Debugging", and try to set the log level to something
>> higher and see if you get any output. I think you also need to set
>> "System Type" -> "Lowlevel debug UART" to the model you're using.
>>
>> - Roland
>>
>> --
>> Roland Hieber | r.hieber@pengutronix.de |
>> Pengutronix e.K. | https://www.pengutronix.de/ |
>> Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
>> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Regards,
Oleksij
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-05-22 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 15:51 Pascal Vizeli
2018-05-22 8:16 ` Roland Hieber
[not found] ` <CACvFaDfa+Od__ZcB=hcFBzJ3eqRv1ZAnwG4-EjVGHsaq3zmnEw@mail.gmail.com>
2018-05-22 13:29 ` Fwd: " Pascal Vizeli
2018-05-22 14:25 ` Pascal Vizeli
2018-05-22 17:38 ` Pascal Vizeli
2018-05-22 18:24 ` Oleksij Rempel [this message]
2018-05-22 19:50 ` Pascal Vizeli
2018-06-04 13:28 ` Roland Hieber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa2ffd7d-d8f6-260c-5176-c4dfc33161b1@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=barebox@lists.infradead.org \
--cc=pascal.vizeli@syshack.ch \
--cc=r.hieber@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox