target.nr

Vxworks的bsp软件开发包(基于wrPpmc74xx)

             of the 7400/7410 PMC module, and on the other said use the 
             RJ11 to 9/25 Pin addapter to connect it to your host. The UART 
             devices is set as follow: 8 data bits, 1 stop bit, hardware 
             handshaking, and parity disabled. The serial console (9600 bps).

       4.2.2 Second, plug the Intel PRO100B/S PCI NIC in the PCI slot on the 
             carrier board and connect a standard Ethernet cable to the NIC.
             
   4.3 Launch a terminal program on the host said, and configures it according 
       to the following details: 8 data bits, 1 stop bit, hardware handshaking, 
       and parity disabled. The serial console (9600 bps).

   4.4 Now to execute this new boot program turn the board off,and on. and you 
       should get the vxWorks boot count down on the terminal window. Press any
       key to stop the count down. Now follow the instruction in the 
       instructions in the "Getting Started" chapter of the 
       "VxWorks Programmer's Guide." for more detail how to configure vxWorks.

.SS "Using visionWARE to run VxWorks"
The following section will explain how to launch VxWorks using 
visionWARE as a boot loader.  Please follow the steps below:

Note(s): - Before using vsionWARE, verify that visionWARE is programmed 
into the FLASH. If visionWARE is not in the FLASH, please read the 
"Programming bootrom_uncmp to PPMC74xx FLASH" section on how to 
program the PPMC74xx Flash, but ignore step 3.1.5 or 3.2.4, "Converting the 
bootrom_uncmp.hex to bootrom_uncmp.bin", and instead of programming 
the 'bootrom_uncmp.bin', program the 'vWARE.bin' file.
 
    1. Connect the PPMC74xx serial channel (RS232) to a host 
       running terminal program at 9600 baud rate 
       (For example 'HyperTerminal') using the supplied serial cable.

    2. Connect the PPMC74xx 100/10Base-T (On the PCI Ethernet card) port to a 
       network hub.

    3. Open TFTP server and point to the location of the vxWorks.bdx file. 
       If you want to use the TFTP server that is supplied with visionWARE, 
       go to the visionWARE directory on your host, inside the visionWARE root 
       directory you will find 'tftp' directory that contain application called 
       "tftpd32.exe" . Run this application and the TFTPD32 window will popup. 
       In the TFTPD32 window press on the 'Settings' button. This will invoke 
       the 'Tftpd32: Settings'. Go to the 'Base Directory' group and inside the 
       edit box type the full path to your vxWorks image, or use the 'Browse' 
       button to navigate to there.

    4. Power up your PPMC74xx and press any key within 3 seconds from the 
       serial terminal to abort the boot script. This will display a ">BKM>"
       prompt.

    5. Type the 'shell' command and press enter. Now you should get the 
       following line: "File System Sectors (256K each) = 8 >" Press enter. 

    6. Next line will be: "Boot Delay (seconds) = 1 >" . Here you need to 
       specify the desired delay value and press enter.

    7. Next line will be: "Boot Script = >" . Here you need to give the boot 
       script command. Please type the following if you are using vWARE 1.10:
      
      "load \\host\vxWorks.bdx!osboot RAM!go 100000" . Where 'host' is the 
      host name, and press enter.

      Or if you are using vWARE 2.0 please type the following:

      "load \\host\vxWorks.bdx!launch 100000"
      
      Note(s):

    	** It is very important to keep the same space between the "load"
           command and the host name "\\host".

    	** It is very important to keep the same space between the "osboot" 
           command and the "RAM".

    	** The host name should be the same as specified in the 
           "Remote System 1 Name" line.
    
    8. Next line will be "MAC Address = 00-A0-11-22-23-E8 >" . If you want to 
       change the target MAC address, type it now and press enter, else press 
       just enter.

    9. Next line will be "IP Address = 0.0.0.0 >". Type your target IP address. 
       For example: 192.168.199.0 and press enter.

   10. Next line will be "Subnet Mask = 0.0.0.0 >". If you want to use subnet 
       mask, type it now and press enter, else just press enter.

   11. Next line will be "Default Gateway = 0.0.0.0 >". If you want to use 
       default gateway, type it now and press enter, else just press enter.

   12. Next line will be "Remote System 1 Name = >". Here you need to type the 
       same host name you specified in the "Boot Script" line.

   13. Next line will be "Remote System 1 IP = >". Here you need to type your 
       host IP address. For example: 192.168.199.1 and press enter.

   14. Next line will be "Remote System 2 Name =  >". Just press enter.

   15. Next line will be "Remote System 3 Name =  >". Just press enter.

   16. Next line will be "Remote System 4 Name =  >". Just press enter.

   17. Next line will be "Command Channel = 0: Serial >". Just press enter.

   18. Now you will get the following message: 

       Saving changes will generate a reboot.
       Save Changes (y/n)?

       Press 'y' to save the changes.

   19. Now the changes are saved and the board will restart visionWARE and boot 
       vxWorks, after a few seconds you will get the following messages:
