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