CSP Drivers (Windows CE 5.0)
If your SDB or hardware platform contains a high-integration CPU or associated chipset (core logic), Windows CE contains a driver for the peripherals on the chip in the CSP directory, %_WINCEROOT%\Public\Common\Oak\CSP. Review the contents of the CSP directory for drivers you want to include in your BSP.
If you cloned a BSP that makes use of the CSP drivers, your BSP includes source files necessary to build the final image using the shared CSP library code. It also includes the Platform.bib and Platform.reg entries necessary to include the resultant image in your run-time image.
Some CSP drivers link against a hardware platform-specific library that is used to define board-specific aspects, including memory maps and interrupts. This is typically the case for chipset peripherals.
To determine if the CSP drivers are linked against a hardware platform-specific library, review the drivers directory of a hardware platform known to use the CSP driver of interest.
For example, the Intel PXA27x development platform uses the PXA27x display driver from the CSP directory, but includes a hardware platform-dependent Touch.cpp file for touch driver routine information.
The greater part of the code for the CSP driver resides in the CSP directory, but the resulting run-time image is built during the run-time image build process.
If a CSP driver must be modified for your hardware platform, copy the CSP sources from the CSP directory to your hardware platform's directory.
For example, copy the USB function CSP driver from %_WINCEROOT%\Public\Common\Oak\CSP\ARM\Intel\PXA27X\USBFN to %_WINCEROOT%\Platform\<Hardware Platform Name>\Src\Drivers\USB.
If necessary, modify the sources file to include hardware platform-specific source files and to generate the resulting DLL. The resulting DLL is generated instead of an intermediate static library, which is later linked into the DLL.
See Also
BSP Drivers | Common Drivers | Device Driver Libraries | Debugging and Testing
Send Feedback on this topic to the authors