perform a build starting with the Sysgen step.
Sysgen operations can take up to 30 minutes to complete. To save time, do not run Sysgen every time you change the OS design. Instead, run Sysgen after adding and removing all desired components.
2. Follow the build process in the Output window. Examine the build information to identify the SYSGEN, BUILD, BUILDREL, and MAKEIMG steps. You can press Ctrl+F to display the Find And Replace dialog box, and then search for the following text to identify the start of these phases:
a. Starting Sysgen Phase For Project The SYSGEN steps start.
b. Build Started With Parameters The BUILD steps start.
c. C:WINCE600Build.log The BUILDREL steps start.
d. BLDDEMO: Calling Makeimg — Please Wait The MAKEIMG steps starts.
3. Open the C:Wince600 folder in Windows Explorer. Verify that Build.* files exist.
4. Open the Build.* files in a text editor, such as Notepad, and examine the content.
Figure 2-8 Building an OS design
Configure Connectivity Options
1. In Visual Studio, open the Target menu and select Connectivity Options to display the Target Device Connectivity Options dialog box.
2. Verify that CE Device is selected in the Target Device list box.
3. Select Device Emulator (DMA) from the Download list box.
4. Select Device Emulator (DMA) from the Transport list box.
5. Select KdStub from the Debugger list box, as illustrated in Figure 2-9.
Figure 2-9 Setting Target Device Connectivity Options
Change the Emulator Configuration
1. Next to the Download list box, click the Settings button.
2. In the Emulator Properties dialog box, switch to the Display tab.
3. Change the Screen Width to 640 pixels and the Screen Height to 480 pixels.
4. Switch to the Network tab.
5. Select the Enable NE2000 PCMCIA Network Adapter And Bind To check box, then select the Connected Network Card option from the list box, as illustrated in Figure 2-10, and then click OK.
6. Click Apply to save the new device configuration.
7. Click Close to close the Target Device Connectivity Options dialog box.
Figure 2-10 Device Emulator network options
Test a Run-Time Image on the Device Emulator
1. In Visual Studio, open the Target menu, and then click Attach Device.
2. Verify that Visual Studio downloads the run-time image to the target device. The download can take several minutes to complete.
3. Follow the debug messages during the start process in the Visual Studio Output window.
4. Wait until Windows Embedded CE has completed the start process, and then interact with the Device Emulator and test the features of your OS design, as illustrated in Figure 2-11.
Figure 2-11 Windows Embedded CE device emulator
Chapter Review
The Windows Embedded CE build process includes several phases and relies on a variety of build and run- time image configuration files to compile the source code and create the run-time image. It includes a compile phase to generate .exe files, static libraries, DLLs, and binary resource (.res) files for the BSP and subprojects; a Sysgen phase to filter and copy source code based on SYSGEN variables from the Public folder for catalog items selected in the OS design, and create a set of run-time image configuration files; a Release Copy phase to copy the files from the BSP and subprojects required to build the run-time image into the release directory; and finally a Make Run-time Image phase to create the run-time image from the content in the release directory according to the setting specified in .bib, .reg, .db, and .dat files.
You can examine the build process if you analyze the information that Platform Builder generates and tracks in Build.log, Build.wrn, and Build.err files. The Build.log file contains detailed information about every build command issued in each build phase. Build.wrn and Build.err contain the same information, but filtered for warnings and errors encountered during the build process. You do not need to open these text files directly in Notepad. It is more convenient to work with build status information and error messages in Visual Studio. The Output window and the Error List window provide convenient access.
Build errors can occur for a variety of reasons. The most common causes are compiler and linker errors. For example, running build commands in an incorrectly initialized build environment will lead to linker errors when environment variables that identify library directories in the Sources file point to invalid locations. Other important build configuration files, such as Dirs files and Makefile.def, can also rely on SYSGEN variables and environment variables in conditional statements and in directory paths.
Having successfully generated a run-time image, you can deploy Windows Embedded CE on a target device. This requires you to configure a device connection based on the Core Connectivity infrastructure. The final deployment step is simply to click the Attach Device command that you can find on the Target menu in Visual Studio with Platform Builder for Windows Embedded CE 6.0 R2.
It is important that you are familiar with the following configuration files, which control the Windows Embedded CE build process:
¦ Binary image builder (.bib) files Configure the memory layout and determine the files included in the run-time image.
¦ Registry (.reg) files Initialize the system registry on the target device.
¦ Database (.db) files Set up the default object store.
¦ File system (.dat) files Initialize the RAM file system layout at start time.
¦ Dirs files Determine which directories to include in the build process.
¦ Sources files Define preprocessing directives, commands, macros, and other
