blob: d07f1ccf7c332ed3e1fac39647cea7c24015d4b1 [file] [log] [blame]
Joe Hamman1bab0b02007-08-09 15:11:03 -05001Wind River SBC8641D reference board
2===========================
3
4Created 06/14/2007 Joe Hamman
5Copyright 2007, Embedded Specialties, Inc.
Paul Gortmaker7095ab32015-10-17 16:40:31 -04006Copyright 2007 Wind River Systems, Inc.
Joe Hamman1bab0b02007-08-09 15:11:03 -05007-----------------------------
8
91. Building U-Boot
10------------------
11The SBC8641D code is known to build using ELDK 4.1.
12
13 $ make sbc8641d_config
14 Configuring for sbc8641d board...
15
16 $ make
17
18
192. Switch and Jumper Settings
20-----------------------------
21All Jumpers & Switches are in their default positions. Please refer to
22the board documentation for details. Some settings control CPU voltages
23and settings may change with board revisions.
24
253. Known limitations
26--------------------
27PCI:
28 The PCI command may hang if no boards are present in either slot.
Paul Gortmakerb86d17f2015-10-17 16:40:29 -040029
304. Reflashing U-Boot
31--------------------
32The board has two independent flash devices which can be used for dual
33booting, or for u-boot backup and recovery. A two pin jumper on the
34three pin JP10 determines which device is attached to /CS0 line.
35
36Assuming one device has a functional u-boot, and the other device has
37a recently installed non-functional image, to perform a recovery from
38that non-functional image goes essentially as follows:
39
40a) power down the board and jumper JP10 to select the functional image.
41b) power on the board and let it get to u-boot prompt.
42c) while on, using static precautions, move JP10 back to the failed image.
43d) use "md fff00000" to confirm you are looking at the failed image
44e) turn off write protect with "prot off all"
45f) get new image, i.e. "tftp 200000 /somepath/u-boot.bin"
Paul Gortmaker7095ab32015-10-17 16:40:31 -040046g) erase failed image: "erase FFF00000 FFF5FFFF"
47h) copy in new image: "cp.b 200000 FFF00000 60000"
Paul Gortmakerb86d17f2015-10-17 16:40:29 -040048i) ensure new image is written: "md fff00000"
49k) power cycle the board and confirm new image works.