BSP Developer's Guide

2
BSP Organization
Files in the target/config/all Directory
The files in target/config/all are delivered as part of the VxWorks architecture
product. Do not alter these files unless absolutely necessary. Of special concern is
configAll.h. This file sets the default configuration for all VxWorks images. The
values you define here should be generic and therefore true for most if not all
VxWorks developers at your site. If you need a VxWorks image that differs from
the default configuration, use your BSP’s config.h to override (#define or #undef)
the default values in configAll.h.
Files in config/all are not directly used when building a project. They are scanned
only once when a new project is made from a BSP. Any changes to the files in
target/config/all after a project has been created do not affect the project. If a
change is desired, the user must make the change directly in the project area.
2
! CAUTION: Changing configAll.h from the command line can have unpleasant
side effects for other VxWorks users at your site. This note only applies to building
from the command line. One benefit of the Tornado project facility is that changes
do not affect existing projects. Only new projects created from a BSP after the
change to configAll.h inherit that change.
bootConfig.c – Main Initialization for Boot ROM Images
The bootConfig.c file is the main initialization and control file for all boot ROM
images. It includes the complete boot ROM shell task. It contains a table (NETIF)
for network device initialization. This module is a subset of usrConfig.c. Boot
ROM images do not provide all of the optional features available in the full
VxWorks images. Of particular note is that boot images do not use MMU libraries
(except for SPARC).
The Tornado project facility does not have the ability to create and manipulate a
boot ROM project. For projects created from a BSP, there is a button that performs
the traditional command-line creation of a boot ROM image from the Build menu.
Please take note that project-specific configuration information has no effect at all
when the boot ROM image gets built. Only the traditional config.h, configAll.h,
bootConfig.c, and bootInit.c files affect the building of a boot ROM image.
bootInit.c – Second-Stage ROM Initialization
The bootInit.c file is the second stage of boot ROM initialization, after romInit.o.
The romInit( ) routine in romInit.s terminates by jumping to romStart( ), defined
in this file. The routine romStart( ) performs the necessary code uncompression
and relocation for ROM images. First it copies the text and data segments from
13