target.ref

vxworks pb926开发板的bsp包

\" integrator926ejs/target.ref - ARM Limited Integrator board's target-specific documentation
\"
\" Copyright 1999-2000 ARM Limited
\" Copyright 1999-2005 Wind River Systems, Inc.
\"
\" modification history
\" --------------------
\" 01a,09feb05,rec  created from integrator940t/target.ref v2a.
\"
\TITLE integrator - ARM Limited Integrator

NAME
`ARM Limited Integrator926ejs'

INTRODUCTION
This reference entry provides board-specific information necessary to run
VxWorks for the Integrator/AP with an ARM926EJ-S core module.  Before using a 
board with VxWorks, verify that the board runs in the factory configuration 
using vendor-supplied ROMs and jumper settings and checking the RS-232 
connection.


\sh ARM Firmware Suite Flash library conformance

The AFS Flash library defines a mechanism for storing multiple images
in Flash.  Each image can be identified by a record ('footer') which is
stored at the end of the last Flash page used by the image.  A special
type of image is used to store System Information Blocks ('SIB').  The
standard Integrator boot-switcher uses a SIB to store system settings,
such as core and bus clock speeds.

The current BSP implementation doesn't use this information.  Instead,
default values are chosen based on the CPU type.

Flash is used to store the boot line parameters.  The location in Flash
is defined by FLASH_ADRS.  This location in Flash can be changed by
modifying the block number in the definition of FLASH_ADRS (cf.
integrator.h).  If INCLUDE_FLASH_SIB_FOOTER is defined, a footer is
written at the end of this block to mark it as a Wind River Systems
type (TYPE_WRS_SIB).  This complies with the footer format used with
AFS.

\sh ROM Init code

Most of the code in romInit.s has been copied from uHAL's start-up
macros for the Integrator.  The board-specific code starts at HiPosn,
where the Core Module remap flag is set.

The code to calculate the size of SDRAM/SSRAM is copied directly from
uHAL's target.s.  As described in the comments, this leaves r1
containing the size of RAM available.  This value is stored in the
variable integratorMemSize, but is not currently used.


\sh Boot ROMs

The boot ROM image has been tested running from Flash.  The Makefile
options are set to run the image from the start of Flash, 0x24000000.
Two methods are available for loading the boot ROM image into target 
flash.  The image may be loaded via the target serial port using the 
supplied onboard boot Monitor program (ref: ARM Firmware Suite 
Reference Guide Chapt 4).  To load the target flash using this method,
first build bootrom.hex using the Tornado.  Connect a null serial cable
from the host serial port to the target Comm-1 port (closest to the 
dip-switches).  Open a terminal emulator program and configure it for 
38400 baud, XON/XOFF flow control.  Power on the Integrator board and 
observe the ARM boot ROM banner.  Download the flash image by typing 
"L <enter>" for load image.  Observe that the firmware deletes image zero.  
Select Transfer->SendTextFile, then browse to find the above hex file.  After 
the download initiates, type "<control-C>".  The terminal window will remain
silent for approximately two minutes, after which it will acknowledge that 
the download has completed and return a boot monitor prompt.
  
Note: Some serial communication programs do not work properly if they
do not delay (approx 5ms) between sending characters.  Other
serial communication programs (such as Hyperterminal) may take an
extraordinary amount of time (1 hour) to program the flash because
they continuously time out from being unable to handle the
communication protocol used by the ARM boot loader.

The ARM Flash Utility (AFU) can be used to program the image into
Flash.  For this the bootrom needs to be generated and converted to 
binary format:
\bs
   make bootrom.hex
\be
The 4-pole DIL switch (S1) is used to control the boot settings.  Turn
S1-1 off to boot from the start of Flash (0x24000000).  With S1-1 on,
the boot switcher will run, in which case S1-4 determines whether to
enter the boot monitor console (s1-4 on), or boot from a defined Flash
image (s1-4 off).

The ARM debugger can be used to load this binary image onto Flash.
For this choose a backend to connect to the target and start the ARM 
debugger and set S1-1 on.  Load and run the semihosted AFU.AXF until 
there are some messages printed in the ARM debugger console window 
with a AFU> prompt. 

To see a listing of the images present in the Flash enter the 
following command:
\bs
    AFU> list
\be
Assuming there is already an image with number 1 in Flash, the new 
binary image can replace it with the following sequence of commands:
\bs
  AFU> Delete 1
  AFU> Program 1 VxBoot c:\Tornado\target\config\integrator926ejs\bootrom.bin \
       b0
\be

The board can use this new image to boot from by setting S1-1 off.

The boot monitor's BI command determines which Flash image to boot from.

\sh Jumpers
The following jumpers and switches are relevant to VxWorks configuration.

\ts
cf3 s s
lf3 lf3 lf3
l l lw(3i) .

Integrator 926

Jumper | Function | Description
------------------------------
S1 | Various | Four-pole DIL switches, S1-1 to S1-4
S1-1 | Boot ROM select | This switch determines which device is mapped to low memory at startup
 | | (before the header card maps its own RAM to address 0).  When the
 | | switch is turned ON, the boot ROM is selected, causing the AFS Boot
 | | Monitor to execute.  Otherwise, Flash is selected.
S1-4 | Boot switcher  | The boot monitor reads this switch at startup to determine whether to
 | | continue execution or jump to Flash.  If the switch is ON, the boot
 | | monitor prompt is generated; otherwise it reads the SIB to determine
 | | which Flash block to jump to.
\te

For details of jumper configuration, see the board diagram at the end
of this entry and in the hardware manual.

FEATURES

The Integrator/AP is a platform for code development for embedded ARM
processors.  It supports up to four processors for which it provides clocks, 
bus arbitration and interrupt handling.  It also provides Flash memory, 
boot ROM, 2 serial ports, readable switches and controllable LEDS.

The Integrator/AP supports flexible expansion:

 - system bus expansion allowing core modules and logic modules to be added.
 - PCI bus bridge allowing PCI expansion cards to be mounted.
 - extension to the PCI bus allowing the Integrator/AP to be installed in a 
   CompactPCI card rack.

\sh Supported Features

The BSP supports and has been tested with PCI Ethernet cards containing
the Digital 21x4x Ethernet controller chip and/or the Intel 8255x Ethernet
controller chip.

\sh RAM size

By default, the RAM size is set to 128 Mbytes (see LOCAL_MEM_SIZE).  This
requires an SDRAM DIMM of at least that size to be fitted to the core
module header card.  The RAM size is configured by changing
LOCAL_MEM_SIZE in config.h.  If this is reduced below 128 MBytes, other
values may need changing, such as RAM_HIGH_ADRS.  The boot ROM
initialization code automatically reads the SPD data from the SDRAM to
configure CM_SDRAM correctly (see CM926EJ-S User Guide, p. 4-16).
If LOCAL_MEM_AUTOSIZE is defined, the board will automatically configure
memory size on boot up.  Size computed and used includes the SDRAM memory
area as well as the SSRM (1-Meg for the 926).

\sh Timestamp support

Two AMBA timers are used by the system and auxiliary clock
facilities.  The system clock provides the timestamp timer as well.
A third timer is used by power managmenet if enabled.


\sh Unsupported Features

No explicit support is provided for use of the JTAG port, EmbeddedICE, 
reading the switches, or any other PCI cards.  However, nothing is done
to prevent these features from being used (e.g. by the Multi-ICE
backend for Tornado).

\sh Flash memory as NVRAM

If the BSP is configured with INCLUDE_FLASH defined, the standard VxWorks
Flash support is included.