
VxWorks
BSP Developer’s Guide, 6.0
98
VME_A24_MSTR_SIZE, VME_A16_MSTR_LOCAL, and VME_A16_MSTR_SIZE must
be defined. However, this requirement can vary depending on the specific VME
controller driver used. Other configuration—such as data width, cycle type, and
other VME-specific details—may also be required. Refer to the VME bus controller
driver for information on exactly what routines must be called during initialization
and what macros must be defined.
The sysBusTas( ) routine is required by the BSP. For boards with a VME bus and
no other bus containing memory, the sysBusTas( ) routine is provided by the VME
bus controller. However, for more complex busses, a custom version of this routine
may be required. In the case of a single board computer, or other simple board
without a complex bus structure, nullVme.c can be used to include sysBusTas( )
and other utility stub routines.
USB Bus Interface Support
VxWorks support for USB is provided as an optional product that supports USB
either as a host or as a device. For current information, refer to the Wind River USB
documentation and your product release notes.
3.3.8 Updating BSP-Specific Documentation
A BSP is not generally considered complete until the BSP-specific user
documentation file, target.ref, is updated. As a general rule, an updated target.ref
file should be available before the BSP is used for any application development.
For target hardware that is developed for “in-house” or internal use only, the
documentation may be required early in the development process.
Once the core BSP is working and contains the bus support that is required for
additional device drivers, it is good idea to update or create the target.ref file. The
documentation file can also include information for any expected optional drivers
and their current level of support. As support for each driver is added and tested,
the target.ref file should be updated as appropriate.
During application development, the target.ref file can be processed and made
available from the IDE (in standard HTML format) by issuing a make man
command from a command or shell window in the BSP directory. See the
NOTE: Wind River does not currently offer the kind of plug-and-play support
published in the VME-64 specification and its extensions.
Comentarios a estos manuales