VxWorks BSP Reference : wrScout
scout - Wind River (Motorola) Scout
This manual entry provides board-specific information necessary to run VxWorks for the wrScout BSP. Please read the section "Getting the board running vxWorks" in order to configure the board to run vxWorks.
Getting the board running vxWorks This section will guide you step by step how to get vxWorks running on this board.
1. Setting the board Jumpers & Switches:
In order to get the board running with the default configuration. the
following jumper's and switch's need to be set as follows:
_____________ | Jumpers | |-------------| | J13 Close | | J14 Close | | J15 Close | | J17 Open | | J19 Open | | J21 Open | |_____________|2. Creating a bootrom_uncmp.hex:
2.1 Launch Tornado II, go to the "Build" menu and choose the option
"Build Boot ROM...".
2.2 the "Build Boot ROM" window will popup, in the "Select a BSP:" column
choose the "wrScout", and in the "Select an Image to build:" column
choose "bootrom_uncmp.hex" and press the "OK" button.
2.3 After the build process will finish successfully (You will see "Done" in
the "Build window" without error), you will have the bootrom_uncmp.hex in
your BSP directory "$(WIND_BASE)/target/config/wrScout".3. Programming bootrom_uncmp to SCOUT FLASH:
If you are using visionCLICK please follow the instruction in section 3.1
if you are using SingleStep please follow the instruction in section 3.23.1 Using visionCLICK:
3.1.1 Install the visionPROBE II or visionICE II and power it on.
Connect the JTAG interface cable from the visionPROBE II or
visionICE II into the SCOUT board JTAG (J19 The MPC75x JTAG Port)
connector.Once all the connections have been made, power up the SCOUT
board and start the visionCLICK executable on the host.3.1.2 Configure the visionCLICK project:
The "Welcome To visionCLICK" window will appear .In this window
press on the "Configure" button, This will invoke "PROJECTS/LOAD"
window. In this window press on the + left to the
"PowerPC_C_Demo.prj".This will show you the project configuration.
Point with the mouse cursor on the "Microprocessors" option and
press the right button and choose the type of CPU you have on your
board. For example: "PowerPC->MPC7xx->MPC750" for Scout board with
MPC750 or "PowerPC->MPC7xx->MPC755" for Scout board with MPC755.
Verify that the "Target Control" option point to visionPROBE for
visionPROBE II or visionICE for visionICE II, Also switch to the
"Communications" TAB and verify that the "Normal Port/Rate" &
"Download Port/Rate" suite your connection. for example: "LPT1"
for visionPROBE II. Now press the "Save" button at the bottom of
the window and after it on the "Activate" button.3.1.3 Verifying that the Master CPU setting is correct:
Once the ">BKM>" or the ">ERR>" prompt appears we need to verify
that the Master CPU setting is correct and MPC8260 used as slave.
To do this type "CF" in the "Terminal" window and press Enter.
The following line:
Target CPU TAR[603E,EC603E,603P,603R,740,750,755,7400] = 755
This line will tell you the CPU setting. If your CPU setting is
deferent use the "CF" command to set it correct. For example if
the CPU setting is equal to 750 and our board contain 755 then
type the following command in the terminal window "CF TAR 755"
and press enter.3.1.4 Setting the MPC8260 to be used as slave:
In the "Terminal" window type "SC GRP ERASE" and press enter.
After getting back the ">BKM>" prompt type the following command:
"CF SLAVE 8260" and press enter. After getting back the ">BKM>"
prompt type the command "CF" and press enter, the following line
will be displayed:
Target CPU( SLAVE ) SLAVE[NONE,8260] = 8260
This line will tell you if the MPC8260 is used as a slave. If
the value is set to "NONE", then you need to reapet this step
again.3.1.4 Program visionPROBE II / visionICE II with the proper register
setting for the SCOUT board:Go to the "Tools" menu and select the
"Log Output/Playback Scripts" option. The "Record / Playback"
dialog box will popup. In this dialog box go to the
"Playback Commands From File" group and press on the "Browse"
button. Navigate your self to the location of the following
register file: "scout64MB.reg" for the board with 64MB SDRAM or
"scout16MB.reg" for the board with 16MB SDRAM. The file located
in the visionCLICK installation. After choosing the register file
press on the "Open" button to confirm the selected reg file. You
will return back to the "Record / Playback" dialog box. Now press
on the "Start" button located in the same group. In the "Terminal"
window you can see that the visionCLICK is running the script.
When visionCLICK will finish the playback you will get back the
">BKM>" or the ">ERR>".3.1.5 Get into Background Mode:
Execute the "IN" command to reset the board and initialize it with
the register setting.
IN
This command is the reset command to initialize the board.3.1.6 Converting the bootrom_uncmp.hex to bootrom_uncmp.bin:
3.1.6.1 In visionCLICK, choose "Convert Object Modules" from the
"Tools" menu. The "CONVERT BINARY AND SYMBOL OBJs" dialog
box will pop up.Select "All Files" in the "Files of Type"
box. Go to the "Select Input Object Module To Convert"
group and navigate to the file "bootrom_uncmp.hex"
located in:
"$(WIND_BASE)/target/config/wrScout/bootrom_uncmp.hex"3.1.6.2 In the group "Binary Downloadable Objects Modules" check
the "Create Flat BIN File For Flash Programming".
"In Range Of 0x" editbox, enter 0 for the start address,
and in the "To 0x" editbox, enter "FFFFFFFF".3.1.6.3 Make sure that all the other check box are unchecked.
Press the "Convert" button. Close the terminal window
when the conversion completes.3.1.7 Programming the SCOUT Flash:
In visionCLICK, select "Program Flash Devices" from the Tools
pull-down menu. This will invoke the "TF FLASH PROGRAMMING"
window. If you are not using visionCLICK, you can also invoke
this window using the "visionICE Utilities Panel" and follow the
steps below:3.1.7.1 Click the "Select" in the "Flash Card or PC Host File
Name and Path" group. The "CHOOSE A FILE FROM HOST PC"
dialog box will popup. In the edit box enter the full path
to the location of the "bootrom_uncmp.bin", or use the
"<--Browse" button to browse to the file location. Go to
the "+/- Bias" group and enter the number "FFF00100" in
the edit box. Now click the "OK" button, this will bring
you back to the "TF FLASH PROGRAMMING" dialog box.3.1.7.2 In the "Programming Algorithm" group in, the edit box
press on the "Select" button, and select one of the
following Flash devices:The 16MB FLASH SIMM: "AMD 29F016/17(2048 x 8) 8 Devices"
3.1.7.3 Set the proper address of the Flash to "FFF00000", check
the "Erase All" radio button,and set the
"Available RAM Workspace" setting to "0F008000", set the
"Bytes Of Target RAM Required" to "4000".3.1.7.4 Press the "Erase and Program" button.
3.1.7.5 Now the Flash memory is programmed with the new boot
program.3.2 Using SingleStep for vision:
3.2.1 Install the visionPROBE II or visionICE II and power it on.
Connect the JTAG interface cable from the visionPROBE II or
visionICE II into the SCOUT board JTAG (J19 The MPC75x JTAG Port)
connector.Once all the connections have been made, power up the SCOUT
board and start the SingleStep for vision executable on the host.3.2.2 Configure the SingleStep project:
3.2.2.1 Go to the "File" menu and choose the
"Start Debug Session..." .3.2.2.2 The "Debug" dialog box will popup, In the "Connection" tab
choose the visionPROBE option & the correct LPT port if
you are using visionPROBE, or visionICE & enter the
emulator IP address if you are using visionICE.3.2.2.3 In the "Processor" tab choose the "MPC750" for Scout with
MPC750 or "MPC755" for Scout with MPC755.3.2.2.4 In the "Register" tab choose the option
"Use vision-style register window with REG file" and then
browse to the location of the file "scout64MB.reg" for
board with 64MB SDRAM or "scout16MB.reg" for board with
16MB SDRAM, and choose it. The "scout64MB.reg" or
"scout16MB.reg" file should be in the SingleStep
registers directory.3.2.2.5 In the "File" tab choose the "Debug without a file"
option.3.2.3 Get into Background Mode:
3.2.3.1 Now in the "File" tab press OK.
3.2.3.2 Now should get the "Debug Status" dialogbox and in the
"Debug Session" field you should have in green
"Started Successfully", press the "Close" button.3.2.3.3 Now go to the "Command" button in the toolbar and press on
it. The "Command" Window will popup, the prompt in the
window will be "SingleStep". Bring the mouse cursor above
the "Command" window and press the right button. A menu
will popup, choose the "VisionShell(vsh)" option. Now the
prompt in the window will be ">BKM>". If the prompt is
">ERR>" execute the "IN" command to reset the board and
initialize it with the register setting.
INThis command is the reset command to initialize the board.
After you got the ">BKM>" prompt again continue with the
instruction in the next section.3.2.4 Verifying that the Master CPU setting is correct:
Once the ">BKM>" or the ">ERR>" prompt appears we need to verify
that the Master CPU setting is correct and MPC8260 used as slave.
To do this type "CF" in the "Command" window and press Enter.
The following line:
Target CPU TAR[603E,EC603E,603P,603R,740,750,755,7400] = 755
This line will tell you the CPU setting. If your CPU setting is
deferent use the "CF" command to set it correct. For example if
the CPU setting is equal to 750 and our board contain 755 then
type the following command in the terminal window "CF TAR 755"
and press enter.3.2.5 Setting the MPC8260 to be used as slave:
In the "Command" window type "SC GRP ERASE" and press enter.
After getting back the ">BKM>" prompt type the following command:
"CF SLAVE 8260" and press enter. After getting back the ">BKM>"
prompt type the command "CF" and press enter, the following line
will be displayed:
Target CPU( SLAVE ) SLAVE[NONE,8260] = 8260
This line will tell you if the MPC8260 is used as a slave. If
the value is set to "NONE", then you need to reapet this step
again. Once the prompt appears, reset the board and the emulator
with the following command:
>BKM> IN
After you got the ">BKM>" prompt again continue with the
instruction in the next section.3.2.6 Converting the bootrom_uncmp.hex to bootrom_uncmp.bin:
3.2.6.1 Go to the menu and choose "Tools" and
"Vision Flash Utility..." .3.2.6.2 The "Flash Programming Window" will popup. Go to the
"Files" tab, press the "Convert" button.3.2.6.3 The "File Convertion" window will popup. In the
"Enter new start address" edit box type "0x0" and in the
"Enter new end address" edit box type "0xFFFFFFFF".3.2.6.4 Now press the "Convert" button. After the convert operation
finished, you will see it in the "Convert Result" section
press the "Close" button.3.2.7 Programming the SCOUT Flash:
3.2.7.2 In the "Flash Programming Window" window. Go to the
"Configuration" tab, & choose the following Flash device:The 16MB FLASH SIMM: "AMD 29F016/17(2048 x 8) 8 Devices"
In "Flash Bank" group for the "Start:" enter "FFF00000".
In the "RAM Workspace" group for the "Workspace Start at:"
enter "0F008000" and for the "Workspace Size:" enter
"4000".3.2.7.3 Now switch to the "Files" tab and press the "Add" button.
The open dialogbox will popup, browse to
"$(WIND_BASE)\target\config\wrScout "bootrom_uncmp.bin" file. Now after getting back to the
"Files" tab you will see the full path to the selected
file in the "Binary Files" group. Move the mouse curser
above the line that showing the full path in the
"Binary Files" group and press the right button to mark
this line. Now press the "Toggle Enable" button to select
this binary file. Make sure that the line is still marked,
and press the "Edit" button on the right. The "File Edit"
dialog box will popup. In the "Enter new start address"
edit box enter "0xFFF00100" and press the "OK" button.3.2.7.4 Now go to the "Program" tab and press the "Erase/Program"
button.3.2.7.5 Now the Flash memory is programmed with the new boot program.
4. Running the VxWorks Boot ROM program:
4.1 Disconect visionPROBE II or the visonICE II if it still connected to the
board, because it still connected to the board in some case it can stop
the processor at the first instruction.4.2 Connecting the Ethernet channel and the serial channel:
4.2.1 First, connect the supplied serial cable with the board. On
one said connect the RJ11 to 9 Pin addapter connector to the
RS-232 (J12) port on the the SCOUT, 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, connect a standard Ethernet cable to the the RJ45 (J11)
connector on the SCOUT board.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.
bootrom_uncmp.hex is provided with this BSP. The bootrom_uncmp is configured to a ROM base address of 0x0 and includes, also it's configured to use the 16MB SIMM FLASH and FCC2 10/100BaseT Ethernet as default boot device and SCC1 as console device and 50MHz Oscillator to drive the 8260 CPM at 100MHz.. The hard reset configuration word must be programmed separately at the flash base address of 0xFE000000 and at offsets 0x0, 0x8, 0x10 and 0x18, see Wind River H.S.I Application Note AN-0039.
The following section will explain how to launch VxWorks using visionWARE as a boot loader. Please follow the steps below:Note: Before using vsionWARE you need to verify that visionWARE is programmed
to you FLASH. If visionWARE is not exist on your FLASH, please see
"Programming bootrom_uncmp to SCOUT FLASH" section how to program the
Scout Flash, and instead of programming the "bootrom_uncmp.bin" program
the "vWARE.bin" file.1. Connect your Scout serial channel (COM1) to a host running terminal
program at 9600 baud rate (For example "HyperTerminal") using the
supplied serial cable.2. Connect your Scout 100\10Base-T (J11) 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 Scout 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: "Command Channel = 0: serial >" 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:
"load \host\vxWorks.bdx!launch 100000" . Where "host" is the host name,
and press enter.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 "launch"
command and the "100000".** The host name should be the same as specified in the
"Remote System 1 Name" line.8. Next line will be "Prompt String = BKM >" . Press enter.
9. Next line will be "MAC Address = 00-00-00-00-00-00 >" . If you want
to change the target MAC address, type it now and press enter, else
press just enter.10. Next line will be "IP Address = 0.0.0.0 >". Type your target IP address.
For example: 24.42.124.92 and press enter.11. 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.12. 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.13. Next line will be "Remote System 1 Name = >" . Here you need to type the
same host name you specified in the "Boot Script" line.14. Next line will be "Remote System 1 IP = >" . Here you need to type your
host IP address. For example: 24.42.124.94 and press enter.15. Next line will be "Remote System 2 Name = >" . Just press enter.
16. Next line will be "Remote System 3 Name = >" . Just press enter.
17. Next line will be "Remote System 4 Name = >" . 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:Wind River visionWARE v2.00 for the Scout Board MAC : 00-00-00-00-00-00 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 <1> seconds to preempt boot script Booting from script... load \\host\vxWorks.bdx!launch 100000 \>Attached TCP/IP interface to motfcc unit 0 Attaching interface lo0...done VxWorks Copyright 1984-1998 Wind River Systems, Inc. CPU: MPC755(Master) and MPC8260(Slave) -- Wind River. Scout Board VxWorks: 5.5 BSP version: 1.2/4 Creation date: Jun 28 2001 WDB: Ready.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.
The supported boot device(s) is(are):motfcc - MII 10/100BaseT Fast Ethernet (FCC2)
This section describes the support and unsupported features of the Scout
The supported features of the Scout board are:
750/755/7400 (with the AltiVec extension) Master processors
8260 Slave processor
Board Initialization
MMU support
Cache support
Decrementer timer, is used to implement a System Clock.
MPC8260 SCC1 a UART for COM1 (Consol channel).
MPC8260 FCC2 Port as an Ethernet device supporting 10/100Base-T protocol.
MPC8260 TIMER2 as an 16-bit auxiliary clock.
MPC8260 TIMER3 and TIMER4 are cascaded into a free-running 32-bit timer for timestamp support.
MPC8260 Interrupt Controller.
MPC8260 Baud Rate Generators as required for SCC1.
64MB SDRAM upgrade socket (32, 64, 128 MB DIMM's) on 60x bus. (Supporting 64 & 128 requires hardware modification)
16MB FLASH upgrade socket (8, 16 MB SIMM's) on 60x bus.
4MB SDRAM on local bus.
MPC8260 CPM speed 100, 133.
The items not supported on the Scout are:
Other MPC8260 peripherals
Saving boot parameters on the flash when using vxWorks bootrom
Support for the MPC750/755/7400 L2 cache (hardware is available but the BSP don't support it)
L1 cache locking is available for MPC8260. The cache lock routine can be used to lock the entire data or instruction cache with a specified memory region.
This section documents the details of the device drivers and board hardware elements for the Scout.
The chip drivers included are:
m8260Sio.c - MPC8260 SCC1 serial driver m8260IntrCtl.c - MPC8260 interrupt controller driver m8260Timer.c - timer driver for the MPC7x5 Decrementer clock and MPC8260 timers m82xxDpramLib.c - DPRAM memory driver. motFccEnd.o - FCC Ethernet END driver miiLib.obj - Media Independent Interface libraryThe BSP configures SCC1 as a UART to implement a console device and the FCC2 as an Ethernet. SCC1 is used as a console device. FCC2 is used as a 10/100Base-T Ethernet port.
MPC7400 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
Memory Map from CPU point of view
Chip Select Start Size Access to
------------------------------------------------------------------
CS0-8 (R/W) 0xFE000000 16MB SIMM FLASH memory (CS 0 for bank 0 & CS8 for bank 1)
Using 16MB SIMM's, 16MB will wrap around.
For Example: 0xFE000000 = 0xFF000000
CS1 (R/W) 0xFC000000 8Bit BCSR(0)
CS1 (R/W) 0xFC000008 8Bit BCSR(1)
CS1 (R/W) 0xFC000010 8Bit BCSR(2)
CS1 (R/W) 0xFC000018 8Bit BCSR(3)
CS2-3 (R/W) 0x0 64MB DIMM SDRAM
CS4 (R/W) 0x04000000 4MB SDRAM on Local bus
0x0F000000 64KB MPC8260 internal memory resources, DPRAM
In order to use the 66Mhz Oscillator instead of th 50Mhz you need to follow those steps:
1. Plug 66Mhz Oscillator in Y2 (This is the Oscillator socket).
2. In "config.h" the following macro need to be changed:
From:
#define OPERATING_FREQUENCY OSCILLATOR_50MHZ
To:#define OPERATING_FREQUENCY OSCILLATOR_66MHZ
3. Rebuild the bootrom and rebuild the VxWorks image.
The BSP configures to use FCC2 as an Ethernet port. The name "motfcc" should be specified as the boot device to the boot ROMs when booting vxWorks over that interface. The Fast Ethernet Controller (FCC) makes available fast Ethernet connectivity through RJ45 connector. The BSP configures to use END-style network driver.
The Scout boards do not have a unique Ethernet hardware address assigned to each board. A unique address is absolutely necessary if the user wishes to connect the board to a network. Thus, the user must provide a suitable 6 byte Ethernet address for each board used on a network. The default Ethernet Address is specified in the "wrScout.h" The following relate to the storage of the Ethernet address:/* Ethernet MAC Address Parameters */ #define CUST_ENET3 0x01 /* Customer specific portion of MAC address */ #define CUST_ENET4 0x02 #define CUST_ENET5 0x03The first three bytes (0x00, 0xa0, 0x1e) are a Wind River specific prefix that should be kept as-is. If for some reason you need to change them, in "config.h" change the following macros:#define WR_ENET0 0x00 /* Wind River specific portion of MAC (MSB->LSB) */ #define WR_ENET1 0xa0 #define WR_ENET2 0x1e #define ENET_DEFAULT 0x00a01e00Note:
The "ENET_DEFAULT" macro should contain the same number as the three
"WR_ENETx" macros. For example :#define WR_ENET0 0x11 #define WR_ENET1 0x22 #define WR_ENET2 0x33 #define ENET_DEFAULT 0x11223300The user must change the last three bytes from 0x03, 0x02, 0x01 to three unique bytes (i.e., bytes not used by any other Wind River Ethernet connection on your net). Check with your system administrator if you do not know this information. If these bytes need changing (they often will not), a new boot ROM must be burned, and a new image must be built. Ethernet Address can be specified at the bootrom prompt (N command). This option will able you to change the last three bytes. To use this option, open the console window (for example: "Hyper Terminal") and when the bootrom banner appear and the countdown start, press any key, when you get the [VxWorks Boot] prompt, press N and follow the instructions.
There are two way to reprogram the Hard Reset Configuration Word. The first way is to plug the Flash in SBC8260 board and using visionPROBE II/visionICE II, the second option is to use visionPROBE II/visionICE II connected to the Scout board.Using SBC8260 board with visionPROBE II/visionICE II:
1. Hardware preparations:
1.1. Make sure the SBC8260 is powerd off.
1.2. Remove the SIMM Flash from the SBC8260 board and plug the Scout board
SIMM Flash instead. You will need to do it twice for the two Scout
SIMM Flash's.1.3. Open SW2-1, by default this switch is closed. Set JP24 1-2 3-4.
1.4. Connect the visionPROBE II/visionICE II to the JTAG connector power on
the board.2. Get into Background Mode:
2.1. If you are usuing visionCLICK continue to step 2.2. , if you are using
SingleStep for vision continue to step 2.3. .2.2. Using visionCLICK:
2.2.1. Start visionCLICK and in the project configuration choose
MPC8260 for the CPU.2.2.2 Use the IN command in the terminal window to get the ">BKM>"
prompt.2.3. Using SingleStep for vision:
2.3.1. Go to the "File" menu and choose the "Start Debug Session..." .
2.3.2. The "Debug" dialog box will popup, In the "Connection" tab
choose the visionPROBE option & the correct LPT port if you are
using visionPROBE, or visionICE & enter the emulator IP address
if you are using visionICE.2.3.3. In the "Processor" tab choose the MPC8260.
2.3.4. In the "Register" tab choose the option
"Use vision-style register window with REG file" and then
make sure that it is empty.2.3.5. In the "File" tab choose the "Open connection only" option
and press OK.2.3.6. Now should get the "Debug Status" dialogbox and in the
"Debug Session" field you should have in green
"Started Successfully", press the "Close" button.2.3.7. Now go to the "Command" button in the toolbar and press on it.
The "Command" Window will popup, the prompt in the window will
be "SingleStep". Bring the mouse cursor above the "Command"
window and pres the right button. A menu will popup, choose the
"VisionShell(vsh)" option. Now the prompt in the window will be
">BKM>".3. Flash Settings:
3.1 Setting the Flash chip select. Once the ">BKM>" prompt appears we need
to verify that the Flash chip select configure correct. To do this type
"CS" in the visionCLICK "Terminal" window or in SingleStep "Command"
window and press Enter. The first line is for the Flash chip select.
This is chip select 0 "CS0" under the "PS" (From Port Size) column
for the first line, check that the number is 32 For the SIMM Flash.
If the number is else follow the step below in order to change it:3.2 Type "CS CS0" in the visionCLICK "Terminal" window or in SingleStep
"Command" window and press Enter.>BKM>CS CS0
3.3 Press enter until you get the following line:(0-3) = 64, 8, 16, 32 bits Port Size = 32 Bits >
Enter 3 for 32 SIMM Flash and keep pressing Enter until you get again
the ">BKM>" prompt.3.4. In the visionCLICK "Terminal" window or SingleStep "Command" window
type the command "TF DEVICE" and press enter. You will get a list of
all the support Flash's sick for the Flash
"17: AMD 29F016/17( 2048 x 8 ) 4 Devices" and remember the index
number that apers on the left side, in this example it is 17, with
deferent versions of the FLASH library it can be a deferent number, but
the the FLASH type should be the same always . press enter until you get
the "New Choice >" prompt, then enter the number of the Flash, in our
case 17 and press enter.3.5. In the visionCLICK "Terminal" window or SingleStep "Command" window
type the command "TF CONFIG:" and press enter. The first line that you
will get will be the Flash device you selected. Verify that this is the
correct one, if it's not the correct one return to step 7. If it's the
correct one enter the start address of the work space in RAM. For
example the second line will be:
"Start of work space in target : 0F008000 >" , in the prompt enter
"0F008000" and press enter. The third line will be:
"Start address of the flash : FE000000 >" , in the prompt enter
the start address of the Flash "FE000000" and press enter.4. Erasing the Flash:
4.1. Now we need to erase the Flash. to do it, in the visionCLICK "Terminal"
window or SingleStep "Command" window type the following command and
press enter: "TF ERASE" after the erase will finished you will get the
following message:AMD 29F016/17( 2048 x 8 ) 4 Devices Erasing Flash(s) ... DoneAnd you will get back the ">BKM>" prompt.5. Programming the Hard Reset Configuration Word:
5.1. In the visionCLICK "Terminal" window or SingleStep "Command" window
type the command "TF TEST" and press enter, you will get the following
message:The flash algorithim : AMD 29F016/17( 2048 x 8 ) 4 Devices has been loaded. The remaining Workspace is filled with a pattern Flash to be programmed starts at = $FE000000 End of current flash device selected at = $FE7FFFFF End of the workspace is at = $0F008DD0 Programming algorithim starts at (PC set to this address) = $0F00802C Erase algorithim starts at = $0F00801C Work space starts at = $0F008000 Work space ends at = $0F008DD0 Test pattern '*ESTFLASH*_' starts at = $0F0084D0When you will get back the ">BKM>" prompt type the following command:
"SML Test pattern *ESTFLASH*_ starts at 30000000 0 02000000 45000000"For example:
"SML 0F0084D0 30000000 0 02000000 45000000" and press enter. Then type
the following command "GO" and press enter. You will get the following
message:>RUN> !HALT! - [msg90004] Unexpected software breakpoint encountered; PC = 0x0F0083B4This normal, it's OK. After you got the ">BKM>" prompt again the Hard
Reset Configuration Word is programmed in you Flash.Now you can turn off the SBC8260 power and put the Flash back in the
Scout board.Using Scout board with visionPROBE II/visionICE II:
1. Hardware modification for the Reset Config signal:
The first thing that needs to be done is to tie the /rstconf signal of the
MPC8260 to 3.3V. An ECO will be generated to solder a 2 pin header to the
board. One pin will be soldered to 3.3V and the other pin will be wired to
R41 (side adjacent to C96). If this header is on the board, a jumper must
be installed during this recovery procedure. If the board does not have the
header, a connection must be made from R41 (side adjacent to C96) and 3.3V
during power up. This causes the MPC8260 to use it's default settings.**NOTE: Verify that R41 is a 1K resistor (RES-00091). If R41 is a 0 ohm
resistor, remove and replace with a 1K resistor. If a jumper is
installed on the 2 pin header with a 0 ohm resistor installed, it
will short 3.3V to ground.2. Disable Master processor (MPC750 or 755):
The master processor will need to be removed or held in reset via a second
visionIce/visionProbe so it will not interfere when the MPC8260 becomes
the master.3. Initializing MPC8260 JTAG interface:
Connect visionPROBE or visionICE to the 8260 JTAG interface (J12) and set
the project up for the MPC8260. Some emulator setup may be required. The
JTAG reset needs to be set to active by using the CF TRESET ACTIVE command.
Also, the port size of the flash has to be set to 64 bit by using the
"SC BR0 FE000001" command.4. Writing the Reset Config Word:
At this point, the flash should be ready to write to. A manual sequence
can be written to the flash by typing the following command's in the
visionCLICK "Terminal" window or SingleStep "Command" window:(This sequence should erase sector 0)
mml fe002aa8 aaaaaaaa aaaaaaaa mml fe001550 55555555 55555555 mml fe002aa8 80808080 80808080 mml fe002aa8 aaaaaaaa aaaaaaaa mml fe001550 55555555 55555555 mml fe000000 30303030 30303030wait a few second's, about 30.(This sequence will write the same config word to both flash SIMMs)
mml fe002aa8 aaaaaaaa aaaaaaaa mml fe001550 55555555 55555555 mml fe002aa8 a0a0a0a0 a0a0a0a0 mml fe000000 30000000 30000000 mml fe002aa8 aaaaaaaa aaaaaaaa mml fe001550 55555555 55555555 mml fe002aa8 a0a0a0a0 a0a0a0a0 mml fe000008 0 0 mml fe002aa8 aaaaaaaa aaaaaaaa mml fe001550 55555555 55555555 mml fe002aa8 a0a0a0a0 a0a0a0a0 mml fe000010 02000000 02000000 mml fe002aa8 aaaaaaaa aaaaaaaa mml fe001550 55555555 55555555 mml fe002aa8 a0a0a0a0 a0a0a0a0 mml fe000018 45000000 450000005. Verifying the Reset Config Word:Use the "DML FE000000" command to verify data has been written correctly.
SCC1 are configured as UART devices with 8 data bits, 1 stop bit, hardware handshaking, and parity disabled.
This VxWorks Scout BSP uses a simple 3 wire connection and standard phone jacks where pin 1 = RIN, pin 2 = TOUT, pin 3 = NC, and pin 4 = GND.
There is no SCSI interface on this board.
FCC2 is configured as a 10/100Mb/s Fast Ethernet port
bootrom_uncmp.hex is provided with this BSP. The bootrom is configured to a ROM base address of 0x0. When programing the bootrom to the FLASH an offset of 0xFFF00100 need to be given, also it's configured to use the 2 MByte On Board Flash ROM and FCC2 10/100BaseT Ethernet as default boot device and SCC1 as console device. The hard reset configuration word must be programmed separately at the flash base address of 0xFE000000 and at offsets 0x0, 0x8, 0x10, 0x18 and 0x20, see chapter 5 Reset in the MPC8260 PowerQUICC II User's Manual.
The following images are delivered with the wrScout BSP:
bootrom_uncmp bootrom_uncmp.hex bootrom bootrom.hex vxWorks vxWorks.st miiLib.obj
Only bootrom_uncmp, bootrom, vxWorks have been tested.
The wrScout is using the m82xxDpramLib.c to allocate dynamically the necessary DPRAM memory for the serial and Ethernet channels. Key features of sysDpramLib are:- Init the DPRAM memory with considerations of any Microcode that add been
loaded.- Allocate aligned and non aligned memory.
- Free memory.
- Manage a special section (b000 - c000) for special FCC needs.
This section describes miscellaneous information that the user needs to know about the BSP.
When using visionPROBE II or visionICE II to run vxWorks image or bootrom you need to set the "VECTOR" table location to low. To do this type the following command in visionCLICK "Terminal" window or SingleStep "Command" window:CF VECTOR LOWAnd press enter after it. Failing to do this will result with crushing at address 0x0 after pressing the "GO" button. The reason for this is, VxWorks is setting the Vector table to LOW, and by default visionPROBE/ICE ia setting it to HIGH.
Scout PCB Engineering Specification (PowerQUICC II + MPC750) MPC8260 PowerQUICC II User's Manual MPC8260UM/D Motorola MPC750 RISC Microprocessor User's Manual, Motorola PowerPC Microprocessor Family: The Programming Environments,