Changes

How to recover a IGEP bricked board

173 bytes added, 17:15, 10 February 2012

no edit summary

#REDIRECT [[Update the PRE-INSTALLED software image to a current release]]

 

= How to recover a bricked IGEPv2 board =

4) Copy the file '''x-load-bin.ift''' (make sure it's the one from the sdcard directory) to a file named '''MLO''' in the root directory of the card. Then copy the files '''x-load-ddp.bin.ift''' and '''u-boot.bin''' also to the root dir.

== First boot == 5) Simply put the card in and start your board. If everything goes well, you should see X-Loader loading u-boot and the usual "Press a key to stop autoboot". Stop the autoboot process and now you need to flash your firmware.

65) The following commands will flash Simply put the new XLoader card in and start your board. If everything goes well, you should see X-Loader loading u-boot (that you put in and the SD card) according usual "Press a key to the latest MTD partitionsstop autoboot". Note that you might need to use different MTD partitions, in which case Stop the size autoboot process and offset arguments of the 'erase' and 'write' commands below now you need to be adjusted (see the u-boot manual for 'onenand erase' and 'onenand write' command syntax)flash your firmware.

mmcinit6) The following commands will flash the new XLoader and u-boot (that you put in the SD card) according to the latest MTD partitions. Note that you might need to use different MTD partitions, in which case the size and offset arguments of the 'erase' and 'write' commands below need to be adjusted (see the u-boot manual for 'onenand erase' and 'onenand write' command syntax). <pre> mmc init

fatload mmc 0 0x80300000 x-load-ddp.bin.ift

onenand ecc hw

onenand erase 0 0x80000

onenand write 0x80300000 0 0x80000

onenand erase 0x80000 0x180000

onenand write 0x80300000 0x80000 0x180000

</pre>

7) Remove the SD card and power cycle the board. XLoader and u-boot should start. If you got lucky, your old environment might still be there. Use printenv to see what's left of it. If not, then you'll need to restore your old environment. The easiest way is to simply type the whole thing back and use saveenv.

 

8) Once your environment is restored, try to boot. If the kernel doesn't boot, you need to reflash it, but at least your board is back to life now.

 

== See also ==

*[[Frequently_Asked_Questions_and_Their_Answers#Boot_up_sequence|Boot up sequence]]

7) Remove the SD card and power cycle the board. XLoader and u-boot should start. If you got lucky, your old environment might still be there. Use printenv to see what's left of it. If not, then you'll need to restore your old environment. The easiest way is to simply type the whole thing back and use saveenv.

8) Once your environment is restored, try to boot. If the kernel doesn't boot, you need to reflash it, but at least your board is back to life now.

[[Category:How to forgeRemove]]

• ← Older edit

0

edits