User`s guide

VxWorks
BSP Developer’s Guide, 6.0
40
ROM_WARM_ADRS
(Optional. Defined in both Makefile and config.h, or in either)
The boot ROM warm boot entry address in hexadecimal form. This is usually
a fixed offset beyond the cold boot entry point,
ROM_TEXT_ADRS. The offset
is architecture-dependent, and can be obtained from the reference BSP or from
the bcopyLong( ) or copyLong( ) call in bootInit.c (located in the
target/config/all directory). If
ROM_WARM_ADRS is defined, the code in
sysToMonitor( ) does an explicit jump to
ROM_WARM_ADRS when a switch
to the hardware ROM code is desired.
ROM_SIZE (Defined in Makefile and config.h)
The flash area size in hexadecimal notation.
RAM_LOW_ADRS and RAM_HIGH_ADRS (Defined in Makefile and config.h)
RAM_LOW_ADRS is the address at which VxWorks is loaded.
RAM_HIGH_ADRS is the destination address used when copying the boot
ROM image to RAM.
HEX_FLAGS (Defined in Makefile)
Defines the architecture-specific flags for the objcopy utility that generates
S-record files.
MACH_EXTRA (Defined in Makefile)
Defines any extra machine-dependent files. In early development, make this
an empty declaration.
BSP_VER_1_1 (Defined in config.h)
BSP_VER_1_2 (Defined in config.h)
BSP_VERSION (Defined in config.h)
BSP_REV (Defined in config.h)
These macros indicate the version and revision numbers for the BSP. The
version number indicates which version of VxWorks can be used with the BSP.
A value of 1.2 for
BSP_VERSION indicates that the BSP is intended for use with
VxWorks 5.4 or VxWorks 5.5 (Tornado 2.x). A value of 2.0 indicates a BSP that
is intended for use with VxWorks 6.0. If
BSP_VER_1_1 is defined with a value
of 1, it indicates that the BSP is backward-compatible with VxWorks 5.4
(Tornado 1.0.1).
NOTE: 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 information on the normal VxWorks memory layout, see the memory
layout diagram in the appropriate VxWorks Architecture Supplement.