]>
Commit | Line | Data |
---|---|---|
60fbe254 WD |
1 | Installation Instructions: |
2 | -------------------------- | |
3 | ||
4 | 1. Put the s2 switch into the following position: | |
5 | ||
7f70e853 | 6 | Off On |
60fbe254 WD |
7 | ------ |
8 | |x | | |
9 | | x| | |
45219c46 WD |
10 | |x | |
11 | | X| | |
60fbe254 WD |
12 | ------ |
13 | ||
d6815435 WD |
14 | Put the s3 switch into the following position: |
15 | ||
7f70e853 | 16 | Off On |
45219c46 WD |
17 | ------ |
18 | | x | | |
19 | | x | | |
20 | | x| | |
21 | | x| | |
22 | ------ | |
23 | ||
24 | Put the s4 switch into the following position: | |
25 | ||
7f70e853 | 26 | Off On |
d6815435 WD |
27 | ------ |
28 | |x | | |
29 | |x | | |
45219c46 | 30 | |x | |
d6815435 WD |
31 | |x | |
32 | |x | | |
33 | | x| | |
34 | | x| | |
45219c46 | 35 | |x | |
d6815435 WD |
36 | ------ |
37 | ||
60fbe254 WD |
38 | 2. Connect to the serial console and to the BDI. Power on. On the |
39 | serial line, you should see: | |
40 | ||
41 | [email protected]> | |
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 | ||
d6815435 WD |
61 | 6. Power off. Restore the original S2 switch position: |
62 | ||
7f70e853 | 63 | Off On |
d6815435 WD |
64 | ------ |
65 | | x| | |
66 | | x| | |
45219c46 WD |
67 | |x | |
68 | | X| | |
d6815435 WD |
69 | ------ |
70 | ||
71 | Power on. U-Boot should come up. | |
60fbe254 WD |
72 | |
73 | ||
60fbe254 WD |
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 | |
d6815435 | 83 | seconds) was chosen. Note that this timeout applies for each erase |
60fbe254 | 84 | operation, i. e. per erased sector. |