Customizes the wince5.0 SDK with a simulator and supports ActiveSync debugging.

Source: Internet
Author: User

This article from csdn blog, http://blog.csdn.net/Veabol/archive/2009/09/04/4520154.aspx

 

Objective: To generate a wince5.0 application for Visual Studio and EVCProgramAnd has two debugging functions: simulator and directly connect to the device.

 

Software environment: wince5.0 platform Builder

 

The following content is for armv4i CPU, and other CPU processes are similar.

1. In addition to building the OS BSP for your own device, you also need another BSP: "deviceemulatorbsp. MSI", which is the armv4i simulator BSP provided by Microsoft and can be downloaded from the official website.

2. Build a simulator image:

1. Install deviceemulatorbsp. After the installation is complete, there will be a using the CE deviceemulator. rtf file in the wince500 \ platform \ deviceemulator Directory, which details how to create an SDK with a simulator.

2. Run platform builder to create a new platform. My name is emulator. BSP select Microsoft deviceemulator: armv4i, design template select mobile handheld, application & media are free, Networking & Communications only select local area network (LAN)-> WIRED local area network, and the rest are removed. Finally, complete the wizard.

3. To develop a hosting program, add the core OS of catalog View> Windows CE devices> Applications-End User> cab file installer/uninstaller.

4. Add ActiveSync (optional) in the catalog view's core OS-> Windows CE devices-> Applications-end user directory.

5. added storage support. Partition driver and fat.

Partition driver in core OS-> Windows CE devices-> file systems and data store-> Storage Manager-> partition driver

Fat in core OS-> Windows CE devices-> file systems and data store-> Storage Manager-> FAT file system.

6. Open the menu platform-> setting, which has three options to be set:

1) under the build options tab, remove enable ce target control support and enable kitl; (if not removed, it may lead to a black screen of the simulator)

2) on the environment tab, add the environment variable ce_modules_serial = 1, which is used to add DMA. (This is important)

3) the locale tab is used to add the language support you want. You can change it or not.

7. Add other required components as needed.

9. buildos-> sysgen.

The final NK. Bin is generated.

3. Build the OS image under your BSP. The steps are basically the same (2) (assuming myplatform)

4. Generate SDK (refer to using the CE deviceemulator. rtf)

1. Run the SDK wizard (platform-> SDK-> New SDK), fill in the necessary information, and check all supported development tools.

2. Use notepad and other tools to open \ wince500 \ pbworkspaces \ myplatform \ exportsdk. sdkcfg

3. Locate the <propertybag name = "deviceemulation"> section and add the following information:

<Propertybag name = "deviceemulation">

<Property name = "default image"> 1 </property>

<Propertybag name = "1">

<Property name = "imagename"> my emulator </property>; (name of the simulator displayed on)

<Property name = "vmid"> {6cb9c6e3-e576-4580-bc1e-aded62b97ffb} </property>

<Property name = "Default skin"/>

<Property name = "height"> 400 </property>

<Property name = "width"> 240 </property>

<Property name = "bitdepth"> 16 </property>

<Property name = "Memory"> 128 </property>

<Property name = "bin DEST"> emulator \ nk. Bin </property>

<Property name = "Fixed Screen"> 1 </property>

<Property name = "cpuname"> armv4i </property>

<Property name = "dpix"> 96 </property>

<Property name = "dpiy"> 96 </property>

<Property name = "supportrotation"> 0 </property>

<Property name = "enabled"> 1 </property>

<Property name = "bin path"> </property>

<Property name = "Ethernet"> 1 </property>

<Property name = "ports"> 1 </property>

<Property name = "additionalparameters">

</Property>

<Propertybag name = "skins"/>

</Propertybag>

</Propertybag>

Modify the screen size and other information of the simulator according to the instructions in this document. Add the following content:

<Propertybag name = "added Files">

<Propertybag name = "{3b388597-0924-4102-adfa-2519d2c3e11b}">

<Property name = "Source"> C: \ wince500 \ pbworkspaces \ emulator \ AddFile </property>

<Property name = "destination"> emulation </property>

<Property name = "subfolders"> 0 </property>

</Propertybag>

</Propertybag>

C: \ wince500 \ pbworkspaces \ emulator \ AddFile this path is self-built and stores the NK of the emulator. bin (only this file is put here; otherwise, all contents in this directory will be compressed when the SDK is generated) and then save the file.

4. Platform-> SDK-> build SDK is waiting for completion.

5. Install the SDK and configure the simulator (refer to using the CE deviceemulator. rtf for this part)

6. If you cannot connect to the simulator, turn off Vs and delete the files under C: \ Documents and Settings \ xxxxxx \ Local Settings \ Application Data \ Microsoft \ corecon \ 1.0 (we recommend that you back up the files first) enable Vs and reconfigure the simulator to connect.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.