BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
HEX_FLAGS
Architecture-specific flags for the objcopy utility that generates S-record files.
MACH_EXTRA
Any extra machine-dependent files. Make it an empty declaration for now.
! CAUTION: The hexadecimal addresses above should not include a leading 0x.
bspname.h
config.h
sysLib.c
Some additional architecture-specific macros might also be required in the
makefile. For example, the i960 needs to know where to link the Initial Boot
Record. For architecture-specific information, see the appropriate VxWorks
Architecture Supplement or 4. Hardware Guidelines.
See bspname.h, p.26.
The basic description of config.h, p.16 applies, although some small modifications
are needed. First, make sure the following code stub is present before the line that
includes configAll.h:
/* BSP version/revision identification, before configAll.h */
#define BSP_VER_1_1 1
#define BSP_VER_1_2 1
#define BSP_VERSION "1.2"
#define BSP_REV "/0" /* 0 for first revision */
To start, add the following lines near the end of the header file:
#undef INCLUDE_MMU_BASIC /* bundled mmu support */
#undef INCLUDE_CACHE_SUPPORT /* cache support */
Make sure the definitions of ROM_TEXT_ADRS, ROM_SIZE, and
RAM_LOW_ADRS match those defined in the makefile.
Make sure LOCAL_MEM_LOCAL_ADRS and LOCAL_MEM_SIZE are correctly
defined.
While sysLib.c is by far the largest BSP file, at this phase you should implement
only the basics: sysModel( ), sysBspRev( ), sysHwInit( ), sysHwInit2( ), and
sysMemTop( ). The routine sysBspRev( ) is new as of VxWorks 5.3. Implement this
routine as follows:
46