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
Wolfgang Denk 256176d3d5 Merge with /home/wd/git/u-boot/custodian/u-boot-mpc83xx 18 years ago
..
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.autoboot
README.bamboo
README.bedbug
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.idma2intr
README.lynxkdi
README.m68k
README.ml300
README.modnet50
README.mpc5xx
README.mpc74xx
README.mpc83xxads
README.mpc85xxads
README.mpc85xxcds
README.mpc832xemds
README.mpc7448hpc2
README.mpc8313erdb
README.mpc8349emds.ddrecc
README.mpc8349itx
README.mpc8360emds
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.sched
README.serial_multi
README.silent
README.standalone
README.stxxtc
README.usb
README.video
README.xpedite1k
TODO-i386

README.xpedite1k

			   XES XPedite1000 Board

Last Update: December 29, 2003
=======================================================================

This file contains some handy info regarding U-Boot and the XES
XPedite1000 PPC440GX PrPMC board. See the README.ppc440 for additional
information.


SWITCH SETTINGS & JUMPERS
==========================

Jumpers selected for AMD29LV040B flash part as the boot flash.


I2C Strap EEPROM & Environment Settings
=======================================

The XPedite1000 uses a single I2C eeprom for the 440 strappings and for
the environment variables. The first page (256 bytes) contains the
strappings and the 2 EMAC HW Ethernet addresses. Be careful not to
change the 1st page of the EEPROM! Unpopulated jumper J560 can get you
out of trouble as it disables the strapping read from EEPROM.

I2C iprobe
=====================

The i2c utilities work and have been tested on Rev B. of the 440GX. See
README.ebony for more information about i2c probing with the 440.


GETTING OUT OF I2C TROUBLE
===========================

(Direct quote from README.ebony)
If you're like me ... you may have screwed up your bootstrap serial
eeprom ... or worse, your SPD eeprom when experimenting with the
i2c commands. If so, here are some ideas on how to get out of
trouble:

Serial bootstrap eeprom corruption:
-----------------------------------
Power down the board and set the following straps:

J560 - closed

This will select the default sys0 and sys1 settings (the serial
eeproms are not used). Then power up the board and fix the serial
eeprom using the imm command. Here are the values I currently
use:

=> imd 50 0 10

0000: 85 7d 42 06 07 80 11 00 00 00 00 00 00 00 00 00 .}B.............

Once you have the eeproms set correctly change the
J560 straps as you desire.


PPC440GX Ethernet EMACs
=======================

The XES XPedite1000 uses emac 2 & 3 and ignores emac 0 & 1. PHYs are connected
only to emac 2 & 3. The HW Ethernet addresses are read from the i2c eeprom and
placed in the bd info structure for enet2addr and enet3addr. The ethernet driver
senses that enetaddr and enet1addr are 0's and does not use them.

As of this writing gigabit ethernet and the TCPIP acceleration hardware is not
supported.


Flash Support
=============

As of this writing, there is support for the 1/2mb boot flash only. User flash
is not yet supported.


Regards,
--Travis
<travis.sawyer@sandburst.com>