BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
and MPC driver queue messages and deliver responses back to the appropriate
device driver. Multiple devices can be controlled simultaneously since all
messages contain source and destination addresses, as well as sequence numbers,
etc., that keep track of message traffic.
PCI, cPCI, and PMC
Wind River provides drivers compliant with Rev 2.1 of the PCI Specifications.
These drivers provide support for manual and automatic configuration and
enumeration of devices. Also provided is a interrupt library module that handles
the overloading of PCI interrupt sources. Refer to the reference entries for
pciConfigLib, pciConfigShow, pciAutoCfg, and pciIntLib for more information.
Wind River Technical Note #49 also contains information regarding PCI support.
Busless
When confronted with the task of porting VxWorks to a busless target, Wind River
strongly recommends the use of a NetROM or In-Circuit Emulator. Emulator
object file formats and operations are as varied as the vendors that sell them.
Contact Wind River Systems for information on appropriate combinations.
The initial goal should be to get serial line activity. Start small. Build a simple
polled serial driver and build up from there. Take advantage of any LEDs that can
be blinked as checkpoints in the code are passed. Use an oscilloscope to see that
interrupts are occurring and being acknowledged correctly.
See 3. Creating a New BSP for more information on strategies for dealing with the
initial startup of a new BSP.
4.4 Devices
Devices should support both read and write access; it is both expensive and error
prone for software to keep copies of registers or other data written to a device.
Devices that have mandatory access timing requirements should not expect
software to delay between accesses (error prone and non-portable), but should
automatically suspend the next access.
76