BSP Development (Compact 2013)
3/26/2014
A board support package (BSP) includes all of the customized OS abstraction code, device-drivers, and configuration files that Windows Embedded Compact needs to run on a particular hardware board. With a BSP, you insulate your customers from hardware-level variations and let them develop their features by using generic OS-level APIs. Also, because it already encompasses all of your hardware-specific software, a BSP can help protect your intellectual property by limiting the amount of technical information you need to publish for customers.
This developer guide contains the following sections:
Section |
Description |
Intended audience |
|---|---|---|
Provides an overview of the components and code organization used by Compact 2013 BSPs |
Developers who are new to BSPs or with Windows Embedded Compact |
|
Provides instructions for cloning a sample BSP and modifying it for specific hardware |
BSP developers who are familiar with BSP concepts |
|
This section explains the differences between Compact 7 and Compact 2013 that will have the most impact on BSP developers and discusses issues specific to BSPs based on x86 and ARM architectures |
Compact 7 BSP developers who want to migrate their BSPs to Compact 2013 |
|
Describes the snapshot boot process and how to implement it on your device. Snapshot boot enables you to reduce boot time by saving the state of your device to persistent storage and then restore that state when the device reboots |
BSP developers who have devices with restrictive cold boot performance requirements |
|
Describes the two different boot loader frameworks available in Windows Embedded Compact and how they work |
BSP developers who want a deeper understanding of boot loader frameworks |