SOC Drivers (Windows Embedded CE 6.0)
1/5/2010
If your standard development board (SDB) or hardware platform contains a high-integration CPU or associated chipset (core logic), Windows Embedded CE 6.0 contains a driver for the peripherals on the chip in the system-on-chip (SOC) directory, %_WINCEROOT%\Platform\Common\Src\SOC. Review the contents of the SOC directory for drivers you want to include in your BSP.
Note
The SOC directory is new for Windows Embedded CE 6.0. The contents of the Windows CE 5.0 CSP directory has been restructured and migrated to the SOC directory.
If you cloned a BSP that makes use of the SOC drivers, your BSP includes source files necessary to build the final image using the shared SOC library code. It also includes the Platform.bib and Platform.reg entries necessary to include the resultant image in your run-time image.
Some SOC 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 SOC drivers are linked against a hardware platform-specific library, review the drivers directory of a hardware platform known to use the SOC driver of interest.
For example, the Intel PXA27x development platform uses the PXA27x display driver from the SOC directory, but includes a hardware platform-dependent Touch.cpp file for touch driver routine information.
The greater part of the code for the SOC driver resides in the SOC directory, but the resulting run-time image is built during the run-time image build process.
If a SOC driver must be modified for your hardware platform, copy the SOC sources from the SOC directory to your hardware platform's directory.
For example, copy the USB function SOC driver from %_WINCEROOT%\Platform\Common\Src\SOC\PXA27X_MS_V1\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.