RaspberryPi 1/2(/3)

RaspberryPi 1/2(/3)

[Pascal Vizeli]

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?

Thanks for any support and hint what my brain do wrongly :)
Pascal

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: RaspberryPi 1/2(/3)

[Roland Hieber]

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

Fwd: RaspberryPi 1/2(/3)

[Pascal Vizeli]

Hi Roland

Roland Hieber <r.hieber@pengutronix.de> schrieb am Di., 22. Mai 2018, 10:16:
>
>
> 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...

I use the latest one. I was not sure if the 20170129 is workable on a RPi3+

Anyway I try this version to release a beta, if they will work.

>
> 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.

Perfect. I will debug it on new Firmware and maybe I can fix this and
make it runable on a RPi3+ too. They use same kind of CPU but need a
other DTS.

I'm happy if I can help on this amazing project.

Best regards
Pascal

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: RaspberryPi 1/2(/3)

[Pascal Vizeli]

2018-05-22 10:16 GMT+02:00 Roland Hieber <r.hieber@pengutronix.de>:
> 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...

1.20171029 Firmware don't work why my barebox config and the origin
rpi_defconfig. Same effect.
I try now the debug modus to find out where are the problem.

Greets
Pascal

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: RaspberryPi 1/2(/3)

[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
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

Re: RaspberryPi 1/2(/3)

[Oleksij Rempel]

[-- 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

Re: RaspberryPi 1/2(/3)

[Pascal Vizeli]

It is the normal default DTS from barebox/linux. I output a 'of_dump':
https://hastebin.com/zanogazonu.xml

greets
Pascal

2018-05-22 20:24 GMT+02:00 Oleksij Rempel <linux@rempel-privat.de>:
> 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
>

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: RaspberryPi 1/2(/3)

[Roland Hieber]

On Tue, May 22, 2018 at 07:38:52PM +0200, Pascal Vizeli wrote:
> With debug modus it works perfect :) Look like the Serial console is
> not exists (PL011).
> Is that a problem with changed/updated DTS files?

If this is still relevant, you could try fiddling a bit with the UART
options [1] in /boot/config.txt of the RPi firmware (e.g. enable_uart
and dtoverlay=pi3-miniuart-bt). AFAIR the firmware itself sets up the
chip with its own device tree and applies device tree overlays. But this
is only necessary for RPi 2+, iirc.

[1]: https://www.raspberrypi.org/documentation/configuration/uart.md

 - 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