board: tbs2910: add private imx config

[people/ms/u-boot.git] / board / sbc8641d / README

diff --git a/board/sbc8641d/README b/board/sbc8641d/README
index af180888182d1309b5d0d29a6241c3ea0c73ad92..4999b7763c9c024b47741c37cd5c987b3a32e24a 100644 (file)
--- a/board/sbc8641d/README
+++ b/board/sbc8641d/README
@@ -3,7 +3,7 @@ Wind River SBC8641D reference board
 
 Created 06/14/2007 Joe Hamman
 Copyright 2007, Embedded Specialties, Inc.
-Copyright 2007 Wind River Systemes, Inc.
+Copyright 2007 Wind River Systems, Inc.
 -----------------------------
 
 1. Building U-Boot
@@ -30,20 +30,20 @@ PCI:
 4. Reflashing U-Boot
 --------------------
 The board has two independent flash devices which can be used for dual
-booting, or for u-boot backup and recovery.  A two pin jumper on the
+booting, or for U-Boot backup and recovery.  A two pin jumper on the
 three pin JP10 determines which device is attached to /CS0 line.
 
-Assuming one device has a functional u-boot, and the other device has
+Assuming one device has a functional U-Boot, and the other device has
 a recently installed non-functional image, to perform a recovery from
 that non-functional image goes essentially as follows:
 
 a) power down the board and jumper JP10 to select the functional image.
-b) power on the board and let it get to u-boot prompt.
+b) power on the board and let it get to U-Boot prompt.
 c) while on, using static precautions, move JP10 back to the failed image.
 d) use "md fff00000" to confirm you are looking at the failed image
 e) turn off write protect with "prot off all"
 f) get new image, i.e. "tftp 200000 /somepath/u-boot.bin"
-g) erase failed image: "erase FFF00000 FFF3FFFF"
-h) copy in new image: "cp.b 200000 FFF00000 40000"
+g) erase failed image: "erase FFF00000 FFF5FFFF"
+h) copy in new image: "cp.b 200000 FFF00000 60000"
 i) ensure new image is written: "md fff00000"
 k) power cycle the board and confirm new image works.