Hello,
On 1/16/20 4:13 PM, Hans-Ulrich Schlieben wrote:
> Hi Enrico,
>
> thank you for your help and for telling me about fdtdump. Works great.
> I could not find any references to state in the device tree.
> There where no references to state and bootchooser in the devicetree.
> The only references to barebox are two addresses inside the nand:
> gpmi-nand@00112000 {
> ...
> partition@0 {
> label = "barebox";
> reg = <0x00000000 0x00400000>;
> };
> partition@1 {
> label = "barebox-environment";
> reg = <0x00400000 0x00100000>;
> };
> ...
> And there is a eeprom entry:
> i2c@021a8000 {
> ...
> eeprom@50 {
> compatible = "atmel,24c32";
> reg = <0x00000050>;
> };
> Where to look for state in the devicetree?
As mentioned in the other mail, it's in the barebox device tree
and on Linux boot fixed up into the Linux device tree.
> Anyhow I compiled a zeus image using the old barebox version 2017.12.0 and bootchooser works again with zeus.
> Interesting is that ubi fails too like in thud. So it seems as long as ubi fails state could be used or the other way around.
I don't think they are related.
It would be best if you can try to reproduce this issue with upstream barebox.
To do so without yocto:
git clone https://git.pengutronix.de/git/barebox
cd barebox
cp $your_barebox_config_in_yocto .config
make -j$(nproc) CROSS_COMPILE=/path/to/your/yocto/toolchain/bin/arm-$your_vendor-linux-gnueabihf- ARCH=arm
under images/ you will have the barebox images. You can get that onto your
device using a SD-Card, imx-usb-loader, tftp ... etc.
If you want to do it in Yocto, there are meta-ptx and meta-barebox that have
more recent barebox versions.
Cheers
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
