Building a Windows Embedded CE6 Image for Trizeps6 from Scratch

Under Construction

This application note will guide you through the steps needed, to create your own Windows Embedded CE 6 image. This article applies to the BSP for Trizeps VI.

Preparation

First of all you need to install Microsoft's Platform Builder for Windows Embedded CE 6.0:

• Visual Studio 2005

• Visual Studio SP1 (Service Pack 1)

• Windows Embedded CE 6.0 (Platform-Builder Plug-In for Visual Studio 2005)

• Windows CE 6.0 SP1 (Service Pack 1)

• Windows CE 6.0 R2 Update

• Windows CE 6.0 Cumulative Product Update Rollup Package 2008 (QFEs)

• Remaining Windows CE 6.0 QFEs

If asked during install for which platforms, you must select ARMV4I and XScale. If you already have an installation, you can add those platforms, by running the Platform-Builder installer. Before using the latest Trizeps-BSP, update the Platform-Builder usingWindows Embedded CE Downloads.
Install the Seco BSP for Trizeps VI.

Creating a new Project

• Start Visual Studio 2005 and select File –> New Project..

• Select Platform Builder CE 6.0, OS Design as project-type and give your project a name. In this example, we will use CE6Demo.

• Follow the instructions of the OS Design Wizard.

• Select the Board-Support-Packages you want to use this project with; i.e. you might want to add TR4CONXS to add support for the Trizeps4-BSP. Since this example uses Trizeps6, select TR6CONXS.

• Select a design-template that matches your needs.

• The following New Platform Wizard-pages allow us to add further components. Don't worry too much if you forgot to select a component here. Adding and removing components can be done later. In this example add ActiveSync. This is a nice tool, you would probably want and need for debugging your application.

• Add Wired Local Area Networking to support the ethernet-chip of the Trizeps6.

• Now the wizard is done.

• Depending on components added, some security warnings might get displayed

Modify a Project

After the OS Design Wizard has generated a new workspace, you may want to do some modifications. <columns> NEWCOL On the left you see the Catalog Items View. If this window is not shown, use View –> Other Windows –> Catalog Items View to add it. This view will show which catalog-items are included into your Windows Embedded CE Image.

• A green check-mark shows that an item is included.

• A green box indicates that an item was included because of an dependancy.

• A red cross indicates that an item could not be included because of missing dependanies.

To add an item check a box. Let's add some drivers:

• Wave Driver

• Trizeps Framebuffer Device

• Select the display-type. The ConXS-evaluation-board uses an LTA065A041F.

• Select No keyboard (dummy)

• Ethernet

• PCF8593 ( This is the RTC mounted on the ConXS)

• Serial-Port COM1:

• Serial-Port COM2:

• Serial-Port COM3:

• IPSM4000

• Trizeps SDMMC

• Trizeps SDMMC (on board)

• UCB Touch

• USB-Host

• USB-OTG-Host

• USB-OTG-Slave

Now select which type of image you want to build:
Type: nk.nb0 (RAM): Build an image, which is not stored to flash. This is quite usefull if you want to directly download the image through Platform-Builder to RAM and start debugging. It can also be used to start images from SD-card. This configuration uses a RAM-based registry and is comparable to the mode used on earlier Trizeps-products.
Type: xip.bin (ROM, BinFS): Build an image which is stored on a seperate flash-partition. It uses a Hive-based registry and the flashdisk is mounted as root-filesystem. That results in all changes to be persistant ( like you experience on desktop operating-systems). Note: When using this configuration, you should set: Project→ ProjectName Properties..→Configuration Properties→General→Target file name for debugger: to xip.bin. Be sure to change this for both build-configurations: TR6CONXS ARMV4I Debug and TR6CONXS ARMV4I Release.

After adding the drivers you might note, that there are two crosses at Trizeps SDMMC. If you want to know why they got excluded, do a mouse right-click on the item and select Reasons for Exclusion of Item.
In this case you only need to add SD Memory.

</columns>

When you want to use ActiveSync, you should include USB Function Clients –> serial component.
You might also want to add the USB Storage Class Driver, so that you can plug USB-memory-sticks.

Build a Project

If you think you are done with your modifications, call Build –> Build Solution.

Wait. . . . . .

After several minutes the build should complete with:

If you selected Type: nk.nb0 (RAM) use nk.nb0;
if you selected Type: xip.bin (ROM,BinFS) use xip.bin;
for download.

Download to Trizeps VI

After your created the image you may proceed to download it to your Trizeps-module. Take a look at the bootloader documentation for further information on how to do this. All commands used here can also be put in an autoboot.bat on a SD-card.

nk.nb0 (RAM)

Run from SD-card:

1. Copy nk.nb0 to a SD-card.

2. Enter bootloader and type:

The first line boot nanddisk will run a script which typically initializes your display.
boot mmc nk.nb0 loads the image to RAM and runs it.
You might want to call epsm to erase the flashdisk-contents.

Download through Platform-Builder:

See Using Eboot for details.

xip.bin (ROM, BinFS)

Run from SD-card:

1. Copy nk.nb0 to a SD-card.

2. Enter bootloader and type:

The first line boot nanddisk will run a script which typically initializes your display.
boot mmc xip.nb0 stores the image to flash.
ereg starts with a clean registry during the next boot.
fb will launch the stored image.
You might want to call epsm to erase the flashdisk-contents.

Download

• Demo-Project:

• Retail-Image: