Windows CE supports a unified communications infrastructure called 
Core Connectivity that enables full-featured connectivity for downloading 
and debugging. The Core Connectivity infrastructure offers a full range
of connectivity support.

To ease the setup of a target board for debugging, we have included 
some folders named "Startup" that can be installed on the root of the 
NORFlash drive (or if the contained batch files are modified they
can be installed on a USB drive).  There are different Startup folders
for VS2005 and VS2008 because they contain different files.

Inside "vs2005 Startup" is a folder called "Startup" that should be
installed on the desired drive if using Visual Studio 2005. Likewise, 
inside "vs2008 Startup" is a folder called "Startup" that should be
installed on the desired drive if using Visual Studio 2008.

With the appropriate Startup folder installed, when the board boots up,
it will automatically prepare the target board for a debugging session. 
If you install the Startup folder on the USB drive there must be no 
Startup applications on the target board's on-board flash that 
would interfere with the Startup batch file process.  

When the target board boots up with one of these Startup folders, 
you will see something similar to the following in the command
prompt window...




Pocket CMD v 6.00
\> cd\Hard Disk\Startup\debug
\Hard Disk\Startup\debug> DEBUG.BAT
\Hard Disk\Startup\debug> copy *.* \windows
Copied 7 file(s).
\Hard Disk\Startup\debug> cd \windows
\windows> 
\windows> REM Show the IP address assigned to the board.
\windows> ipconfig   
Windows IP configuration Ethernet adapter [CS89501]: 
	 IP Address ........ : 10.0.2.220
	 Subnet Mask ....... : 255.255.255.0
	 Default Gateway ... : 10.0.2.1

	 DNS Servers........ : 10.0.2.1

\windows> 
\windows> REM Override sercurity for connection manager.
\windows> CoreConOverrideSecurity
Overriding CoreCon security...ok.\windows> 
\windows> ECHO OFF
Note that CONMANCLIENT2.EXE never exits.
\windows> 
\windows> conmanclient2  




Note that the command prompt window is inaccessible since 
conmanclient2 never exits.



To prepare Visual Studio for connecting
1.On the Visual Studio Tools menu, click Options, 
 then click Device Tools, and then click Devices.

2.Select Windows the target CE Device, and then 
  click Properties.  You must install the SDK
  for the device before it can be available
  for selection.

3.To the right of the Transport box, click Configure.

4.In the Configure TCP/IP Transport dialog box,
  select "Use specific IP address", and then type
  the device IP address shown in the command prompt
  window on the device (you may need to scroll
  the command prompt window to see it).

5.Close the dialog boxes.


In order to do remote debugging with a target, your project
must be created with a wizard for a "Smart Device" project.
(For .Net or managed code development, you must also select
the Smart Device subcategory "Windows CE 5.0". Yes, 5.0 is
used even though we are programming for 6.0).

After the application is ready, Select "connect to device"
 on the tools menu.  "Platform:" should be "Windows CE 5.0"
(again, not a typo) and you should select your target
device from the "Devices:" window, then press the CONNECT
button.  

A "Connecting" dialog box will appear and if everything
works okay, after a short delay it should say 
"Connection succeeded".  You can close this dialog 
box then press F5 to start the Deploy process.  Sometimes 
this process can take 30 seconds or more, especially
for .Net applications.