1. Installing a BSP

2. Software tool chain As with any cross development the cross tool chain is important On Windows it is enormous - you need –Developer Studio professional edition > 2Gb Plus service pack 1 – 431 mb! –Platform builder 847Mb –WinCE version 6 > 9Gb! The you will also require you vendor or homemade BSPs

3. Installing a new BSP Generally the suggested way is to clone an existing BSP design I will use the Cirrus epc93xx BSP –This needs installing in C:\wince600\platforms\epc933 –This is the generic design for the cirrus ep92xx range C:\Program Files\Microsoft Platform Builder\6.0\catalog\ –This requires the ep92xx.pbxml file C:\wince600\osdesigns\ –Finally these are some sub-designs for various cpu and board variants – we will require the ep9302 board one. At the start I will simply take over this design and only clone once I have got it working.

4. Changing the BSP We will require a few potential changes –The memory addresses for the BSP load –The serial ports selected for debug information We should build a minimal system first we will attempt to get more services and features up later on

5. The EP9302 boot sequence The EP9302 boots for a small built in boot ROM. This allows the developer to select 3 alternatives to boot from –From a UART at 9600 Only 2k of code –From an SPI device, i.e. EEPROM –From FLASH Starting at 0x10000

6. The TS7300 boot sequence The TS7300 uses the SPI boot option This loads in a small (2k) program from an EEPROM This program has a serial driver and an SD card driver and loads the first sector off the SDcard –We won’t want to change the EEPROM, at least at first, so we will have to live with this approach

7. TS7300 boot WINCE is expecting a more traditional system that is writes its BSP into FLASH and that is used to boot the board and bring up the kernel We will have to modify the WINCE boot order and change the installation method. –No jtag re-flashing, just dd’ing to sdcards! –No BSP board initialisation code.