.CS
    Wind River visionWARE v2.00 HSI PPMC 7xx
    Wind River HSI [phone]
    Build #14, 09/11/01 08:43:14
        
    MAC : 00-11-22-33-44-55 IP : 192.168.199.0
    Type "shell" to set IP and/or MAC addresses
    Type "help" to see available commands
 
    Press a key in the next <6> seconds to preempt boot script
    Booting from script...
        
    load \\host\vxWorks.bdx!launch 100000

    >RUN>Attached TCP/IP interface to fei unit 0
    Attaching interface lo0...done


                     VxWorks

    Copyright 1984-2001  Wind River Systems, Inc.

                CPU: Motorola PowerPC - Wind River PPMC7400 Board
            VxWorks: VxWorks5.5
        BSP version: 1.2/2
      Creation date: Oct 23 2001
                WDB: Ready
.CE


For more information regarding visionWARE boot services and the 
visionWARE development kit, please refer to the visionWARE manuals, 
located on the CD that was shipped with your board.

.SS "BOOT DEVICES"
The supported boot device(s) is(are):
.CS
	fei  - 100\10BaseT Ethernet
.CE

.SH "FEATURES"
This section describes the support and unsupported features of the wrPpmc74xx

.SS "Supported Features"
.PP
The supported features of the PPMC74xx board are:
        7400/7410 processors with the AltiVec extension.
	Board Initialization.
	MMU support.
	Cache support.
	L2 Cache support.
	Decrementer timer is used to implement a System Clock.
	Timestamp clock.
	NS 16550 UART (Consol channel).
	FEI 10\100BaseT Intel 82557/9/0 PCI Ethernet device supporting 10\100Base-T protocol (5V & 3.3V PCI).
	MPC107 Programmable Interrupt Controller.
	MPC107 PCI bridge.
	MPC107 Memory Controller.
	SDRAM upgrade (64 to 256 MB Memory SODIMM).
	FLASH 4MB On board.
	Saving boot parameters on the flash when using vxWorks bootrom.

.SS "Unsupported Features"
.PP
The items not supported on the PPMC74xx are:
	Other MPC107 peripherals.
	Aux Clock.

.SH "HARDWARE DETAILS"
This section documents the details of the device drivers and board
hardware elements for the PPMC74xx.

.SS "Devices"
The chip drivers included are:

.TS
expand tab(|);
l lw(4i)
l lw(4i) .
sysNvRam.c|Generic non-volatile RAM library
ppcDecTimer.c|system clock and timestamp driver using PPC decrementer
amd29LV800TMem.c|Flash access routines
sysMpc107Epic.c|Motorola MPC107 PIC interrupt controller driver
sysMpc107Pci.c|Motorola MPC107 PCI bus bridge chip driver
pciConfigLib.c|PCI Configuration Space Access Library
pciConfigShow.c|PCI Configuration Space Display Library
pciAutoConfigLib.c|PCI Bus Auto-configuration Library
sysSerial.c|prepares serial driver ns16550sio
sysNet.c|prepares PCI Ethernet driver "fei"
sysACache.s|PowerPC 750/755/7400/7410 L2 cache library
ns16550Sio.c|NS 16550 UART driver (serial ports 1)
fei82557End.o|Intel 82550, 82557, 82558, 82559 END driver
.TE

The BSP configures NS 16550 UART to implement a console device and the 
FEI82557 as an Ethernet.

.SS "Support for L1 Cache Locking"
L1 cache locking is available for MPC750, MPC755, MPC7400 and
MPC7410. The cache lock routine can be used to lock the entire data
or instruction cache with a specified memory region. 

