blob: dc3e00d10bcf5a3a9c4e8cc894d5e428b4398dc7 [file] [log] [blame]
wdenk60fbe252003-04-08 23:25:21 +00001Installation Instructions:
2--------------------------
3
41. Put the s2 switch into the following position:
5
6 1 0
7 ------
8 |x |
9 | x|
wdenk45219c42003-05-12 21:50:16 +000010 |x |
11 | X|
wdenk60fbe252003-04-08 23:25:21 +000012 ------
13
wdenkd6815432003-05-12 09:51:00 +000014 Put the s3 switch into the following position:
15
wdenk45219c42003-05-12 21:50:16 +000016 1 0
17 ------
18 | x |
19 | x |
20 | x|
21 | x|
22 ------
23
24 Put the s4 switch into the following position:
25
26 1 0
wdenkd6815432003-05-12 09:51:00 +000027 ------
28 |x |
29 |x |
wdenk45219c42003-05-12 21:50:16 +000030 |x |
wdenkd6815432003-05-12 09:51:00 +000031 |x |
32 |x |
33 | x|
34 | x|
wdenk45219c42003-05-12 21:50:16 +000035 |x |
wdenkd6815432003-05-12 09:51:00 +000036 ------
37
wdenk60fbe252003-04-08 23:25:21 +0000382. 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
433. Type '8'. No echo will be displayed. In response, you should get:
44
45 7A(pass)
46
474. From BDI, enter command:
48
49 mmw 0xb800d860 0x0042c7ff
50
515. 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
wdenkd6815432003-05-12 09:51:00 +0000616. Power off. Restore the original S2 switch position:
62
63 1 0
64 ------
65 | x|
66 | x|
wdenk45219c42003-05-12 21:50:16 +000067 |x |
68 | X|
wdenkd6815432003-05-12 09:51:00 +000069 ------
70
71 Power on. U-Boot should come up.
wdenk60fbe252003-04-08 23:25:21 +000072
73
74
75Implementation Notes:
76---------------------
77
78Due to the RAM/flash bus arbitration problem the suggested workaround
79had to be implemented. It works okay. On the downside is that you
80can't really check whether 'erase' is complete by polling flash as it
81is usually done. Instead, the flash driver simply waits for a given
82time and assumes that erase then has passed. This behaviour is
83identical to what the VxWorks driver does; also, the same timeout (6
wdenkd6815432003-05-12 09:51:00 +000084seconds) was chosen. Note that this timeout applies for each erase
wdenk60fbe252003-04-08 23:25:21 +000085operation, i. e. per erased sector.