| Author |
Topic |
|
|
jnosek
3 Posts |
 Posted - 30 Aug 2006 : 13:36:47
|
Ethernet Debugging in Visual Studio 2005
If ActiveSync is not available as an option for debugging, it is still possible to debug over ethernet in Visual Studio 2005. This MSDN article gives instructions on how to set up your device and Visual Studio for debugging over ethernet. Our tests here at ADS have resulted in the modified set of steps for ethernet debugging listed below.
This process has been tested to work on WinCE 5.0 Builds communicating over ethernet and wireless.
Device Preparation
- Copy the following list of files, found on your development machine here: C: Program Files -> Common Files -> Microsoft Shared -> CoreCon -> 1.0-> Target -> wce400 -> armv4i.
to the Windows folder of your device
- Clientshutdown.exe
- ConmanClient2.exe
- CMaccept.exe
- eDbgTL.dll
- TcpConnectionA.dll
Note: These files will be erased on power-off or reboot since they are not a part of the OS image. You can use the ADSCopy Utility to have it automatically copy the files from the flash disk into the /Windows folder every time the board boots.
- From the command prompt on the device, run conmanclient2.exe.
- Determine the IP address of the device.
Visual Studio Preparation
- On the Visual Studio Tools menu, click Options, then click Device Tools, and then click Devices.
- Select Windows CE 5.0 Device, and then click Properties.
- To the right of the Transport box, click Configure.
- In the Configure TCP/IP Transport dialog box, check Use fixed port number (the default value should be 5655), select Use specific IP address, and then type the device IP address.
- Close the dialog boxes.
Note:
Make sure to disable your Windows Firewall. Connection issues have been seen with PCs that have the firewall enabled.
Establish the Connection
- At the command prompt on the device, run CMaccept.exe.
Note:
It is best to run this command right after running ConmanClient2.exe.
- Within three minutes, connect to the device.
Note:
For each connection made (ie. debug session, deployment, etc.), you may have to run CMaccept.exe again, or possibly ConmanClient2.exe followed by CMaccpet.exe.
edited by M.Grenier, 26 Sept 2007: Changed the following: FROM: C: Program Files -> Common Files -> Microsoft Shared -> CoreCon -> 1.0-> Target -> wce400 -> armv4
TO: C: Program Files -> Common Files -> Microsoft Shared -> CoreCon -> 1.0-> Target -> wce400 -> armv4i |
|
|
cbadr
154 Posts |
Posted - 09 Oct 2008 : 18:26:35
|
Notes:
1. If ConmanClient2.exe does not return, open another command promt to run CMaccept.exe and continue with the rest of the instructions.
2. The files you copy to the Windows folder of the device should originate from your development machine. If you copied them initially from a different computer, they may not work when you try to connect from your development machine.
|
 |
|
| |
Topic |
|
|
|
All Forums
Microsoft Windows CE
Ethernet Debugging in Visual Studio 2005
Forum Locked
Topic Locked
Send Topic to a Friend
Printer Friendly