xref: /openbmc/u-boot/board/sbc8641d/README (revision 743d7592)
1702e6014SWolfgang DenkWind River SBC8641D reference board
2702e6014SWolfgang Denk===========================
3702e6014SWolfgang Denk
4702e6014SWolfgang DenkCreated 06/14/2007 Joe Hamman
5702e6014SWolfgang DenkCopyright 2007, Embedded Specialties, Inc.
6702e6014SWolfgang DenkCopyright 2007 Wind River Systemes, Inc.
7702e6014SWolfgang Denk-----------------------------
8702e6014SWolfgang Denk
9702e6014SWolfgang Denk1. Building U-Boot
10702e6014SWolfgang Denk------------------
11702e6014SWolfgang DenkThe SBC8641D code is known to build using ELDK 4.1.
12702e6014SWolfgang Denk
13702e6014SWolfgang Denk    $ make sbc8641d_config
14702e6014SWolfgang Denk    Configuring for sbc8641d board...
15702e6014SWolfgang Denk
16702e6014SWolfgang Denk    $ make
17702e6014SWolfgang Denk
18702e6014SWolfgang Denk
19702e6014SWolfgang Denk2. Switch and Jumper Settings
20702e6014SWolfgang Denk-----------------------------
21702e6014SWolfgang DenkAll Jumpers & Switches are in their default positions.  Please refer to
22702e6014SWolfgang Denkthe board documentation for details.  Some settings control CPU voltages
23702e6014SWolfgang Denkand settings may change with board revisions.
24702e6014SWolfgang Denk
25702e6014SWolfgang Denk3. Known limitations
26702e6014SWolfgang Denk--------------------
27702e6014SWolfgang DenkPCI:
28702e6014SWolfgang Denk	The PCI command may hang if no boards are present in either slot.
29*743d7592SPaul Gortmaker
30*743d7592SPaul Gortmaker4. Reflashing U-Boot
31*743d7592SPaul Gortmaker--------------------
32*743d7592SPaul GortmakerThe board has two independent flash devices which can be used for dual
33*743d7592SPaul Gortmakerbooting, or for u-boot backup and recovery.  A two pin jumper on the
34*743d7592SPaul Gortmakerthree pin JP10 determines which device is attached to /CS0 line.
35*743d7592SPaul Gortmaker
36*743d7592SPaul GortmakerAssuming one device has a functional u-boot, and the other device has
37*743d7592SPaul Gortmakera recently installed non-functional image, to perform a recovery from
38*743d7592SPaul Gortmakerthat non-functional image goes essentially as follows:
39*743d7592SPaul Gortmaker
40*743d7592SPaul Gortmakera) power down the board and jumper JP10 to select the functional image.
41*743d7592SPaul Gortmakerb) power on the board and let it get to u-boot prompt.
42*743d7592SPaul Gortmakerc) while on, using static precautions, move JP10 back to the failed image.
43*743d7592SPaul Gortmakerd) use "md fff00000" to confirm you are looking at the failed image
44*743d7592SPaul Gortmakere) turn off write protect with "prot off all"
45*743d7592SPaul Gortmakerf) get new image, i.e. "tftp 200000 /somepath/u-boot.bin"
46*743d7592SPaul Gortmakerg) erase failed image: "erase FFF00000 FFF3FFFF"
47*743d7592SPaul Gortmakerh) copy in new image: "cp.b 200000 FFF00000 40000"
48*743d7592SPaul Gortmakeri) ensure new image is written: "md fff00000"
49*743d7592SPaul Gortmakerk) power cycle the board and confirm new image works.
50