BSP Developer's Guide

2
BSP Organization
PCI_MSTR_IO_LOCAL Local address mapped into PCI I/O window.
PCI_MSTR_MEMIO__SIZE Size of the window onto PCI memory
(non-prefetched).
PCI_MSTR_MEMIO_BUS Bus address of PCI non-prefetched memory
window.
PCI_MSTR_MEMIO_LOCAL Local address mapped into non-prefetched
window.
Not all PCI spaces are implemented in every situation. Note that there are different
windows mapping main memory. The default window is for prefetchable memory
operations. The second window, PCI_MSTR_MEMIO, is for performing
non-prefetchable operations. One or both of these windows to main memory is
always mapped. Our standard signal to disable a window is to set the size value
to zero, which should disable access from local memory to that space.
For more information on PCI macros, please refer to Wind River Technical Note #49.
2
romInit.s
Network Device and Interrupt Vector. If this BSP uses external boards for network
devices, then the bus addresses and interrupt vector assignments are user options
presented in config.h.
bspname.h. This file is normally included after all option selections. This allows
tests to be inserted into bspname.h to check for proper selection combinations. An
example would be a board that has two different Ethernet options, only one of
which can be selected at a time. In this case, the bspname.h file would check to see
if both were defined and generate an error message, if necessary.
Another example would be to add additional features required to support a
user-selected feature. For example, the user might select NFS support, and the
bspname.h file would add RPC and network support as being required to support
NFS. This is precisely what usrExtra.c does for usrConfig.c. Of course, this is just
a hypothetical illustration of the concept, not an actual example.
This file contains the assembly language source for initialization code that is the
entry point for the VxWorks boot ROMs and ROM-based versions of VxWorks.
The entry point, romInit( ), is the first code executed on power-up. It sets the
BOOT_COLD parameter to be passed to the generic romStart( ) routine. If the
hardware requires immediate memory mapping or setting special registers,
handle it here. Most hardware initialization occurs using the sysHwInit( ) routine
in sysLib.c.
23