This article assumes that the developer knows how to debug applications using the standard processes such as activesync. This particular process is for users that do not require activesync to be on their device or prefer to use a more robust method of debugging.
Tools required:
Visual Studio 2003
Windows CE
Install PowerToys from MS website
SDAuthDevice.exe for your processor type from PowerToys
Ethernet cable (straight through or crossover, dependant on your product)
-
Start Visual Studio 2003 and open your project that you want to debug on the device.
-
Start Windows CE.Net ensuring that you place SDAuthDevice on the Windows CE device on the CE device turn on the device and plug the Ethernet cable into both the device and the PC.
The next thing you need to do is set up the CE device and the pc so that they can communicate with each other. In order to do this you need to double click the SDAuthDevice.exe file on the device which should come up with a list of IP addresses that the device is set to for each Ethernet port that the device has. This is the IP address that you will link to from your pc e.g. 192.135.1.1 and click start. Then put your IP address on your PC to the same range as the device i.e. 192.135.1.130. Go into Visual Studio on your PC and run the Smart Device Authentication Utility from the Tools menu bar. Put the IP address in as the same as the device that you are connecting to i.e. 192.135.1.1. Once it has said that it has connected close the application and go to the Device Options in Visual Studio, select the Windows CE.Net device and select Transport as TCP Connect Transport and click on the Configure button. This will give you a form with a list of configuration settings. Ensure that the IP address is set to your device IP Address, NOT obtain IP address automatically using ActiveSync and if you have closed off most ports on your device select a port that you know is going to allow connections.
You are now ready to start debugging your programs on the CE platform. To do this you need to ensure that when you run the application you deploy the application to the Windows CE.Net Device not the emulator. This will send the CAB files to the device, deploy the CAB files and install your software and allow you to remotely debug your code.
If you are running on a bespoke device be aware that you may have to re-set your registry settings to get your own third party softwares to run again. We have had this issue in our office and we have a registry cab file with our original registry settings and re-set them to this! You can use the Embedded C++ tools to capture the registry values from your device and export them into a file... You need to put them into a CAB file to then re-install these settings onto your device. Best of luck!
posted @ Sunday, June 05, 2005 6:50 PM