Difference between revisions of "BootStrap"
(→Instructions to use the Armadeus UbootRecover utility) |
m (→Introduction) |
||
| Line 3: | Line 3: | ||
===Introduction=== | ===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. | + | 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 2 packages Python and pyserial installed on your PC. |
<br> | <br> | ||
This utility communicates with the i.MX processor while in ''bootstrap mode'' (See i.MX reference manual for more informations). | This utility communicates with the i.MX processor while in ''bootstrap mode'' (See i.MX reference manual for more informations). | ||
Revision as of 16:05, 29 December 2008
Contents
Instructions to use the Armadeus U-Boot recovering utility
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 2 packages Python and pyserial installed on your PC.
This utility communicates with the i.MX processor while in bootstrap mode (See i.MX reference manual for more informations).
To enter the bootstrap mode, you have to put the bootstrap jumper and reset your Armadeus board:
Launch
Go inside the uboot_recover folder (software/uboot_recover/) and launch
$ python uboot_recover.py
- The tool will ask you to specify the serial port on which the board is connected. Under Linux please use /dev/ttySx and under Windows use COMx
- Then the size of the SDRAM has to be indicated. Default value is 16Mo.
- The tool will then try to synchronize with the i.MX:
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 !
When you see that message reset your board.
If nothing happens, verify your bootstrap jumper is put and try to reset your board. At last, check your serial port device is the right one and don't forget to quit all kermit/minicom instances before launching uboot_recover tool !
- 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 responds by 'y'
The following messages are then displayed:
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 !
