Automotive Platform Development
Windows Automotive version 4.2 provides you with tools, components, and code for designing an automotive platform using Platform Builder 4.2.
This section describes the general tasks for designing a platform based on Windows CE .NET and provides links to information specific to Windows Automotive.
Getting Started with Platform Development
To build a platform based on the Microsoft Windows CE .NET operating system (OS), you must complete the following major steps:
- Create a platform for prototyping using a Windows CE configuration with a standard development board (SDB).
- Customize the platform with additional projects and Catalog features.
- Build the OS image, download it to your SDB, and debug the platform using the debugging tools found in the Microsoft Platform Builder 4.2 integrated development environment (IDE).
- Create a boot loader and board support package (BSP) for your specific target device.
- Rebuild the OS image using your new BSP, download it to your target device, and debug the platform.
- When the platform is complete, export a software development kit (SDK) for your platform application developers.
The following illustration shows the sequence of tasks in the process of creating a Windows CE-based platform with Platform Builder:
In a typical platform development scenario, you first download your OS image to a sample hardware platform, such as the Windows CE PC-based hardware development platform (CEPC). Platform Builder includes boot loaders and BSPs for the CEPC and many other hardware development platforms.
After refining and debugging your platform on a hardware development platform, you adapt it for your custom target device. You must create a boot loader and an OEM adaptation layer (OAL) before you can download your OS image to your target device. The OAL is a layer between the kernel and the target-platform hardware.
Once you have completed your platform, you export a custom SDK. Application developers can import your SDK into Microsoft eMbedded Visual C++ 4.0 and write applications for your platform.
Platform Development Tasks
The following table lists the tasks in the process of designing a platform based on Windows Automotive.
For each task in the chart, a link is provided that goes to a topic in the PB Help documentation that provides detailed information about performing the task. While the process for developing a platform is well-documented within the PB help topics, note that several steps in this process are customized for automotive platform development. The basic process is described at the link in the “Topics in PB Help” column. The automotive-specific process steps, if any, are described at the link in the “automotive-specific topics” column.
Users should use the topics in the PB Help documentation and the topics in this section for complete information about completing each platform development task.
|Task||Description||Topics in PB Help||automotive-specific topics|
|Creating a Platform||In this task, you configure your platform using the New Platform Wizard and select the features that you wish to include in your platform.||Platform Creation||Using the PB Catalog with Windows Automotive|
|Customizing a Platform||In this task, you can add, delete, or modify platform features.||Platform Customization||Compiling for a Target Device|
|Building a Platform||In this task, you build custom source code and generate an OS image.||Platform Building||Using the CEPC with Windows Automotive|
|Downloading an Image||In this task, you connect to a target device and download your platform.||Platform Downloading|
|Adding Features to a Platform||In this task, you add features to your platform.||Feature Additions to a Platform|
|Debugging a Platform||In this task, you use the new tools and capabilities of PB 4.2 to debug platforms and features.||Platform Debugging|
|Creating a Boot Loader||In this task, you create a boot loader for downloading and debugging code from a development workstation to a target device.||How to Develop a Boot Loader|
|Creating an OEM Adaptation Layer||In this task, you develop an OAL for a target device.||How to Develop an OEM Adaptation Layer|
|Creating and Exporting an SDK||In this task, you create and export an SDK and use Platform Manager features.||Software Development Kit Customization|
|Profiling your Platform||In this task, you can profile your platform to measure operating system performance on your platform.||Instrumented Kernel Profiling and Monte Carlo Profiling|
|Localizing your Platform||In this task, you can adapt your platform for a specific international market, or locale.||Platform Localization||Building a Localized Product|
NOTE To bookmark this topic for future reference, select Favorites in the left window of the HTMLHelp viewer and then click Add.
SECURITY NOTE A target device can be booted only from the flash memory in the system that contains the OEM-approved ROM image. The device cannot be booted from a CD-ROM or PCMCIA/CF slot. This prevents end users from installing their own OS to bypass Windows Automotive security to access the device’s data or programs.