| wdenk | a6db71d | 2003-04-08 23:25:21 +0000 | [diff] [blame] | 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 | |
| wdenk | 57c58b4 | 2003-05-12 09:51:00 +0000 | [diff] [blame^] | 14 | Put the s3 switch into the following position: |
| 15 | |
| 16 | 1 0 |
| 17 | ------ |
| 18 | |x | |
| 19 | |x | |
| 20 | |x | |
| 21 | |x | |
| 22 | |x | |
| 23 | | x| |
| 24 | | x| |
| 25 | |x | |
| 26 | ------ |
| 27 | |
| wdenk | a6db71d | 2003-04-08 23:25:21 +0000 | [diff] [blame] | 28 | 2. Connect to the serial console and to the BDI. Power on. On the |
| 29 | serial line, you should see: |
| 30 | |
| 31 | PURPLE@1.2> |
| 32 | |
| 33 | 3. Type '8'. No echo will be displayed. In response, you should get: |
| 34 | |
| 35 | 7A(pass) |
| 36 | |
| 37 | 4. From BDI, enter command: |
| 38 | |
| 39 | mmw 0xb800d860 0x0042c7ff |
| 40 | |
| 41 | 5. Then, from BDI: |
| 42 | |
| 43 | erase 0xB0000000 |
| 44 | erase 0xB0008000 |
| 45 | erase 0xB000C000 |
| 46 | erase 0xB0010000 |
| 47 | erase 0xB0020000 |
| 48 | |
| 49 | prog 0xB0000000 <u-boot.bin> bin |
| 50 | |
| wdenk | 57c58b4 | 2003-05-12 09:51:00 +0000 | [diff] [blame^] | 51 | 6. Power off. Restore the original S2 switch position: |
| wdenk | a6db71d | 2003-04-08 23:25:21 +0000 | [diff] [blame] | 52 | |
| wdenk | 57c58b4 | 2003-05-12 09:51:00 +0000 | [diff] [blame^] | 53 | 1 0 |
| 54 | ------ |
| 55 | | x| |
| 56 | | x| |
| 57 | |x | |
| 58 | | X| |
| 59 | ------ |
| wdenk | a6db71d | 2003-04-08 23:25:21 +0000 | [diff] [blame] | 60 | |
| wdenk | 57c58b4 | 2003-05-12 09:51:00 +0000 | [diff] [blame^] | 61 | Power on. U-Boot should come up. |
| 62 | |
| 63 | |
| wdenk | a6db71d | 2003-04-08 23:25:21 +0000 | [diff] [blame] | 64 | |
| 65 | Implementation Notes: |
| 66 | --------------------- |
| 67 | |
| 68 | Due to the RAM/flash bus arbitration problem the suggested workaround |
| 69 | had to be implemented. It works okay. On the downside is that you |
| 70 | can't really check whether 'erase' is complete by polling flash as it |
| 71 | is usually done. Instead, the flash driver simply waits for a given |
| 72 | time and assumes that erase then has passed. This behaviour is |
| 73 | identical to what the VxWorks driver does; also, the same timeout (6 |
| wdenk | 57c58b4 | 2003-05-12 09:51:00 +0000 | [diff] [blame^] | 74 | seconds) was chosen. Note that this timeout applies for each erase |
| wdenk | a6db71d | 2003-04-08 23:25:21 +0000 | [diff] [blame] | 75 | operation, i. e. per erased sector. |