VxWorks BSP Reference : wrMdpBasic8xx
wrMdpBasic8xx - Wind River MdpBasic8xx
This manual entry provides board-specific information necessary to run VxWorks for the wrMdpBasic8xx 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:.CS
__________________________________________________________________________
| ICM DTR BD - MPC821/860 | ICM DTR BC - MPC823/850 | ICM MPC821,855 & 860 |
|-------------------------|-------------------------|----------------------|
| JP1 Open | JP1 Open | JP1 Open |
| JP5 2-3 | JP5 2-3 | JP2 1-3 & 2-4 |
| JP6 1-2 | JP6 1-2 | JP5 1-2 |
| JP7 1-3 & 2-4 | JP7 1-3 & 2-4 | JP6 2-3 |
|_________________________|_________________________|______________________|.CE
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 "wrMdpBasic8xx", 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/wrMdpBasic8xx".3. Programming bootrom_uncmp to MdpBasic8xx 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 MdpBasic8xx board BDM (J1 The BDM Port)
connector.Once all the connections have been made, power up the MdpBasic8xx
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->MPC8xx->MPC860" or the one that
match your MPC8xx . Verify that the "Target Control" option point
to visionPROBE II or 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 Program visionPROBE II / visionICE II with the proper register
setting for the MdpBasic8xx 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: "hsi860basic50mhz.reg" for the MdpBasic860
board with MPC860 50Mhz. 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.4 Get into Background Mode:
Execute the "IN" command to reset the board and initialize it with
the register setting..CS
IN
.CSThis command is the reset command to initialize the board.
3.1.5 Setting the Flash Chip Select:
3.1.5.1 Once the ">BKM>" prompt appears we need to verify that the
Flash chip select configure correct. To do this type "CS"
in the "Terminal" 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 16 For the On Board FLASH. If the
number is else follow the step below in order to change it:3.1.5.2 Type "CS CS0" in the "Terminal" window and press Enter.
.CS
>BKM>CS CS0
.CE3.1.5.3 Press enter until you get the following line:
.CS
(0-2)=32, 8, 16 bits / 3=Rsvd | Port Size = 16 Bits >
.CEEnter 2 for the On Board FLASH and keep pressing Enter
until you get again the ">BKM>" prompt.3.1.5.4 Once the prompt appears, reset the board and the emulator
with the following command:.CS
>BKM>IN
.CEAfter you got the ">BKM>" prompt again continue with the
instruction in the next section.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/wrMdpBasic8xx/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 MdpBasic8xx 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 4MB On Board FLASH: "AMD 29F016/17(2048 x 8) 2Devices"
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 "00000000", set the
"Bytes Of Target RAM Required" to "60000".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 MdpBasic8xx board BDM (J1 The BDM Port)
connector.Once all the connections have been made, power up the MdpBasic8xx
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 "MPC860".
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 "est860basic50mhz.reg"
for the MdpBasic860 board with MPC860 50Mhz. The
"hsi860basic50mhz.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..CS
IN
.CS
This 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 Setting the Flash Chip Select:
3.2.4.1 Once the ">BKM>" prompt appears we need to verify that the
Flash chip select configure correct. To do this type "CS"
in the "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 16 For the On Board FLASH. If the
number is else follow the step below in order to change it:3.2.4.2 Type "CS CS0" in the "Command" window and press Enter.
.CS
>BKM>CS CS0
.CE3.2.4.3 Press enter until you get the following line:
.CS
(0-2)=32, 8, 16 bits / 3=Rsvd | Port Size = 16 Bits >
.CEEnter 2 for the On Board FLASH and keep pressing Enter until
you get again the ">BKM>" prompt.3.2.4.4 Once the prompt appears, reset the board and the emulator
with the following command:.CS
>BKM>IN
.CEAfter you got the ">BKM>" prompt again continue with the
instruction in the next section.3.2.5 Converting the bootrom_uncmp.hex to bootrom_uncmp.bin:
3.2.5.1 Go to the menu and choose "Tools" and
"Vision Flash Utility..." .3.2.5.2 The "Flash Programming Window" will popup. Go to the
"Files" tab, press the "Convert" button.3.2.5.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.5.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.6 Programming the MdpBasic8xx Flash:
3.2.6.2 In the "Flash Programming Window" window. Go to the
"Configuration" tab, & choose the following Flash device:The 4MB On Board FLASH: "AMD 29F016/17(2048 x 8) 2Devices"
In "Flash Bank" group for the "Start:" enter "FFF00000".
In the "RAM Workspace" group for the "Workspace Start at:"
enter "00000000" and for the "Workspace Size:" enter
"60000".3.2.6.3 Now switch to the "Files" tab and press the "Add" button.
The open dialogbox will popup, browse to
"$(WIND_BASE)\target\config\wrMdpBasic8xx "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.6.4 Now go to the "Program" tab and press the "Erase/Program"
button.3.2.6.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 connector to the COM1 (JP3) port on the
the MdpBasic8xx, 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
connector (JP1 on the mother 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 4 MByte On Board FLASH and SCC 10BaseT Ethernet as default boot device and SMC1 as console device.
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 MdpBasic8xx FLASH" section how to program the
MdpBasic8xx Flash, also you can skeep step 3.1.6 or 3.2.5 that explain how
to convert the bootrom_uncmp.hex to *.bin, and instead of programming the
"bootrom_uncmp.bin" program the "vWARE.bin" file.1. Connect your MdpBasic8xx serial channel (COM1) to a host running
terminal program at 9600 baud rate (For example "HyperTerminal") using
the supplied serial cable.2. Connect your MdpBasic8xx 10Base-T RJ45 port (J1) 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, insaide 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 MdpBasic8xx 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 disaierd delay value and press enter.7. Nex 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: 192.168.199.0 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: 192.168.199.1 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 MdpBasic8xx Board MAC : 00-00-00-00-00-00 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 <1> seconds to preempt boot script Booting from script... load \\host\vxWorks.bdx!launch 100000 >Attached TCP/IP interface to cpm unit 0 Attaching interface lo0...done VxWorks Copyright 1984-1998 Wind River Systems, Inc. CPU: MPC821/860 -- Wind River MdpBasic821/860 VxWorks: 5.5 BSP version: 1.2/30 Creation date: Oct 29 2001 WDB: Ready.For more information regarding visionWARE boot services and the visionWARE development kit, please refer to the visionWARE manuals.
The supported boot device(s) is(are):cpm - 10BaseT Ethernet
This section described the support and unsupported features of the MdpBasic8xx
The supported features of the MdpBasic8xx board are:
8xx processors as discrabed in Processors Supported section
Board Initialization
MMU support
Cache support
Decrementer timer, is used to implement a System Clock.
SMC1 a UART for COM1 (Consol channel).
SCC Port as an Ethernet device supporting 10Base-T protocol.
TIMER2 as an 16-bit auxiliary clock.
TIMER3 and TIMER4 are cascaded into a free-running 32-bit timer for timestamp support.
Interrupt Controller.
Baud Rate Generators as required for SMC1.
4MB On Board DRAM.
4MB On Board FLASH.
25, 40, 50, 66, 80 MHZ CPU speeds
The items not supported on the MdpPro8xx are:
virtual DMA
ATM Transparent, or HDLC protocols
This section documents the details of the device drivers and board hardware elements for the wrMdpBasic8xx.
The chip drivers included are: ppc860Sio.c - serial driver ppc860Intr.c - interrupt controller driver ppcDecTimer.c - Timer library for PPC decrementer timer ppc860Timer.c - Timer library for PPC CPM timers 2,3,4 byteNvRam.c - Byte oriented nvram device flash29NvRam.c - FLASH 29LVxxx access routines sysMotCpmEnd.c - configuration module for motCpmEnd driver if_cpm.o - Ethernet Communication library for SCC motCpmEnd.o - END-style Ethernet Communication library for SCCThe timer driver, ppc860Timer, implements a system clock using the PPC decrementer timer, an auxiliary clock using CPM timer 2, and a 32-bit timestamp facility by cascading CPM timers 3 & 4. The BSP configures SMC1 as a UART to implement a console device and the CPM SCC1 as an Ethernet port.
L1 cache locking is available for MPC8xx. The cache lock routine can be used to lock the entire instruction cache with a specified memory region. In the 8xx family allowed two cache types, one for the 8xx (4K cache and one for the 860P (16K instruction cache, and 8K data cache). In the file cache800LockALib.h you will find the following macro:
#define CPUCACHETYPEFor the 8xx with the 4K cache it need to be defined to:
#define CPUCACHETYPE PPCMPC8XX_4KIC4KDCFor the 860P it need to be defined to:
#define CPUCACHETYPE PPCMPC8XX_16KIC8KDC
Memory Map from CPU point of view Chip Select Start Size Access to ------------------------------------------------------------------ CS2 0x0 4MB On Board DRAM 0xFF002000 16KB MdpBasic8xx DPRAM CS0 0xFFC00000 4MB On Board FLASH
N/A.
MPC821/860 , MPC850The BSP determines the processor type during operation. The value in the partnum/IMMR register field is used to determine the processor. Unfortunately Motorola is not consistent in bumping the part number and mask numbers. The following are the values used (from wrMdpBasic8xx.h):
/* CPU Type (for determining 823/850 or 821/860 */ #define INVALID_CPU_TYPE 0x00 #define CPU_TYPE_821_860 0x00 #define CPU_TYPE_823 0x20 #define CPU_TYPE_850 0x21 #define PARTNUM_MASK 0x0000FF00 /* part number file in IMMR */The BSP works properly with all the processor type and revs listed.
The wrMdpBasic8xx.h file contains a construct for manually specifying the desired operating speed. The user should select the desired process operating speed. The speed can be less than or equal to the rated processor speed marked on the chip.#define OPERATING_FREQUENCY CPU_FREQ_50MHZThe BSP is supplied with the operating frequency default to 50Mhz.
The BSP configures to use CPM SCC1 as an Ethernet port. The name "cpm" should be specified as the boot device to the boot ROMs when booting vxWorks over that interface. The BSP configures to use END-style network driver. If you want to use the non-END-style network driver, in "config.h" change the macro from "#define BOOT_DEVICE CPM_END" to "BOOT_DEVICE CPM_NETIF". Each time config.h is edited, new vxWorks and bootrom images should be built and Flash memory is to be programmed.
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 wrMdpBasic8xx.h file and are:#define ETHERNET_ADR_SET /* (used in bootConfig.c to enable 'N' command) */The ETHERNET_ADR_SET is a value that indicates the MAC address is stored in NVRAM and alterable via the N bootrom command.
The MdpBasic8xx 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 "wrMdpBasic8xx.h". The following relate to the storage of the Ethernet address in NVRAM:/* 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 WR-specific prefix that should be kept as-is. If for some reason you need to change them, in "wrMdpBasic8xx.h" change the following macros:#define WR_ENET0 0x00 /* WR specific portion of MAC (MSB->LSB) */ #define WR_ENET1 0xa0 #define WR_ENET2 0x1e #define ENET_DEFAULT 0xa01e0000Note:
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). The Ethernet address is stored in the on board NVRAM. 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.
One of two types of clock input is used on the board. Either a 50000KHz crystal or a 1:1 oscillator is used as the MdpBasic8xx primary clock source. The boot ROM and kernel detect and configure themselves dynamically to support the configured clock. No special user configuration is required.
SMC1 is configured as UART devices with 8 data bits, 1 stop bit, hardware handshaking, and parity disabled.
This VxWorks MdpBasic8xx 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.
SCC1 is configured as a 10Mb/s Ethernet port
If the FORCE_DEFAULT_BOOT_LINE is defined (in config.h), then the DEFAULT_BOOT_LINE parameters are used as boot parameters regardless of the NVRAM values previously specified. Recall, boot parameters are stored in the NVRAM device so boot parameters are not lost during a power cycle.Defining the FORCE_DEFAULT_BOOT_LINE value is useful for debugging emulator/visionPROBE II downloaded RAM based vxWorks images. It is considered a DEBUG options so it should be #undef'ed for the final image.
Normally the boot parameters are specified at the bootrom prompt and stored in NVRAM. When a downloaded image executes, the boot parameters are retrieved from the NVRAM device.
This can sometimes cause undesired results. For example, if the NVRAM has been previously initialized, then changing the DEFAULT_BOOT_LINE in the config.h will not result in the new settings being used. The reason being is the initialization code always takes the boot parameters from the NVRAM device. If there are sane values in the NVRAM device, these boot parameters are used.
If you intended to debug an image by downloading with WR's visionTools and plan on changing the DEFAULT_BOOT_LINE parameters a number of times, it might be convenience to define this FORCE_DEFAULT_BOOT_LINE parameter.
As a note, unitialized NVRAM device is initialized automatically with the DEFAULT_BOOT_LINE parameters specified in the config.h file.
As an alternate solution for the above scenario, the boot parameters can be changed via the bootrom. This will store the values in NVRAM and will sub sequentially be used by the download image. This would require a sane bootrom and would require the target board to run via the bootroms to set the values and then halted to download the image to be debugged via the WR Tools.
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 4 MByte On Board Flash ROM and SCC 10BaseT Ethernet as default boot device and SMC1 as console device.
The following images are delivered with the wrMdpBasic8xx BSP:
bootrom_uncmp bootrom_uncmp.hex bootrom bootrom.hex vxWorks vxWorks.st
Only bootrom_uncmp, bootrom, and vxWorks have been tested.
This section describes miscellaneous information about the BSP.
Some early revisions of MPC821 and MPC850 lack the ability of supporting the timestamp driver, since they only feature two internal timers, whereas the timestamp driver uses timer 3 and timer 4 in cascade mode. On these processors, the timestamp library support is not available.
The module sysMotCpmEnd.c creates the load string for the END-style cpm interface. The Ethernet transceiver on the MdpPro8xx boards is normally wired to the SCC1 channel of the Communication Processor Module (CPM). However, on MdpPro823/850 boards, SCC2 is used instead. The module sysMotCpmEnd.c dynamically configures the driver to use either the SCC1 or the SCC2 channel by reading the BCSR3 register to find out which processor is being used and set up the load string accordingly. The user does not need to perform any other configuration, unless he wants to change default parameters.
Note(s):
** the old cpm driver has been left in the BSP, but no testing and
support is provided.
** 850 uses SCC2 for CPM/CPM End
** 860 uses SCC1 for CPM/CPM End
If 40Mhz is the OPERATING_SPEED, it should be noted that 50Mhz UPM timing values are used. This works but the values could be changed to optimize the timings. Using 50Mhz timing values results in less than optimal performance when run at 40Mhz. See romInit.s for implementation.
N/A
Wind River MDP8xxBasic Hardware Reference Manual MPC860 PowerQUICC User's Manual PowerPC Microprocessor Family: The Programming Environments for 32-bit Microprocessors MPCFPE32B/AD MPC603e & EC603e RISC Microprocessors User's Manual MPC603EUM/AD