.IP "Running the VxWorks Boot ROM Program"

At this point, the on-board local flash memory is programmed with the new 
boot program.  To execute this new boot program, turn the board off and on, 
possibly disconnecting the visionPROBE in the process.  If the 
visionPROBE I/II or the visionICE I/II is still connected to the board, 
the processor is stopped at the first instruction to execute.  If either the 
visionICE or the JTAG probe are not connected, the boot ROM image will execute 
and prompt the user via the serial port to download a VxWorks image.
.LP

To load VxWorks, and for more information, follow the instructions in the 
.pG "Getting Started".


An alternative way to load vxWorks is through vWARE.

.SS "Using visionWARE to run VxWorks"
The following section explains how to launch VxWorks using visionWARE as a boot loader.

Complete the following steps:
	  
    1. Connect your SBCARM7 serial channel (COM1) to a host running a
       terminal program at 9600 baud (for example, '
       HyperTerminal') using the supplied serial cable.

    2. Connect your SBCARM7 100\10Base-T RJ45 connector (JP13) port to
       a network hub.

    3. Open a 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 and 
	   locate the 'tftp' directory in the visionWARE root directory.  
       The 'tftp' directory contains an application called 'tftpd32.exe'. 
	   This application launches the TFTPD32 window. In the TFTPD32
       window, click the 'Settings' button. This invokes 
       'Tftpd32: Settings'. Go to the 'Base Directory' group and 
       type the full path to your VxWorks image inside the edit box,
       or use the 'Browse' button to navigate to your image.

    4. Power up your SBCARM7 and, from the serial terminal, press 
	   any key within 1 second to abort the boot script. This displays
       a '>BKM>' prompt.

    5. Type the 'shell' command and press enter. The following line 
	   appears: 'Boot Delay (seconds) = 6 >' . Specify the desired 
	   delay value and press enter.

    6. The next line is: ' Boot Script = >' . Type the boot script 
	   command. For example, if your host computer was named
      'BOS-GILH', you would type the following:
      
      "load \\\\BOS-GILH\vxWorks.bdx!launch 6000"

      and then press enter.
      
      Note(s):

        ** It is very important to keep the same space between the
           'load' command and the host name '\\\\BOS-GILH'.

        ** It is also very important to keep the same space between 
		   the 'launch' command and the '6000'.

        ** The host name should be the same as specified in the
           "Remote System 1 Name" line.
    
    7. The next line is "MAC Address = 00-A0-1E-08-04-9A >" . If you
       want to change the target MAC address, type it now and press
       enter, else just press enter.

    8. The next line is "IP Address = 0.0.0.0 >" . Type your target
       IP address. For example: 24.42.124.92, and press enter.

    9. The next line is "Subnet Mask = 0.0.0.0 >" . If you want to
       use a subnet mask, type it now and press enter, else just press
       enter.

   10. The next line is "Default Gateway = 0.0.0.0 >" . If you want
       to use a default gateway, type it now and press enter, else just
       press enter.

   11. The next line is "Remote System 1 Name = >" . Type the same 
       host name you specified in the 'Boot Script' line.

   12. The next line is "Remote System 1 IP = >" . Type your host 
       IP address. For example: 24.42.124.94 and press enter.

   13. Press enter after each of the following lines:
       "Remote System 2 Name = >"

       "Remote System 3 Name = >"

       "Remote System 4 Name = >"

   14. The following message appears:

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

       Press 'y' to save the changes.

The changes are now saved. The board will restart visionWARE and 
boot VxWorks. After a few seconds, the following messages appear:

.CS
    Wind River visionWARE v2.00 EAR for SBC-ARM50100
    Wind River HSI +1(781) 828 5588
    Build #6, 04/17/01 16:16:56
 
    MAC : 00-A0-1E-08-04-9A IP : 24.42.124.92
    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 \\BOS-GILH\vxWorks.bdx!launch 6000

    >RUN>慉ttached TCP/IP interface to sng unit 0
    Attaching interface lo0...done


                     VxWorks

    Copyright 1984-2001  Wind River Systems, Inc.

                CPU: KS32C50100 for WindRiver SBC ARM7
            VxWorks: 5.4.1
        BSP version: 1.2/13
      Creation date: Jul 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-ROM shipped with your board.

.SH "BOOT DEVICES"

The only supported boot device is:

.TS
expand;
1 1 .
'sng' | 100\10BaseT Ethernet (in the Samsung CPU ASIC)
.TE 

.SS "Jumpers and Switches"

No jumpers are relevant to VxWorks configuration. However, to
get the board running with the default configuration, the following
jumpers and switches must be set as follows:

.TS
expand;
1 1 .
Jumper Settings   
_
JP4 | Close
JP5 | 1-2, 3-4, 5-6, 7-8
JP11 | All Open
JP12 | 5-6, 9-10
JP14 | 1-3, 2-4
JP16 | 1-3, 2-4
JP17 | 1-3, 2-4
JP23 | 1-2, 3-4, 5-6
JP24 | 1-2, 3-4, 5-6 
 | 
** NOTE: | If the jumper contains more then two pins the pin numbers
         | that are open will not by specified here, only the pin
         | numbers that are closed (connected) are specified.
.TE


.TS
expand;
1 1 1 1 1 1 1 1 1 .
Switch Settings
-
| S4-1 Open | | S3-1 Close | | S5-1 Close | | SW3-1 On
| S4-2 Open | | S3-2 Close | | S5-2 Open  | | SW3-2 Off
| S4-3 Open | | S3-3 Close | | S5-3 Open  | | SW3-3 Off
| S4-4 Open | | S3-4 Close | | S5-4 Open  | | SW3-4 Off
| S4-5 Open | | S3-5 Close | | S5-5 Open  | | SW3-5 Off
| S4-6 Open | | S3-6 Open  | | S5-6 Close | | SW3-6 On
| S4-7 Open | | S3-7 Close | | S5-7 Close
| S4-8 Open | | S3-8 Close | | S5-8 Close
.TE

.SH "FEATURES"

This section describes the supported and unsupported features of the SBCARM7

.SS "Supported Features"

The supported features of the SBCARM7 board include:

    - Samsung's KS32C50100 microprocessor (based on an ARM7TDMI Core)
    - Little-Endian or Big-Endian byte order
    - ARM or Thumb mode
    - Board Initialization
    - The two KS32C50100 32-bit timers used to implement a System clock,
      Aux clock, and Timestamp clock.
    - The first KS32C50100 UART channel for COM1 (Console channel).
    - The KS32C50100 Ethernet controller as an Ethernet device
      supporting 100\10BaseT protocol.
    - The KS32C50100 Interrupt Controller.
    - 8 MB on-board DRAM.
    - 2 MB on-board flash.
    - 50 MHz CPU speeds.
    - Cache support.
    - Emulating NvRam on flash.

.SS "Unsupported Features"

The items not supported on the SBCARM7 board are:

    - IIC support.
    - HDLC support.
    - CAN Bus support.

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

.SS "Devices"

The device drivers included are:

.TS
expand;
1 1 .
Device Drivers
_
sngks32cTimer.c | SNGKS32CARM7 timer driver
sngks32cIntrCtl.c | SNGKS32CARM7 interrupt controller driver
sngks32cSio.c | SNGKS32CARM7 serial driver
'sngks32cEnd.o' | SNGKS32CARM7 Ethernet driver
sysSerial.c | serial device initialization routines
sysEnd.c | END network driver support routines
sysLcd.c | SBCARM7 LCD driver
sysLed.c | SBCARM7 User LED driver
nullNvRam.c | dummy non-volatile RAM library
.TE

The timer driver, 'sngks32cTimer', implements a system clock,
auxiliary clock, and timestamp clock using the two SNGKS32CARM7 32-bit
timers. This BSP configures the SNGKS32CARM7 first UART to implement a
console device and the SNGKS32CARM7 Ethernet controller to implement
an Ethernet port.

.SS "Default Memory Map"

The following is the memory map from the CPU point of view (before RAM and 
ROM are swapped in 'romInit' early during boot ROM execution).

.TS
expand;
1 1 1 1 1 .
Chip | Select | Start | Size | Access to
_
nRCS0 | R/W | 0x0 | 2 MB | External flash Boot ROM
nRCS2 | R/W | 0x03FB0000 | 8 KB | External EEPROM
nRCS3 | R/W | 0x03FC0000 | 64 KB | External Register (MailBox)
nRDCS0 | R/W | 0x01000000 | 16 MB | External SDRAM
nECS1 | R | 0x03FD4000 | 256 Byte | External Register (8 Switch Bank)
nECS1 | W | 0x03FD4000 | 256 Byte | External Register (8 LED Bank)
nECS1 | R | 0x03FD4100 | 16 KB | External Display (LCD)
nECS2 | R/W | 0x03FD8000 | 16 KB | External CAN 1 controller
nECS3 | R/W | 0x03FDC000 | 16 KB | External CAN 2 controller
' ' | R/W | 0x03FE0000 | 8 KB | Internal SRAM
' ' | R/W | 0x03FF0000 | 24 KB | Internal Registers
.TE

.SS "Shared Memory"
Does not apply.

.SS "Interrupts"
21 interrupt levels are provided:

.TS
expand;
1 1 .
Interrupt Levels
_
0 | External Interrupt 0
1 | External Interrupt 1
2 | External Interrupt 2
3 | External Interrupt 3
4 | UART 0 Transmit Interrupt
5 | UART 0 Receive and Error Interrupt
6 | UART 1 Transmit Interrupt
7 | UART 1 Receive and Error Interrupt
8 | GDMA channel 0 interrupt
9 | GDMA channel 1 interrupt
10 | Timer 0 Interrupt
11 | Timer 1 Interrupt
12 | HDLC channel A Tx interrupt
13 | HDLC channel A Rx interrupt
14 | HDLC channel B Tx interrupt
15 | HDLC channel B Rx interrupt