On Wed, Nov 13, 2013 at 12:11:04AM +0100, Rostislav Lisovy wrote: > One small issue I am facing: > The board has a jumper to switch between 'internal boot' and 'serial > boot'. If I set it to 'serial boot' and then use imx-usb-loader to load > barebox to RAM, everything works just fine. When I then try to flash it > (flash controller support is missing in this patch-set), flashing is > successful, however I am not able to boot it later when switched to > 'internal boot' mode. If I try to flash some old version of the barebox > (from my version running in RAM -- thus the problem is probably not in > the flash support), it not only flashes successfully, this older version > is even able to boot in the 'internal boot' mode. > > I also noticed that when I am using CONFIG_IMX_MULTI_BOARDS the whole > set of CONFIG_ARCH_IMX_INTERNAL_BOOT_* disappears. > > Commands I am using to flash barebox: > erase /dev/nand0 > addpart /dev/nand0 512k(barebox)ro,512k(bareboxenv),4M(kernel),-(rootfs) > nand -a /dev/nand0.* > erase /dev/nand0.barebox.bb > tftp /vmx53/barebox.bin /dev/nand0.barebox.bb You should use the barebox_update infrastructure. See imx53_bbu_internal_nand_register_handler(). With this you would exeute on the commandline: barebox_update /path/to/barebox.bin As a bonus this command also creates a bad block table the imx53 ROM is able to read. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 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
