You can debug a Windows Embedded Compact application right on your device as you develop it. This debug method uses an Ethernet connection and Visual Studio, but it does not require you to use Platform Builder. That is, your application is a stand-alone Visual Studio solution; it is not a subproject of an OS design solution in Platform Builder. This article is intended for developers who have intermediate knowledge of Windows Embedded Compact.
In this article:
Before you begin this procedure, verify that your setup meets the following software, hardware, and network prerequisites:
In order for your development computer to connect to your device, copy the following files to any directory on your device by using Windows Explorer and a USB drive:
On your development computer, these files are automatically installed when you install Visual Studio 2008. They typically install to C:\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\Wce400\<Target device>. For example, the files to use for the TI OMAP 3530 EVM: ARMv7 BSP are in C:\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\Wce400\Armv7.
Obtain the IP address of your device by doing a command-line search of the Ethernet adapter settings.
To obtain the IP address of your device
ipconfig
You need to prepare Visual Studio to connect to your device before you prepare your device to connect with Visual Studio.
To prepare Visual Studio to connect to your device
Visual Studio is now prepared to connect to your device. In Step 4, you prepare your device to connect to Visual Studio.
Now that you have set up Visual Studio to connect to your device, you need to prepare your device to connect to Visual Studio.
To prepare your device to connect to Visual Studio
conmanclient2
cmaccept
You can now debug your application on your device.
Windows Embedded Compact
Windows Embedded Compact on the TechNet Wiki
W. Giberson edited Revision 1. Comment: Updated title to include "Windows Embedded Compact 7"
Regarding Step 4.2, it's much simpler to:
Enter 'start conmanclient2'; the command prompt will return, allowing 'cmaccept' to be entered without having to open a new command prompt and relocate the connectivity files.