Hello, On 1/16/20 4:09 PM, Hans-Ulrich Schlieben wrote: > Hi Ahmad, > > Thanks to your Mail I tested with barebox_2017.12.0-phy6.bb (thud used barebox_2017.12.0-phy4.bb) and this works in zeus too. > >> According to the state command output under thud, your state is stored on the EEPROM, not the NAND. Look for update-eeprom in your device tree. >> There should also be an /dev/eeprom0.update-eeprom in barebox. > That seems right, when working the eeprom is written to on each boot. > But I could not find any references to *eep* inside barebox in any layer. Does it come from the phytec git directly? Upstream barebox has this: https://git.pengutronix.de/cgit/barebox/tree/arch/arm/dts/imx6qdl-phytec-state.dtsi?h=next I would imagine, yours does to. You can check in the yocto build directory. (If you have rm_work enabled, you might need RM_WORK_EXCLUDE += "your-barebox-recipe" in your local.conf) Also try of_dump /state inside of barebox to see the device tree node. The reason, you haven't found it in the deploy/ device tree is that barebox modifies the kernel device tree on loading and adds the state nodes to it. >> if not, try executing the drvinfo command and see if the driver has probed the EEPROM. >>>> Looks like the state node is missing in your device tree. Do you have the state driver enabled? drvinfo should tell you that. 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
