DEVELOPING A BSP
This section outlines some of the issues with developing a new BSP from an existing one. The “White Papers” referred to at the start of this chapter provide details for BSP development and porting.
Developing a new BSP is generally not a simple task. To do so requires a lot of background knowledge and experience with Windows Embedded Compact. A simpler task is to adapt an existing BSP for a similar target by cloning it, implementing the bootloader and OAL, customizing the configuration, and adding any new drivers or replacing any that are different.
Cloning a BSP
As covered previously, a BSP for a board that has the same CPU and similar components can be cloned. This creates a new folder under the platform folder for the new BSP. Only modify code under this copied folder. Do not modify any other code because this can break other aspects of Platform Builder. Cloning a BSP was covered in Chapter 6.
Implement Bootloader and OAL
If the new target hardware is similar to the existing BSP’s hardware, then the same bootloader might work. If this is not sufficient, the bootloader code might (hopefully) need only some small reconfiguration and rebuilding. You do, however, need to get this working first. If the task requires a major effort, then the bootloader architecture CE Boot might be a better option.
Customize the memory configuration, interrupts, any GPIO, peripherals, and system initialization requirements.
Add the drivers that ...