summaryrefslogtreecommitdiff
path: root/doc/README.Purple
diff options
context:
space:
mode:
Diffstat (limited to 'doc/README.Purple')
-rw-r--r--doc/README.Purple29
1 files changed, 26 insertions, 3 deletions
diff --git a/doc/README.Purple b/doc/README.Purple
index 9e70004..c05e0ff 100644
--- a/doc/README.Purple
+++ b/doc/README.Purple
@@ -11,6 +11,20 @@ Installation Instructions:
| X|
------
+ Put the s3 switch into the following position:
+
+ 1 0
+ ------
+ |x |
+ |x |
+ |x |
+ |x |
+ |x |
+ | x|
+ | x|
+ |x |
+ ------
+
2. Connect to the serial console and to the BDI. Power on. On the
serial line, you should see:
@@ -34,8 +48,17 @@ Installation Instructions:
prog 0xB0000000 <u-boot.bin> bin
-6. Power off. Restore the original S2 switch position. Power on.
- U-Boot should come up.
+6. Power off. Restore the original S2 switch position:
+
+ 1 0
+ ------
+ | x|
+ | x|
+ |x |
+ | X|
+ ------
+
+ Power on. U-Boot should come up.
@@ -48,5 +71,5 @@ can't really check whether 'erase' is complete by polling flash as it
is usually done. Instead, the flash driver simply waits for a given
time and assumes that erase then has passed. This behaviour is
identical to what the VxWorks driver does; also, the same timeout (6
-seconds) was chosen. Note that this timeout applies for each errase
+seconds) was chosen. Note that this timeout applies for each erase
operation, i. e. per erased sector.