I see on the recent test images[1] that u-boot and MLO are handled differently than before[2]. You copy u-boot.img and MLO using:
dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k I want to try my own u-boot, but before overwriting working copy I'd like to back it up. Does this work? bone$ *dd if=/dev/mmcblk1boot1 of=u-boot.img.bak count=2 seek=1 bs=384k* bone$ *dd if=/dev/mmcblk1boot0 of=MLO.bak count=1 seek=1 bs=128k* When updating u-boot, do I also need to update MLO? Can I update a running Bone with? dd if=MLO of=/dev/*mmcblk1boot0* count=1 seek=1 conv=notrunc bs=128k dd if=u-boot.img of=/dev/*mmcblk1boot1* count=2 seek=1 conv=notrunc bs=384k Thanks... --Mark [1] http://rcn-ee.net/deb/testing/ [2] http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0#Boot_Partition_.28omap4.2B_.28am335x.29.29 -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
