Difference between revisions of "BootStrap"
From ArmadeusWiki
m |
(Re-org) |
||
Line 43: | Line 43: | ||
*Then you can specify whether the environment variables (IP, your special scripts...) have to be erased or not. If your board does not start anymore after a first uboot_recover, please respond 'y'. | *Then you can specify whether the environment variables (IP, your special scripts...) have to be erased or not. If your board does not start anymore after a first uboot_recover, please respond 'y'. | ||
− | *The following messages are then displayed | + | *The following messages are then displayed: |
− | <pre class="host"> | + | {| border="1" cellpadding="5" cellspacing="0" summary="Recovery final messages" |
+ | |- style="background:#efefef;" | ||
+ | ! '''APF9328''' || '''APF27''' || '''APF51''' || '''APF28''' | ||
+ | |---------------- | ||
+ | ||<pre class="host"> | ||
loading file ramprogrammer.bin. Please wait... | loading file ramprogrammer.bin. Please wait... | ||
284 octets | 284 octets | ||
Line 56: | Line 60: | ||
</pre> | </pre> | ||
− | + | ||<pre class="host"> | |
− | <pre class="host"> | + | |
run flash_uboot | run flash_uboot | ||
device 0 offset 0x0, size 0xa0000 | device 0 offset 0x0, size 0xa0000 | ||
Line 75: | Line 78: | ||
BIOS>uBoot successfully recovered ! | BIOS>uBoot successfully recovered ! | ||
</pre> | </pre> | ||
+ | || | ||
+ | |||
+ | || | ||
+ | |---------------- | ||
+ | |} | ||
+ | |||
+ | |||
+ | {{Note|If all went fine, don't forget to remove the bootstrap jumper if you want to restart the board in its normal boot state}} | ||
==Links== | ==Links== | ||
* http://www.armadeus.com | * http://www.armadeus.com |
Revision as of 18:59, 24 May 2012
Instructions to use the Armadeus U-Boot recovery utility.
If you think you bricked your board by flashing a bad bootloader, don't worry: there is a solution to recover it, without a JTAG probe. Indeed i.MX controllers have an internal "bootstrap" mode that allow them to communicate through RS232 or USB just after the reset.
Introduction
- The uboot_recover tool is a Python piece of code that allows you to automatically install a new U-Boot from scratch or to recover it in case of failure. uboot_recover requires the python and pyserial packages to be installed on your PC:
$ sudo apt-get install python-serial python-usb
This utility communicates with the i.MX(L/27/28/51) processor while in bootstrap mode (See i.MX(L/27/28/51) Reference Manual for more informations).
- To enter the bootstrap mode, you have to put the bootstrap jumper and reset your Armadeus board:
Usage
- Quit all Kermit/Minicom/GTKTerm/Hyperterminal sessions connected to the board through Serial Port.
- Go inside the software/uboot_recover/ directory and launch (sudo usage is only required on APF28 & APF51):
$ sudo python apfXX_recover.py (XX depends on the version of your board (ie: 9328, 27, 28 or 51))
- The tool will ask you to specify the serial port on which the board is connected. Under Linux please use /dev/ttySx or /dev/ttyUSBx and under Window$ use COMx.
- Then the size of the SDRAM has to be indicated. Default value is 16Mo for the APF9328 and 64Mo for the APF27. Not required on APF51.
- The tool will then try to synchronize with the i.MX (on APF9328 only). When you see that message, reset your board:
Re-synchronizing... Please reset your board in bootstrap mode ! Please reset your board in bootstrap mode ! Please reset your board in bootstrap mode ! Please reset your board in bootstrap mode !
- Then you can specify whether the environment variables (IP, your special scripts...) have to be erased or not. If your board does not start anymore after a first uboot_recover, please respond 'y'.
- The following messages are then displayed:
APF9328 | APF27 | APF51 | APF28 |
---|---|---|---|
loading file ramprogrammer.bin. Please wait... 284 octets Loading file u-boot.bin. Please wait... 150304 octets loading file flashprogrammer.bin. Please wait... 668 octets Flashing please wait... . uBoot successfully recovered ! |
run flash_uboot device 0 offset 0x0, size 0xa0000 nand_unlock: start: 00000000, length: 655360! NAND flash successfully unlocked NAND erase: device 0 offset 0x0, size 0xa0000 OK NAND write: device 0 offset 0x0, size 0xa0000 655360 bytes written: OK NAND flash successfully locked device 0 offset 0xa0000, size 0x7f60000 nand_unlock: start: 000a0000, length: 133562368! NAND flash successfully unlocked Flashing of uboot succeed BIOS>uBoot successfully recovered ! |
Note: If all went fine, don't forget to remove the bootstrap jumper if you want to restart the board in its normal boot state |