u-boot

mirror of https://github.com/AsahiLinux/u-boot synced 2024-11-24 21:54:01 +00:00

History

Simon Glass 52c411805c board_f: Drop board_type parameter from initdram() It looks like only cm5200 and tqm8xx use this feature, so we don't really need it in generic code. Drop it and have the users access gd->board_type directly. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>		2017-04-05 13:58:44 -04:00
..
ddr.c	Add more SPDX-License-Identifier tags	2016-01-19 08:31:21 -05:00
Kconfig	kconfig: remove redundant "string" type in arch and board Kconfigs	2014-09-13 16:43:55 -04:00
law.c	Add GPL-2.0+ SPDX-License-Identifier to source files	2013-07-24 09:44:38 -04:00
MAINTAINERS	Add board MAINTAINERS files	2014-07-30 08:48:06 -04:00
Makefile	Driver/DDR: Moving Freescale DDR driver to a common driver	2013-11-25 11:43:43 -08:00
README	Use correct spelling of "U-Boot"	2016-02-06 12:00:59 +01:00
sbc8641d.c	board_f: Drop board_type parameter from initdram()	2017-04-05 13:58:44 -04:00

README

Wind River SBC8641D reference board
===========================

Created 06/14/2007 Joe Hamman
Copyright 2007, Embedded Specialties, Inc.
Copyright 2007 Wind River Systems, Inc.
-----------------------------

1. Building U-Boot
------------------
The SBC8641D code is known to build using ELDK 4.1.

    $ make sbc8641d_config
    Configuring for sbc8641d board...

    $ make


2. Switch and Jumper Settings
-----------------------------
All Jumpers & Switches are in their default positions.  Please refer to
the board documentation for details.  Some settings control CPU voltages
and settings may change with board revisions.

3. Known limitations
--------------------
PCI:
	The PCI command may hang if no boards are present in either slot.

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
three pin JP10 determines which device is attached to /CS0 line.

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.
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 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.