TYPICAL DEVELOPMENT PROCESSES
With Windows Embedded Compact 7 devices ranging from small head-less devices with minimal processing requirements for automation and control application, to sophisticated medical instruments with high-performance processing requirements to capture complex inputs and support high-resolution display, there isn’t a set of detailed processes or steps that are generally applicable to all these devices.
The information in this section covers some of the typical Windows Embedded Compact development steps to help you better understand the environment.
With the assumption that a hardware platform for the development project has been selected, following are some of the typical steps needed to develop a Compact 7 device:
- Board Support Package (BSP)
- OS design
- Application
- Debugging and testing
- Deployment
- Post-deployment support and update
Board Support Package (BSP)
After you select the hardware platform, if it does not include a Compact 7 BSP, developing the BSP is the next major hurdle.
BSP is a software package that contains the necessary components needed to generate the OS run-time image for the target device, typically including the following:
- OEM adaptation layer (OAL) codes
- Device drivers for the target device’s peripherals
- File system support unique to the target device
- Bootloader or bootstrap codes needed to launch Compact 7 OS run-time image on the target device
- Bootloader with connectivity codes to establish connection and download OS run-time image ...
Get Professional Windows® Embedded Compact 7 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
