
2 Overview of a BSP
2.3 Components of a BSP
29
2
#include "sysIOPort.c"
This means that the BSP contains a source file sysIOPort.c that does not have a
corresponding object module. Instead of a separate object module, that object code
is included in sysLib.o.
Another source of derived files is the target.ref (or target.nr) documentation file in
the BSP directory. This file is maintained in an unprocessed form that is difficult to
read. To process the target.ref file, issue a make man command in the BSP
directory. This command results in a new HTML file that is suitable for online
viewing. For more information on the HTML output or the target.ref file, see
B. Documentation Guidelines.
Other objects derived from files in the BSP directory are related to the project
facility. Each time a bootable project is created from a BSP directory, a projName.wpj
file is created. A project also contains several derived source and header files
including a makefile for use with the project facility, a prjObjs.lst file containing a
list of all the object modules used for the build, and directories containing the
object modules and VxWorks images themselves. Note that although these objects
are derived from information in the BSP directory, the objects themselves are not
located in the BSP directory.
2.3.3 Required Data Variables
You must declare and initialize the following data variables in your BSP.
sysPhysMemDesc[ ]
PHYS_MEM_DESC sysPhysMemDesc[ ]
The sysPhysMemDesc[ ] array holds descriptions of different memory ranges on
the board. This is used by several vxWorks libraries, including the memory
management subsystem. This array must be initialized by the BSP. Typically, it is
sysPhysMemDesc[ ] Determines physical memory layout
sysPhysMemDescNumEnt Number of entries in sysPhysMemDesc[ ]
sysBootLine Address of boot line
sysExcMsg Catastrophic message area
sysFlags Boot flags
Kommentare zu diesen Handbüchern