diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/I2C_Edge_Conditions | 2 | ||||
| -rw-r--r-- | doc/README-integrator | 110 | ||||
| -rw-r--r-- | doc/README.OFT | 28 | ||||
| -rw-r--r-- | doc/README.Sandpoint8240 | 4 | ||||
| -rw-r--r-- | doc/README.bedbug | 4 | ||||
| -rw-r--r-- | doc/README.dk1s10 | 4 | ||||
| -rw-r--r-- | doc/README.ebony | 4 | ||||
| -rw-r--r-- | doc/README.ml300 | 2 | ||||
| -rw-r--r-- | doc/README.mpc85xxads | 2 | ||||
| -rw-r--r-- | doc/README.ocotea | 6 | ||||
| -rw-r--r-- | doc/README.ocotea-PIBS-to-U-Boot | 4 | ||||
| -rw-r--r-- | doc/README.ppc440 | 2 |
12 files changed, 155 insertions, 17 deletions
diff --git a/doc/I2C_Edge_Conditions b/doc/I2C_Edge_Conditions index be7f1be..44d3478 100644 --- a/doc/I2C_Edge_Conditions +++ b/doc/I2C_Edge_Conditions @@ -28,7 +28,7 @@ I2C Edge Conditions: Notes ----- -!!!THIS IS AN UNDOCUMENTED I2C BUS BUG, NOT A IBM 4xx BUG!!! +!!!THIS IS AN UNDOCUMENTED I2C BUS BUG, NOT A AMCC 4xx BUG!!! This reset edge condition could possibly be present in every I2C controller and device available. For boards where a I2C bus reset diff --git a/doc/README-integrator b/doc/README-integrator new file mode 100644 index 0000000..ce8a9d2 --- /dev/null +++ b/doc/README-integrator @@ -0,0 +1,110 @@ + + U-Boot for ARM Integrator Development Platforms + + Peter Pearse, ARM Ltd. + peter.pearse@arm.com + www.arm.com + +Manuals available from :- +http://www.arm.com/products/DevTools/Hardware_Platforms.html + +Overview : +-------- +There are two Integrator variants - Integrator/AP and Integrator/CP. +Each may be fitted with a variety of core modules (CMs). +Each CM consists of a ARM processor core and associated hardware e.g + FPGA implementing various controllers and/or register + SSRAM + SDRAM + RAM controllers + clock generators etc. +CMs may be fitted with varying amounts of SDRAM using a DIMM socket. + +Boot Methods : +------------ +Integrator platforms can be configured to use U-Boot in at least three ways :- +a) Run ARM boot monitor, manually run U-Boot image from flash +b) Run ARM boot monitor, automatically run U-Boot image from flash +c) Run U-Boot image direct from flash. + +In cases a) and b) the ARM boot monitor will have configured the CM and mapped +writeable memory to 0x00000000 in the Integrator address space. +U-Boot has to carry out minimal configration before standard code is run. + +In case c) it may be necessary for U-Boot to perform CM dependent initialization. + +Configuring U-Boot : +------------------ + The makefile contains targets for Integrator platforms of both types +fitted with all current variants of CM. If these targets are to be used with +boot process c) above then CONFIG_INIT_CRITICAL may need to be defined to ensure +that the CM is correctly configured. + + There are also targets independent of CM. These may not be suitable for +boot process c) above. They have been preserved for backward compatibility with +existing build processes. + +Code Hierarchy Applied : +---------------------- +Code specific to initialization of a particular ARM processor has been placed in +cpu/arm<>/start.S so that it may be used by other boards. + +However, to avoid duplicating code through all processor files, a generic core +for ARM Integrator CMs has been added + + cpu/arm_intcm + +Otherwise. for example, the standard CM reset via the CM control register would +need placing in each CM processor file...... + +Code specific to the initialization of the CM, rather than the cpu, and initialization +of the Integrator board itself, has been placed in + + board/integrator<>/platform.S + board/integrator<>/integrator<>.c + +Targets +======= +The U-Boot make targets map to the available core modules as below. + +Integrator/AP is no longer available from ARM. +Core modules marked ** are also no longer available. + +ap720t_config ** CM720T +ap920t_config ** CM920T +ap926ejs_config Integrator Core Module for ARM926EJ-STM +ap946es_config Integrator Core Module for ARM946E-STM +cp920t_config ** CM920T +cp926ejs_config Integrator Core Module for ARM926EJ-STM +cp946es_config Integrator Core Module for ARM946E-STM +cp1136_config Integrator Core Module ARM1136JF-S TM + +The final groups of targets are for core modules where no explicit cpu +code has yet been added to U-Boot i.e. they all use the same U-Boot binary +using the generic "arm_intcm" core: + +ap966_config Integrator Core Module for ARM966E-S TM +ap922_config Integrator Core Module for ARM922T TM with ETM +ap922_XA10_config Integrator Core Module for ARM922T using Altera Excalibur +ap7_config ** CM7TDMI +integratorap_config +ap_config + + +cp966_config Integrator Core Module for ARM966E-S TM +cp922_config Integrator Core Module for ARM922T TM with ETM +cp922_XA10_config Integrator Core Module for ARM922T using Altera Excalibur +cp1026_config Integrator Core Module ARM1026EJ-S TM +integratorcp_config +cp_config + +The Makefile targets call board/integrator<>/split_by_variant.sh +to configure various defines in include/configs/integrator<>.h +to indicate the core module & core configuration and ensure that +board/integrator<>/u-boot.lds loads the cpu object first in the U-Boot image. + +********************************* +Because of this mechanism +> make clean +must be run before each change in configuration +********************************* diff --git a/doc/README.OFT b/doc/README.OFT new file mode 100644 index 0000000..dd1c632 --- /dev/null +++ b/doc/README.OFT @@ -0,0 +1,28 @@ +Open Firmware Flat Tree and usage. +---------------------------------- + +As part of the ongoing cleanup of the Linux PPC trees, the preferred +way to pass bootloader and board setup information is the open +firmware flat tree. + +Please take a look at the following email discussion for some +background. + + http://ozlabs.org/pipermail/linuxppc-dev/2005-August/019408.html + http://ozlabs.org/pipermail/linuxppc-dev/2005-August/019362.html + +The generated tree is part static and part dynamic. + +There is a static part which is compiled in with DTC and a dynamic +part which is programmatically appended. + +You'll need a fairly recent DTC tool, which is available by git at + + rsync://ozlabs.org/dtc/dtc.git + +The xxd binary dumper is needed too which I got from + + ftp://ftp.uni-erlangen.de/pub/utilities/etc/xxd-1.10.tar.gz + + +Pantelis Antoniou, 13 Oct 2005 diff --git a/doc/README.Sandpoint8240 b/doc/README.Sandpoint8240 index b506c01..a41b69a 100644 --- a/doc/README.Sandpoint8240 +++ b/doc/README.Sandpoint8240 @@ -253,7 +253,7 @@ bootfile=telemetry hostname=sp1 ethaddr=00:03:47:97:E4:6B load=tftp 100000 u-boot.bin -update=protect off all;era FFF00000 FFF3FFFF;cp.b 100000 FFF00000 $(filesize);saveenv +update=protect off all;era FFF00000 FFF3FFFF;cp.b 100000 FFF00000 ${filesize};saveenv filesize=1f304 gatewayip=145.17.228.1 netmask=255.255.255.0 @@ -308,7 +308,7 @@ Protected 1 sectors You can put these commands into some environment variables; => setenv load tftp 100000 u-boot.bin -=> setenv update protect off all\;era FFF00000 FFF3FFFF\;cp.b 100000 FFF00000 \$(filesize)\;saveenv +=> setenv update protect off all\;era FFF00000 FFF3FFFF\;cp.b 100000 FFF00000 \${filesize}\;saveenv => saveenv Then you just have to type "run load" then "run update" diff --git a/doc/README.bedbug b/doc/README.bedbug index 56aeb09..9cfb421 100644 --- a/doc/README.bedbug +++ b/doc/README.bedbug @@ -2,7 +2,7 @@ BEDBUG Support for U-Boot -------------------------- These changes implement the bedbug (emBEDded deBUGger) debugger in U-Boot. -A specific implementation is made for the IBM405 processor but other flavors +A specific implementation is made for the AMCC 405 processor but other flavors can be easily implemented. ##################### @@ -58,7 +58,7 @@ can be easily implemented. routines are common to all PowerPC processors. ./cpu/ppc4xx/bedbug_405.c - IBM PPC405 specific debugger routines. + AMCC PPC405 specific debugger routines. Bedbug support for the MPC860 diff --git a/doc/README.dk1s10 b/doc/README.dk1s10 index bb8375a..622bef5 100644 --- a/doc/README.dk1s10 +++ b/doc/README.dk1s10 @@ -118,11 +118,11 @@ see the following: at the Altera Standard 32 to SRAM: - ==> cp.b 800000 40000 $(filesize) + ==> cp.b 800000 40000 ${filesize} at the Microtronix LDK 2.0 to SDRAM: - ==> cp.b 1010000 8000000 $(filesize) + ==> cp.b 1010000 8000000 ${filesize} U-Boot will now automatically start when the board is powered on or reset using the Standard-32 configuration. To start U-Boot with the diff --git a/doc/README.ebony b/doc/README.ebony index 6e2a811..8b030db 100644 --- a/doc/README.ebony +++ b/doc/README.ebony @@ -1,9 +1,9 @@ - IBM Ebony Board + AMCC Ebony Board Last Update: September 12, 2002 ======================================================================= -This file contains some handy info regarding U-Boot and the IBM +This file contains some handy info regarding U-Boot and the AMCC Ebony evalutation board. See the README.ppc440 for additional information. diff --git a/doc/README.ml300 b/doc/README.ml300 index c9ef6e6..27c5b92 100644 --- a/doc/README.ml300 +++ b/doc/README.ml300 @@ -5,7 +5,7 @@ Xilinx ML300 platform --------------- The Xilinx ML300 board is based on the Virtex-II Pro FPGA with -integrated IBM PowerPC 405 core. The board is normally booted from +integrated AMCC PowerPC 405 core. The board is normally booted from System ACE CF. U-Boot is then run out of main memory. An FPGA is a configurable and thus very flexible device. To diff --git a/doc/README.mpc85xxads b/doc/README.mpc85xxads index 08d6831..f0cf782 100644 --- a/doc/README.mpc85xxads +++ b/doc/README.mpc85xxads @@ -130,7 +130,7 @@ Updated 13-July-2004 Jon Loeliger include/configs/MPC8540ADS.h include/configs/MPC8560ADS.h - CONFIG_BOOKE BOOKE(e.g. Motorola MPC85xx, IBM 440, etc) + CONFIG_BOOKE BOOKE(e.g. Motorola MPC85xx, AMCC 440, etc) CONFIG_E500 BOOKE e500 family(Motorola) CONFIG_MPC85xx MPC8540,MPC8560 and their derivatives CONFIG_MPC8540 MPC8540 specific diff --git a/doc/README.ocotea b/doc/README.ocotea index 403735d..9ac3a18 100644 --- a/doc/README.ocotea +++ b/doc/README.ocotea @@ -1,9 +1,9 @@ - IBM Ocotea Board + AMCC Ocotea Board Last Update: March 2, 2004 ======================================================================= -This file contains some handy info regarding U-Boot and the IBM +This file contains some handy info regarding U-Boot and the AMCC Ocotea 440gx evalutation board. See the README.ppc440 for additional information. @@ -53,7 +53,7 @@ Special note about the Cicada CIS8201: This has been done in the 440gx_enet.c file with a #ifdef/endif pair. -IBM does not store the EMAC ethernet addresses within their PIBS bootloader. +AMCC does not store the EMAC ethernet addresses within their PIBS bootloader. The addresses contained in the config header file are from my particular board and you _*should*_ change them to reflect your board either in the config file and/or in your environment variables. I found the addresses on diff --git a/doc/README.ocotea-PIBS-to-U-Boot b/doc/README.ocotea-PIBS-to-U-Boot index 0044aa0..25dd2a2 100644 --- a/doc/README.ocotea-PIBS-to-U-Boot +++ b/doc/README.ocotea-PIBS-to-U-Boot @@ -75,8 +75,8 @@ powering the board you should see the following message: U-Boot 1.1.3 (Apr 5 2005 - 22:59:57) -IBM PowerPC 440 GX Rev. C -Board: IBM 440GX Evaluation Board +AMCC PowerPC 440 GX Rev. C +Board: AMCC 440GX Evaluation Board VCO: 1066 MHz CPU: 533 MHz PLB: 152 MHz diff --git a/doc/README.ppc440 b/doc/README.ppc440 index 95d63fc..08f34f5 100644 --- a/doc/README.ppc440 +++ b/doc/README.ppc440 @@ -12,7 +12,7 @@ and enabled via the CONFIG_440 flag. It is largely based on the 405gp code. A sample board support implementation is contained in the board/ebony directory. -All testing was performed using the IBM Ebony board using both +All testing was performed using the AMCC Ebony board using both Rev B and Rev C silicon. However, since the Rev B. silicon has extensive errata, support for Rev B. is minimal (it boots, and features such as i2c, pci, tftpboot, etc. seem to work ok). |