Connecting CE 6.0 Device to VS2005 Development Station 1

Introduction

Corecon is used to establish connection between CE 6.0 device and Visual Studio 2005 development station for the purpose of downloading VS2005 application onto the CE 6.0 device for testing and debug.

Connecting CE 6.0 Device to VS2005 Development Station

For the purpose of this article, the following condition is assumed. eBox-2300 (x86 device) is used as example for this article. CE 6.0 image is built and deployed on eBox-2300. A SDK is created from the OS Design project, used to build the CE 6.0 image for eBox-2300, and installed onto the VS2005 development station. A Windows CE device application is cr

Preparing eBox-2300 to Connect to VS2005

The following Corecon component files need to be copied to the CE 6.0 image running on eBox-2300

• Clientshutdown.exe • ConmanClient2.exe • CMaccept.exe • eDbgTL.dll • TcpConnectionA.dll

The above files are installed during Visual Studio 2005 installation and locate in the following directory.

..\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\..

Corecon files supporting different CPU families are provided and placed in separate sub-folder, with corresponding CPU name, under the above directory.

Note: Corecon component files can be included with the OS Design and build into the resulting CE 6.0 image. A Corecon component for CE 6.0 is available for download at the following URL.

http://www.embeddedpc.net/download.htm

The eBox-2300 IP Address is needed when setting up the device properties within VS2005 to establish connection between eBox-2300 and VS2005 development station.

• From eBox-2300 desktop, with CE 6.0 running, click on Start | Run from CE 6.0 desktop with the cmd command to open a console command window.

Fig. 1 - CE 6.0 desktop – executing cmd command

Samuel Phung [eMVP] samuelp@embeddedpc.net

Connecting CE 6.0 Device to VS2005 Development Station 2

• From within the console command window, type s IpConfig to view the eBox’s assigned IP-address.

Fig. 2 - CE 6.0 console command window

Now that we have eBox-2300’s IP address, let’s move to VS2005 IDE to configure device settings. In order for this to work, both the VS2005 development station and eBox-2300 must be connected to the same LAN segment and acquire their IP address from the same DHCP server.

From VS2005 IDE, set the target device to “eBox2300_WinCE600_SDK x86 Device”

Fig. 3 - VS2005 IDE / select target device

From VS2005 IDE, select Tools | Options…

Fig. 4 - VS2005 Tools Options

Samuel Phung [eMVP] samuelp@embeddedpc.net

Connecting CE 6.0 Device to VS2005 Development Station 3

• On the left, click to expand the “Device Tools” folder and select the “Devices” sub-folder.

• On the right, select eBox2300_WinCE600_SDK from the list of available platform in the Show devices for platform combo text box.

• Click on the Properties button to bring up eBox2300_WinCE600 x86 Device Properties setting screen

Fig. 5 - eBox2300_WinCE600 x86 Device properties

• Click on the Configure button to bring up Configure TCP/IP Transport

• Select Use specific IP address and enter eBox-2300’s IP address

Fig. 6 - Configure TCP/IP Transport / Set device IP Address

• Click OK and to commit device IP address setting.

Connecting eBox-2300 to VS2005

To initiate connection between VS2005 development station and eBox-2300 using Corecon, take the following steps to launch ConmanClient2.exe and cMaccept.exe Corecon components from eBox-2300.

• From eBox-2300 desktop, with CE 6.0 image created in the earlier steps running, double click on My Device and open the Windows folder.

• From the Windows folder, double click on ConmanClient2.exe follow by double click on cMaccept.exe to launch Corecon connection service.

• From Visual Studio 2005 IDE, select Tools | Connect to device… and select eBox2300_WinCE600_SDK from the list of available devices, and click on the Connect button.

Samuel Phung [eMVP] samuelp@embeddedpc.net

Connecting CE 6.0 Device to VS2005 Development Station 4

Fig. 39 - Connect to Device (eBox-2300)

When connection is successful, the Connecting dialog box will display Connection succeeded to indicate a successful connection.

Fig. 40 - eBox-2300 connected

At this point, you can deploy VS2005 application onto to eBox-2300 for testing and debug.

Samuel Phung [eMVP] samuelp@embeddedpc.net