BSP Developer's Guide

3
Creating a New BSP
Makefile
At a minimum, your makefile must define the following macros:
CPU
The target CPU, which must be the same as the reference BSP.
3
TOOL
The host tool chain (such as gnu), which must be the same as the reference BSP.
TGT_DIR
The path to the target directory. The default is installDir/target.
TARGET_DIR
The BSP directory name.
VENDOR
The board manufacturer’s name.
BOARD
The board name.
ROM_TEXT_ADRS
The boot ROM entry address in hexadecimal. For most boards, this is set to the
beginning of the ROM address area. However, there may be some hardware
configurations that use an area at the start of ROM for the reset vector; thus, it
should be offset accordingly. The offset is typically architecture dependent.
Thus, the low order bytes of this macro can be copied from a reference BSP.
ROM_WARM_ADRS
The boot ROM warm entry address in hexadecimal. This is usually a fixed
offset of 8 bytes beyond the cold boot entry point ROM_TEXT_ADRS. The code
in sysToMonitor( ) should do an explicit jump to ROM_WARM_ADRS when a
switch to the hardware ROM code is desired.
ROM_SIZE
The ROM area’s size in hexadecimal.
RAM_LOW_ADRS 2
The address at which to load VxWorks.
RAM_HIGH_ADRS 2
The destination address used when copying the boot ROM image to RAM.
2. RAM_LOW_ADRS and RAM_HIGH_ADRS are absolute addresses, typically chosen to
be at an architecture-specific offset from the start of DRAM. For a quick look at the VxWorks
memory layout, see the memory layout diagram in the appendix of the VxWorks
Programmer’s Guide.
45