BSP Developer's Guide

2
BSP Organization
For boards without NVRAM, include the file mem/nullNvRam.c so that calls to
NVRAM routines return ERROR. This file is provided on the BSP Kit CD-ROM in
the target/src/drv/mem directory.
There is a generic NVRAM driver called templateNvRam.c. See comments in this
file for a description of the requirements and macros needed to use this driver. The
templateNvRam.c file is appropriate for all boards where NVRAM is byte
accessible, as opposed to block accessible.
NV_RAM_SIZE
The total bytes of NVRAM available. Define NV_RAM_SIZE in config.h. For
boards without NVRAM, define NV_RAM_SIZE as NONE.
BOOT_LINE_SIZE
The number of bytes of NVRAM that are reserved for the VxWorks boot line.
The default value is 255 and is defined in configAll.h. BOOT_LINE_SIZE must
be less than or equal to NV_RAM_SIZE. To override the default value of
BOOT_LINE_SIZE, first undefine the macro in config.h, then define it.
2
NV_BOOT_OFFSET
The byte offset to the beginning of the VxWorks boot line in NVRAM. The
default value is 0 and is defined in configAll.h.
Default Bootline Parameters. The DEFAULT_BOOT_LINE macro provides an
example bootline, which end users can alter to reflect their target environment.
This is particularly useful for targets without NVRAM, because it means the end
user does not have to re-enter the boot parameters on each power cycle.
Timestamp Support. Each BSP should have timestamp support for the WindView
product. The user configures timestamp support by defining or undefining the
macro INCLUDE_TIMESTAMP. See the comments in the timer driver source file for
a description of the additional support required by that specific driver.
External Bus Address Mapping. VMEbus mapping is controlled by a series of nine
macros for master window mapping and another set of nine standard macros for
slave window mapping. The user configures VME by defining INCLUDE_VME in
config.h. The VME mappings for A16, A24, and A32 space master access are
controlled by a sequence of three macros each.
It is assumed that the BSP honors all of these macros. If the hardware is fixed and
one or more sets of these macros must have fixed values, then those macros should
be moved from config.h to bspname.h. Only macros that the user can reasonably
change should be in config.h.
21