target.nr

VxWorks 5.4嵌入式操作系统, Tornado II开发平台BSP包的移植

0xa0000	0x60000	video ram, etc
0x100000	LOCAL_MEM_SIZE - 0x100000	upper memory
.TE

.SS "Shared Memory"
Not applicable to this BSP

.SS "Interrupts"
All ISA interrupts are external to the CPU and are routed
through the ISA interrupt prioritization hardware.  This hardware is
comprised of two 82C59 PICs.  There are 16 ISA interrupts and
interrupt priority levels numbered 0 through 15. The mapping between
interrupt numbers and priority levels is not necessarily one to one.
The motherboard hardware determines the mapping of interrupt
request lines (IRQ) to priority levels. The hardware should
adhere to the standard ISA assignments:

.ne 18 
            IRQ         Priority
            ---         --------
             0              0
             1              1
             2              2
             3             11
             4             12
             5             13
             6             14
             7             15
             8              3
             9              4
            10              5
            11              6
            12              7
            13              8
            14              9
            15             10

IRQs 0 - 7 are handled by PIC1 and IRQs 8 - 15 by PIC2.  PIC2 interrupts are
cascaded into PIC1 at IRQ2 which is reflected in the above table.

.SS "Serial Configuration"
Refer to the board vendor's documentation.

.SS "SCSI Configuration"
Refer to the board vendor's documentation.

.SS "Network Configuration"
Refer to the board vendor's documentation.

.SS "VME Access"
This BSP has no VME access

.SS "PCI Access"
In order to use PCI the INCLUDE_PCI
directive must be enabled in config.h.
Furthermore, PCI_CFG_TYPE in pc.h
must be set to the correct configuration type.
Values for PCI_CFG_TYPE must be one of:

.TS
center;
c c
l l.
Macro	meaning
_
PCI_CFG_FORCE	force user specified configuration
PCI_CFG_AUTO	VxWorks does auto configuration. Currently unavailable.
PCI_CFG_NONE	external agent does configuration
.TE

PCI defines two mechanisms. The newer method, and the default vxWorks
method, is PCI_MECHANISM_1. Some older PCs might work better with
the old method, PCI_MECHANISM_2. If PCI is not working with
your older PC, change the first argument to pciIomapLibInit
to PCI_MECHANISM_2 in sysLib.c:
.ne 7
.CS
#ifdef  INCLUDE_PCI
    pciIomapLibInit (PCI_MECHANISM_1, PCI_CONFIG_ADDR, PCI_CONFIG_DATA,
NONE);
#if     FALSE
    pciIomapLibInit (PCI_MECHANISM_2, PCI_CONFIG_CSE, PCI_CONFIG_FORWARD,
                     PCI_CONFIG_BASE);
#endif  /* FALSE */
.CE
.ne 22
.SS "Boot Devices"
The supported boot devices are:
	
.CS
    \f3xx\f1 - Ethernet (any one of the many adaptors described above)
.CE
.CS
    \f3pcmcia=<slot number>\f1 - PCMCIA device
        slot number is one of:
            0 = PCMCIA slot 0
            1 = PCMCIA slot 1
	Note: Supported PCMCIA boot cards are the 3COM Etherlink III PC card
	and a PCMCIA ATA card
.CE
.CS
    \f3fd=<drive number>,<diskette type>\f1 - Diskette
        drive number is one of:
            0 = default; the first diskette drive (drive A:)
            1 = the second diskette drive (drive B:)
        diskette type is one of:
            0 = default; 3.5" diskette
            1 = 5.25" diskette
.CE
.CS
    \f3ata=<controller number>,<drive number>\f1 - ATA/IDE drive
        controller number is one of:
            0 = controller described in the first entry of 
                the ataResources table
            1 = controller described in the second entry of 
                the ataResources table
        drive number is one of:
            0 = first drive on the controller
            1 = second drive on the controller