.SS "Support for L2 Cache"
L2 Cache is available for MPC750, MPC755, MPC7400 and MPC7410. Callback function
pointers for L2 cache Global Invalidation, L2 Cache Enable, L2 Cache
Flush and L2 Cache Disable are intialized in sysHwInit().

.SS "Support for L2 Cache Locking"
L2 cache locking is supported on MPC750, MPC755, MPC7400 and MPC7410. On these
CPUs L2 is implemented as an unified cache. The L2 cache lock library
can be used to lock data or instructions in the L2 cache.

.SS "Support for AltiVec"
MPC7400 and MPC 7410 support an altiVec sub-system that implements
vector processing. Support for altiVec is now available, but an
altiVec aware compiler must be used to create applications that
use altiVec instructions. The altiVec support can be enabled by
defining INCLUDE_ALTIVEC in config.h

.SS "Default Memory Map"
.CS
        Memory Map from CPU point of view

Chip Select	    Start               Size         Access to
---------------------------------------------------------------------
SDRAMCS0 (R/W)	0x0                 64MB (min)   SDRAM SODIMM
RCS0 (R/W)	0xFFC00000	     4MB         On Board FLASH
RCS3 (W)	0x78000000           ---         User LED's (Register)
RCS2 (R/W)	0x7C000000	     ---         UART (Register)
RCS1 (R/W)	0xFF000000           ---         MAIL BOX (Register)
     (R/W)      0xFCE00000           ---         EUMB
     (R/W)      0x80000000         128MB         PCI prefetchable memory
     (R/W)      0x88000000         128MB         PCI non-prefetchable memory
     (R/W)      0xFE000000          16MB         PCI IO
.CE

.SS "Shared Memory"
.PP
N/A

.SS "Using the vPROBE/vICE to download the vxWorks image directly to RAM"
when using vPROBE/vICE to download the vxWorks image directly to RAM you need
to remember that the CS & main CPU initialization are done by the emulator and 
not by the bootrom (romInit.s), because the reset symbol is "sysInit" and not
the reset vector (0xFFF00100). Because this the code will execute only the 
module "sysALib.s", and it will not execute the module "romInit.s". If you will 
not use the correct register file the vxWorks image will not run correctly.

.SS "SDRAM Size"
.PP
Initial boards and bsp are supplied with a 64Meg SDRAM SODIMM, which can be
expanded to 256Meg by the user.

Note:

	** When expanding the RAM to 256Meg, changes need to be done in the BSP
	   in order to change the chip select to support 256Meg.

The BSP divides the 64Meg SDRAM into two 32Meg sections. The reason for this 
has to do with the EABI compilation option of a 24 bit address. The default
compilation options generates a 'bl' for branch instructions. This 
increases performance, but places a 32Meg address limit on the code.
  
There are two 'work arounds' to this limitation.
 
    1.) recompile all the source with the -mlongcall compilation flag
    2.) add remaining 32Meg to the memory pool vi the memAddToPool() function.
  
Option #1 would require all the libraries, driver, and the BSP to be 
recompiled with the -mlongcall compiler option. This results in a number
of code changes; the most obvious code change is branches are implemented
via brlr instruction verses the bl instruction.
  
Option #2, the perferrable options, requires the USER_RESERVED_MEM and
the memAddToPool() constructs be used to specify the remaining 32Meg
to be added
to the memory pool. Consult WindTech Note WTN41 for details on specifying
user memory.


.SS "Network Configuration"
All boards come with a PCI Ethernet card which is 10baseT and 100baseT
compatible. The Ethernet card uses an RJ45 (twisted pair) jack and can be 
used with either 10baseT or 100baseTX. The Ethernet driver automatically 
senses and configures the port as 10baseT or 100baseT.

.SS " NVRAM Support" 
This BSP emulate NvRam via a the On Board FLASH device.
There are a few user parameters associated with this device. The parameters are 
located in the 'wrPpmc74xx.h' file.

.SS "Ethernet Address"
The Media Access Control (Ethernet) address for each port is obtained from a
serial ROM contained in the Intel 82557/9 chip. The Ethernet address should 
be written on the card itself, 12 digit number in Hex format. If it's not 
written on the card, you can use the 'arp -a' command from the host