upstream u-boot with additional patches for our devices/boards: https://lists.denx.de/pipermail/u-boot/2017-March/282789.html (AXP crashes) ; Gbit ethernet patch for some LIME2 revisions ; with SPI flash support
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
u-boot/doc
..
I2C_Edge_Conditions
README-i386
README-integrator
README.440-DDR-performance
README.AMCC-eval-boards-cleanup
README.ARM-SoC
README.ARM-memory-map
README.AVR32
README.COBRA5272
README.EVB-64260-750CX
README.INCA-IP
README.IPHASE4539
README.IceCube
README.JFFS2
README.JFFS2_NAND
README.Lite5200B_low_power
README.MBX
README.MPC866
README.Modem
README.NetConsole
README.OFT
README.OXC
README.PIP405
README.POST
README.PXA_CF
README.PlanetCore
README.Purple
README.RPXClassic
README.RPXlite
README.SBC8560
README.SNTP
README.Sandpoint8240
README.TQM8260
README.VLAN
README.adnpesc1
README.adnpesc1_base32
README.alaska8220
README.amigaone
README.atum8548
README.autoboot
README.bamboo
README.bedbug
README.blackfin
README.cmi
README.commands
README.commands.itest
README.console
README.db64360
README.db64460
README.dk1c20
README.dk1c20_std32
README.dk1s10
README.dk1s10_mldk20
README.dk1s10_std32
README.dk1s40_std32
README.dk20k200_std32
README.ebony
README.evb64260
README.fads
README.generic_usb_ohci
README.idma2intr
README.lynxkdi
README.m68k
README.m5253evbe
README.m5373evb
README.m5475evb
README.m52277evb
README.m54455evb
README.marubun-pcmcia
README.ml300
README.modnet50
README.mpc5xx
README.mpc74xx
README.mpc83xx.ddrecc
README.mpc83xxads
README.mpc85xxads
README.mpc85xxcds
README.mpc832xemds
README.mpc837xemds
README.mpc837xerdb
README.mpc7448hpc2
README.mpc8313erdb
README.mpc8315erdb
README.mpc8323erdb
README.mpc8349itx
README.mpc8360emds
README.mpc8544ds
README.mpc8610hpcd
README.mpc8641hpcn
README.nand
README.nand-boot-ppc440
README.ne2000
README.nios
README.nios_CFG_NIOS_CPU
README.nios_DK
README.ns9750dev
README.ocotea
README.ocotea-PIBS-to-U-Boot
README.omap730p2
README.ppc440
README.sbc8349
README.sbc8548
README.sbc8641d
README.sched
README.serial_multi
README.sh
README.sha1
README.silent
README.standalone
README.stxxtc
README.usb
README.video
README.xpedite1k
README.zeus
TODO-i386

README.zeus


Storage of the board specific values (ethaddr...)
-------------------------------------------------

The board specific environment variables that should be unique
for each individual board, can be stored in the I2C EEPROM. This
will be done from offset 0x80 with the length of 0x80 bytes. The
following command can be used to store the values here:

=> setdef de:20:6a:ed:e2:72 de:20:6a:ed:e2:73 AB0001

ethaddr eth1addr serial#

Now those 3 values are stored into the I2C EEPROM. A CRC is added
to make sure that the values get not corrupted.


SW-Reset Pushbutton handling:
-----------------------------

The SW-reset push button is connected to a GPIO input too. This
way U-Boot can "see" how long the SW-reset was pressed, and a
specific action can be taken. Two different actions are supported:

a) Release after more than 5 seconds and less then 10 seconds:
-> Run POST

Please note, that the POST test will take a while (approx. 1 min
on the 128MByte board). This is mainly due to the system memory
test.

b) Release after more than 10 seconds:
-> Restore factory default settings

The factory default values are restored. The default environment
variables are restored (ipaddr, serverip...) and the board
specific values (ethaddr, eth1addr and serial#) are restored
to the environment from the I2C EEPROM. Also a bootline parameter
is added to the Linux bootline to signal the Linux kernel upon
the next startup, that the factory defaults should be restored.

The command to check this sw-reset status and act accordingly is

=> chkreset

This command is added to the default "bootcmd", so that it is called
automatically upon startup.

Also, the 2 LED's are used to indicate the current status of this
command (time passed since pushing the button). When the POST test
will be run, the green LED will be switched off, and when the
factory restore will be initiated, the reg LED will be switched off.


Loggin of POST results:
-----------------------

The results of the POST tests are logged in a logbuffer located at the end
of the onboard memory. It can be accessed with the U-Boot command "log":

=> log show
<4>POST memory PASSED
<4>POST cache PASSED
<4>POST cpu PASSED
<4>POST uart PASSED
<4>POST ethernet PASSED

The DENX Linux kernel tree has support for this log buffer included. Exactly
this buffer is used for logging of all kernel messages too. By enabling the
compile time option "CONFIG_LOGBUFFER" this support is enabled. This way you
can access the U-Boot log messages from Linux too.

2007-08-10, Stefan Roese <sr@denx.de>