From: Bob C. <bco...@ve...> - 2011-03-05 20:53:30
|
Just take this: MLO-overo-1.44+r19+gitr6f3a26101303051e0f91b6213735b68ce804e94e-r19 and rename it MLO like so: mv MLO-overo-1.44+r19+gitr6f3a26101303051e0f91b6213735b68ce804e94e-r19 MLO Pay careful attention to what Steve advises, because he is the one who rescued me. Bob Cochran On 03/05/2011 03:01 PM, dtran11 wrote: > There are several versions of MLO/x-loader, which one do I use to flash on > the nand? > > > MLO-overo-1.44+r19+gitr6f3a26101303051e0f91b6213735b68ce804e94e-r19 > x-load-overo-1.44+r19+gitr6f3a26101303051e0f91b6213735b68ce804e94e-r19.bin.ift > x-load-usb-overo-1.44+r19+gitr6f3a26101303051e0f91b6213735b68ce804e94e-r19.bin > > Thanks > > > sakoman wrote: >> On Mon, Dec 27, 2010 at 5:18 PM, Bob Cochran<bco...@ve...> >> wrote: >>> A short time ago, I managed to brick my Overo's NAND in an attempt to >>> update it with the latest X-loader. Ash responded to one of my posts >>> that the Overo should simply boot from the SD card, but that was not my >>> experience. However I had to stop my troubleshooting efforts for a few >>> days. >>> >>> Tonight, I came back to this problem. What I did was, I re-formatted the >>> first partition on my SD card following the standard advice for >>> populating an Overo SD card. I also added a console rootfs on the SD >>> card's second partition. >>> >>> Then I created a script copied from this web page: >>> >>> http://overoinfo.blogspot.com/ >>> >>> and noticed it was not updating the x-loader, so I decided to do that as >>> the first script action with this logic which I basically copied and >>> modified from the script provided: >>> >>> ---------------------------------------------------------------------------------------------------------------------- >>> >>> # reload the x-loader >>> >>> if [ -e $xload ]; then >>> echo "Erasing x-loader partition ..." >>> flash_eraseall /dev/mtd0 >>> echo "Writing x-loader to NAND ..." >>> nandwrite -p /dev/mtd0 $xload >>> echo "x-loader image has been written to NAND ..." >>> else >>> echo "ERROR: couldn't find x-loader binary" >>> fi >>> ---------------------------------------------------------------------------------------------------------------------- >>> >>> The Overo did indeed boot from the SD card! I was really pleased to see >>> that, my first sign of hope with this. Then I ran the script, and the >>> x-loader update part failed with these results: >>> >>> -------------------------------------------------------------------------------------------- >>> root@overo:~/images# ./nand_update.sh >>> Erasing x-loader partition ... >>> flash_eraseall: /dev/mtd0: Permission denied >>> Writing x-loader to NAND ... >>> /dev/mtd0: Permission denied >>> ... >>> ... >>> -------------------------------------------------------------------------------------------- >>> All the other sections of the script appear to have worked fine, though. >>> >>> My question is: Why did the above error happen? And how do I fix the >>> error and update x-loader? >> The x-load partition (mtd0) is write protected in linux, so you will >> have to update the x-load partition using u-boot. >> >> There actually is a good reason for this: the x-load partition must be >> written using hw ecc, and linux currently uses sw ecc. Thus if the >> partition were to be written by linux, the OMAP boot rom would see ecc >> errors and could not boot. >> >> Writing a new x-load is pretty simple once you can boot from an SD >> card, so you ar 90% of the way there! >> >> Just break into u-boot by pressing a key during the boot sequence, the >> issue the following u-boot commands: >> >> mmc init >> fatload mmc 0 $loadaddr MLO >> nandecc hw >> nand erase 0 80000 >> nand write $loadaddr 0 20000 >> nand write $loadaddr 20000 20000 >> nand write $loadaddr 40000 20000 >> nand write $loadaddr 60000 20000 >> reset >> >> The above prccess writes 4 copies of x-load in case errors develop in >> those initial nand blocks. >> >> (I typed this from memory, so hopefully there aren't too many typos!) >> >> Steve >> >> ------------------------------------------------------------------------------ >> Learn how Oracle Real Application Clusters (RAC) One Node allows customers >> to consolidate database storage, standardize their database environment, >> and, >> should the need arise, upgrade to a full multi-node Oracle RAC database >> without downtime or disruption >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> |