projects / people / ms / u-boot.git / blame
| Commit | Line | Data |
|---|---|---|
| 60fbe254 WD |
1 | Installation Instructions: |
| 2 | -------------------------- | |
| 3 | ||
| 4 | 1. Put the s2 switch into the following position: | |
| 5 | ||
| 6 | 1 0 | |
| 7 | ------ | |
| 8 | |x | | |
| 9 | | x| | |
| 10 | |x | | |
| 11 | | X| | |
| 12 | ------ | |
| 13 | ||
| 14 | 2. Connect to the serial console and to the BDI. Power on. On the | |
| 15 | serial line, you should see: | |
| 16 | ||
| 17 | PURPLE@1.2> | |
| 18 | ||
| 19 | 3. Type '8'. No echo will be displayed. In response, you should get: | |
| 20 | ||
| 21 | 7A(pass) | |
| 22 | ||
| 23 | 4. From BDI, enter command: | |
| 24 | ||
| 25 | mmw 0xb800d860 0x0042c7ff | |
| 26 | ||
| 27 | 5. Then, from BDI: | |
| 28 | ||
| 29 | erase 0xB0000000 | |
| 30 | erase 0xB0008000 | |
| 31 | erase 0xB000C000 | |
| 32 | erase 0xB0010000 | |
| 33 | erase 0xB0020000 | |
| 34 | ||
| 35 | prog 0xB0000000 <u-boot.bin> bin | |
| 36 | ||
| 37 | 6. Power off. Restore the original S2 switch position. Power on. | |
| 38 | U-Boot should come up. | |
| 39 | ||
| 40 | ||
| 41 | ||
| 42 | Implementation Notes: | |
| 43 | --------------------- | |
| 44 | ||
| 45 | Due to the RAM/flash bus arbitration problem the suggested workaround | |
| 46 | had to be implemented. It works okay. On the downside is that you | |
| 47 | can't really check whether 'erase' is complete by polling flash as it | |
| 48 | is usually done. Instead, the flash driver simply waits for a given | |
| 49 | time and assumes that erase then has passed. This behaviour is | |
| 50 | identical to what the VxWorks driver does; also, the same timeout (6 | |
| 51 | seconds) was chosen. Note that this timeout applies for each errase | |
| 52 | operation, i. e. per erased sector. |