.CE
Note: 
By default, with INCLUDE_ATA, vxWorks is set up for 
one ATA hard disk device on the primary ATA controller.  
The 2nd hard disk on the primary controller and the 
secondary controller are normally disabled to prevent timeouts.
If you have multiple controllers and/or hard disks
you must modify the ataResources structure array in sysLib.c to support 
more drives.

.ne 34
Example:
Two controllers, each with two drives (4 drives total):
.CS
ATA_RESOURCE ataResources[ATA_MAX_CTRLS] =
    {
        {
            {
                5, 0,
                {ATA0_IO_START0, ATA0_IO_START1}, 
                {ATA0_IO_STOP0, ATA0_IO_STOP1}, 0,
                0, 0, 0, 0, 0
            },
            IDE_LOCAL, ATA0_NUM_DRIVES, ATA0_INT_VEC, 
            ATA0_INT_LVL, ATA0_CONFIG, ATA_SEM_TIMEOUT, 
            ATA_WDG_TIMEOUT, 0, 0
        },
        {
            {
                 5, 0,
                 {ATA1_IO_START0, ATA1_IO_START1}, 
                 {ATA1_IO_STOP0, ATA1_IO_STOP1}, 0,
                 0, 0, 0, 0, 0
            },
            IDE_LOCAL, ATA1_NUM_DRIVES, ATA1_INT_VEC, 
            ATA1_INT_LVL, ATA1_CONFIG, ATA_SEM_TIMEOUT, 
            ATA_WDG_TIMEOUT, 0, 0
        }
    };
.CE
where:
.CS
#define ATA0_NUM_DRIVES 2
#define ATA1_NUM_DRIVES 2
#define ATA0_INT_LVL 0x0e
#define ATA1_INT_LVL 0x0f
.CE
A boot EPROM (type 27020 or 27040) is supported 
with Blunk Microsystems' ROM Card 1.0. 
For information on booting from these devices, 
see the Blunk Microsystems documentation.
The program romcard.s, a loader for code programmed in to the EPROM,
is provided to support 
VxWorks with the ROM Card.
In addition, the following configurations are defined in 
the makefile to generate Motorola S-record format from 
bootrom_uncmp or from vxWorks_boot.st :
.TS
center;
l l.
romcard_bootrom_512.hex	boot	ROM image for 27040 (512 KB)
romcard_bootrom_256.hex	boot	ROM image for 27020 (256 KB)
romcard_vxWorks_st_512.hex	bootable VxWorks image for 27040 (512 KB)
.TE
Neither the ROM Card nor the EPROM is distributed with VxWorks.
For more information visit http://www.blunkmicro.com/

.SS "Boot Methods"
The boot methods are affected by the boot parameters.  If no password is
specified, RSH (remote shell) protocol is used.  If a password is specified,
FTP protocol is used, or, if the flag is set, TFTP protocol is used.

These protocols apply only to Ethernet devices

.SS "ROM Considerations"
Not applicable to this BSP

.SH "SPECIAL CONSIDERATIONS"
.SS "Delivered Objects"
.ne 20
.TS
center;
c c
l l.
Object Name	Description
_
vxWorks	T{
image with no target shell or target symbol table. Network is included
and initialized.
T}
VxWorks.st	T{
fully linked stand alone image including
a target based shell, symbol table, and network 
interface. Note that the network interface is not initialized.
There is no WDB agent.
T}
bootrom_uncmp	T{
bootrom with uncompressed image which will run in lower memory
T}
mkboot.o	vxWorks utility for creating boot disks
.TE

.SS "Make Targets"
The BSP supports the following make targets:

.TS E
expand;
cw(1i)	cw(2i)	c
lw(1i)	lw(2i)	l.
Image Name	Description	Comments
=
vxWorks_rom	T{
high memory uncompressed bootable vxWorks
T}
vxWorks_rom_low	T{
low memory uncompressed bootable vxWorks
T}	T{
feiattach may not obtain enough memory
T}
vxWorks.st_rom	T{
high memory compressed bootable vxWorks.st
T}
bootrom	T{
low memory compressed bootrom
T}
bootrom_uncmp	T{
low memory uncompressed bootrom
T}
bootrom_high	T{
high memory compressed bootrom
T}	T{
May fail to boot; psychadelic video suggest video memory
or controller corrupted
T}
vxWorks	standard "Tornado-style" vxworks
vxWorks.st	T{
Fully linked stand alone vxWorks
including target based shell, symbol table, and network 
interface. The network interface is not initialized.
There is no WDB agent.
T}
vxWorks.res_rom	T{
Standalone VxWorks image that can be put in ROM.
Only the data segment of this ROM image is copied into RAM.
T}
vxWorks.res_rom_nosym	T{
Standalone VxWorks image that can be put in ROM.
Only the data segment of this ROM image is copied into RAM.
There is no symbol table. 
T}
_
.TE

.SS "Special Routines"
The following routines are specific to this BSP and are available
to the user. The are written in assembly code in sysALib.s. For 
further details see the man pages:
.CS
sysInByte - input one byte from I/O space
sysInWord - input one word from I/O space
sysInLong - input one long-word from I/O space
sysOutByte - output one byte to I/O space
sysOutWord - output one word to I/O space
sysOutLong - output one long-word to I/O space
sysInWordString - input word string from I/O space
sysInLongString - input long string from I/O space
sysOutWordString - output word string to I/O space
sysOutLongString - output long string to I/O space
.SS "Known Problems"
bootrom_high (high memory compressed bootrom) 
may fail to boot; psychadelic video suggest video memory
or controller corrupted

vxWorks_rom_low (low memory uncompressed bootable vxWorks)
feiattach may fail: feiattach might not be
able to obtain enough memory

Failures during Validation Test Suite (VTS):

NVRAM test: fails as this BSP has no NVRAM.

Catastrophic error test: fails as the VTS expects
an exception message but this BSP displays none;
however, the BSP correctly recovers
by rebooting the target.

Bootline Test :
Bus error test for local error address fails.
Bus error test for off-board error address fails.
Boot commands test failed as the VTS incorrectly presumes a big
endian architecture.

.SS "Other"
The valid auxiliary clock rates are between 2 ticks per 
second and 2 to the power of 13 ticks per second (2^13 = 8192).

Warm booting (reboot) is dependent upon the following parameters (shown with
default values) in config.h:

.CS
#define SYS_WARM_TYPE       1   /* 0=BIOS, 1=Floppy, 2=Ata (Hard) */
#define SYS_WARM_FD_DRIVE   0   /* 0 = drive a:, 1 = b: */
#define SYS_WARM_FD_TYPE    0   /* 0 = 3.5" 2HD, 1 = 5.25" 2HD */
#define SYS_WARM_ATA_CTRL   0   /* controller 0 */
#define SYS_WARM_ATA_DRIVE  0   /* 0 = c:, 1 = d: */
.CE

If SCSI configuration fails, it may be the result of improper SCSI bus 
termination. Check termination carefully on all devices, including
the controller. Note that some devices
have built in termination that is configured via a jumper.

In order to dynamically update the MMU table entries,
prior to MMU initialization,
several dummy entries
have been added to the end of the memory description
table sysPhysMemDesc. This allows PCI device configuration space,
configured by the BIOS, to be properly mapped into the VxWorks memory
map. This is done by sysMmuMapAdd() in sysLib.c.
.SH "AUTHOR"
Original port by Hdei Nunoe of Wind River Systems, Alameda, CA.

.SH SEE ALSO
.tG "Getting Started,"
.pG "Configuration"
.pG "Architecture Appendix"

.SH "BIBLIOGRAPHY"
Refer to the vendor's documentation for the motherboard and
any adaptor cards installed.