Porting WinCE on eval boards – part 1

Porting of WinCE on a new evaluation board is one challenging task. Though when some of the following
things when kept in mind will always make the job easy.

1. Know details of your hardware board well
  - programming details of peripherals on the SoC
  - availability of RAM, flash technologies, etc, or much better, know the memory mapping details
  - hardware ports availability on the board
  - details of board layout and connections with SoC
2. Familiarize yourself with the Microsoft Visual Studio (I work with v2005) and Platform builder
3. Check for a working BSP targeting the same platform,
   - parts of the existing BSP involving writing of assembly code for boot loader and OAL layer
     can be reused for writing the new BSP.
   - more simpler, clone the existing BSP and tweak the cloned BSP to work for the new target
   - most of the OAL framework code duplication will be avoided
4. WINCE600 will always have some or the other support libraries provided to make job of the developer
   easy. Always check if there are any helpful libraries available for use. "google MSDN :D "

Carrying out the porting for the new target will involve the development of following,
1. Boot loader (boot strapping of boot loader is a different issue)
3. KITL (Kernel Independent Trasport Layer)
2. OAL (OEM Abstraction Layer)
4. WinCE Device Drivers
5. Applications

Will add details on the components in my future posts.

cheers,
somesh

This entry was posted on Thursday, April 29th, 2010 at 12:12 PM and is filed under WinCE. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply