1. WinCE 6.0 development

2. Getting Started: requirements
• Visual studio 2005 with service pack:Create an operating system design
and build a Windows Embedded CE 6.0 runtime image using this
development toolkit. Works with Platform Builder for Windows
Embedded
CE 6.0.
• Windows Embedded CE 6.0: Integrate with Visual Studio 2005 using this
Platform Builder for CE 6.0 development toolkit
• Windows Embedded CE 6.0 Platform Builder Service Pack 1: Improve the
debugging process. Update for Windows Embedded CE 6.0. Necessary for
Visual Studio 2005 to build a CE 6.0 R2 runtime image
• Windows Embedded CE 6.0 R2 : extended features and capabilities.

3. Building the OS design
• Open a new platform builder 6.0 project
• Chose your OS design template
• Add the BSP needed.
• Select the installer application i.e CAB
• Add all needed development service core os
services and communication networking
services.
• Build OS

4. Customizing the OS design
• create or customize an OS design: using OS design
wizard
OS design is a set of configuration files for Platform Builder to
generate a Windows Embedded CE run-time image
• Generate corresponding run-time image.
TARGET
Reduced footprint
Lower hardware requirements

5. Creating Os design
• OS design must preferbly consist of following
Software components drivers / BSP
device drivers, hardware-specific utilities, and
an OEM adaptationlayer (OAL)
Catalog items (not hardware dependent)
Custom registry settings
Installer/debugger (build option)

6. steps:
 Start VS2005 with platform builder for WCE6.0 R2
 Chose a OS design template (if avalaible the actual device
design template)
 Add required components and windows applications.(only
necessary ones, to keep footprint small)
 Choose build configuration ( debug and release)

7. Property pages

8. OS design property
• Locals: allows to select languages
• Build options: configure options for runtime
image.
• Environment options: configure enviroment
variables needed during build process.

9. Advanced OS design configuratoin
• Its also possible to develop a runtime image which will
support multiple platforms with the same OS design
OS Design Paths and Files
 <file sol^n Name>.sln : store settings specific to the OS design
project. The file name is generally the same as that of your OS
design.
 <file sol^n Name>.suo : contains user-dependent information
 OS Design Name>.pbxml: catalog components and all the
settings related to OS design
 Subprojects: a separate subfolder for each subproject created
as part of the OS design

10.  SDKs : This directory includes the Software Development Kits
(SDKs) created for the OS design
 Reldir: This is the release directory. Platform Builder copies
the files into this directory during the process of creating the
run-time image that can then be downloaded to a target
device
 WinCE600 : files are copied here after the sysgen phase,
including resource and configuration files of the OS

11. Creating and Adding Subprojects to an OS
Design
• Use windows embedded CE Subproject
project wizard by right clicking the subfolder
in solution explorer and clicking add new
subproject or add existing subproject.
• For eg: we can add device driver for a USB
peripheral in the form of a subproject or add
registry settings, environment variables

12. Creating and Adding existing Subprojects to an
OS Design
• Subfolder contains following configuration
files
o .pbpxml : XML-based file that contains metadata information
about the subproject. This file references the .bib, .reg,
sources, and dirs files to build the subproject.
o .bib : A binary image builder (.bib) file used during the making
step in the build process to dictate files to include in the
binary image
o .reg : A registry file with settings to be included in the final
run-time image.

13. o Sources : A Windows Embedded CE sources file. This is a
makefile that contains build options to control the Windows
Embedded CE build process.
o Makefile : A file used in association with the sources file in the
indows Embedded CE build process

14. Catalog Component Dependencies
• The catalog in Platform Builder for Windows Embedded CE
6.0 R2 supports component dependencies. To specify that a
component is dependent on another component, you must
set the SYSGEN or Additional Variables field for the
component of the catalog item, and then include this value in
the form of an additional environment variable in the
dependent component

15. SDK
• Windows Embedded CE 6.0 R2 is a componentized operating system,
which implies that application developers require a customized SDK that
corresponds to your OS design in order to develop applications that will
work on your target device
• The custom SDK should not only include the required Windows Embedded
CE components, but also the headers and libraries for any custom
components that you included in the OS design, to avoid problems due to
missing files or libraries at build and runtime.
• Platform Builder provides an SDK export feature to generate SDKs and to
create an MSI package for convenient SDK deployment on application
development computers by means of an SDK Setup Wizard.

16. Building and
Deploying a Run-Time
Image

17. BUILDING AN IMAGE
• Compiling: generate executable (.exe) files, static (.lib) libraries,
dynamic-link library (.dll) files, and binary resource (.res) files according to
the selected locales
• Sysgen : creates import libraries for sdks. creates a set of run-time
image configuration files for the OS design, and builds the BSP based on
the source files in the Platform directory.
• Build phase : The build system processes the source files of your
Board Support Package and applications using the files generated during
the Sysgen phase.
• Make Run-time Image phase: create Nk.bin file which is
runtime image. Can be downloaded and run on target device.

18. Builduing and deploying runtime
image

19. Analyzing build errors
• Build.log: Contains information about the individual commands issued within
each phase during the build process. This information is useful for analyzing both
the build process in general, and build errors in particular.
• Build.wrn : Contains information about warnings generated during the build
process. If possible, try to eliminate or at least identify the reasons for the
warnings. The information in Build.wrn is also included in Build.log.
• Build.err: Contains specific information about build errors encountered during
the build process. This information is also available with additional details in
Build.log. This file is created only when an error occurs.

20. Deploying a Run-Time Image on a
Target Platform

21. Core Connectivity infrastructure supports the following
download layers for
deploying a run-time image:
• Ethernet
• Serial
• Device emulator
• USB
• Image update

22. Debugger Options
• Sample Device Emulator eXDI2 Driver : included in
Windows Embedded CE 6.0 R2. XDI is a standard hardware-
debugging interface
• KdStub : This is the Kernel Debugger. KdStub stands for kernel
debugger stub, which instructs Platform Builder and Visual
Studio to use the software debugger
• CE Dump File Reader : avaliable only when Error Report
Generator catalog item is added to your OS design

23. System performance and
programming
• Parameters affecting system performance
Processor utilaitzation : fraction of available
processing power that an application is able to
make use of
Response time : time it takes for the real-time
system to response to external stimuli.
jitter : the variation in the execution times of a
given periodic task