All Forums
 Microsoft Windows CE
 General CE
 Remote Ethernet Debugging without ActiveSync		  Forum Locked  Topic Locked
 Send Topic to a Friend
 Printer Friendly
Author Topic  

KnowledgeBase

296 Posts
Posted - 25 Feb 2002 :  17:54:40  Show Profile  Email Poster
Q: What if I don't want to use ActiveSync. Is there any other way to do remote Ethernet debugging?

Yes. There is a TCP/IP method for remotely debugging applications in eMbedded Visual Studio. Ethernet is much faster than RS-232 for application debugging, and is recommended for most application development.

You can use ActiveSync Ethernet debugging, but that method requires that you first set up a serial ActiveSync connection. TCP/IP debugging is very useful if you have difficulty creating an ActiveSync connection, or want to go directly to Ethernet debugging.

To use TCP/IP debugging, do the following (see updated instructions for CE.NET, below):
  1. In eMbedded Visual Tools, select Configure Platform Manager... from the Tools menu.

  2. Select a device that matches the SDK you're using and click the Properties... button.

  3. Click the Advanced button and select the Manual Server. Click Ok.

  4. Select TCP/IP Transport

  5. Click the Test button.
    The PC will pop up a dialog box with instructions about what to run on your CE device.

  6. In the Start Menu->Run dialog of your CE device, run \Windows\CEMGRC.exe with the parameters listed in the eV Tools dialog (see tip below to simplify this step in the future).

  7. Click Ok on your PC. The devices should connect successfully.

  8. You can now run any of the CE remote tools from your PC or begin a remote debugging session.

Tips:
  • The parameter you enter on your CE device includes the MAC address of your development PC. Only the first four digits of that parameter change each time you establish a connection.

  • You can make that parameter non-volatile by storing it in your ADSLOAD.REG file. It will appear in the list of applications in the Run dialog of your Start Menu.

    Use an entry like the following sample to replace the existing entry in your ADSLOAD.REG file:
      [HKEY_LOCAL_MACHINE\Explorer\RunHistory]
          "0"="CEMGRC /T:TCPIPC.DLL /D:02053439622831063a2ec02e31f001"

Troubleshooting tips:
  • Make sure both your PC and your device can see each other on the TCP/IP network (use IPCONFIG on each device, then PING from one computer to the other ).

  • Click the "Yes" button if you get the message, "The CPU does not support configuration ARM. Executable will not run on the Device. Continue? Y/N ?". This error message is based on a registry key that isn't yet included in many ADS CE images.

Here are some additional files and applications that can help if you want to use TCP/IP transport. These files are supplied "as is":
  • Client DLLs and applications (CE 3.0, CE.NET): Updated applications and libraries required for Ethernet debugging, if not included in your build of CE 3.0. Files included: repllog.exe, mansrv.dll, cemgrc.exe, cetlstub.dll, tcpipc.dll. ZIP 71kB

  • RunCEMgr: Simple application that automatically copies files needed for Ethernet debugging and starts client debug application. ZIP 12kB

  • ADS Go, v1.0: Similar in function to RunCEMgr, this application from Todd Earles at Icon Labs offers more sophisticated, dialog box control of CEMgr including the ability to restart if the connection is broken. ZIP 71kB

For information about using ActiveSync, see the ActiveSync topic index.

------------------
ADS Knowledge Base

Edited by akidder 25-oct-2002: Add instructions. Remove note that TCP/IP debug is not recommended.
Edited by akidder 29-oct-2002: Add note about error message that CPU doesn't support configuration ARM
Edited by akidder 29-may-2003: Clarify that the PC will give instructions about what to type on CE device
Edited by akidder 14-Jan-2004: Add debug files for CE.NET (e.g. for Bitsy Plus and other, older CE.NET builds)

akidder

1519 Posts
Posted - 25 Oct 2002 :  17:01:17  Show Profile  Email Poster
This is a quick and convenient way to create an Ethernet debugging session. See the expanded instructions above for details.
Go to Top of Page

whuh

23 Posts
Posted - 03 Oct 2003 :  14:09:25  Show Profile  Email Poster
#.NET

Update for CE.NET 4.1

To use TCP/IP debugging, do the following:
  1. In eMbedded Visual Tools, select Configure Platform Manager... from the Tools menu.
  2. Select the ADS device (e.g. IABitsyX for XScale, IAGM for CE.NET StrongARM or applicable SDK) and click the Properties... button.
  3. Select "TCP/IP Transport for Windows CE" for Tansport
    Nothing needs to be changed under the "Configure..." button
  4. Select "Manual Server" for Startup Server
  5. Click the Test button.
    The PC will pop up a dialog box with instructions about what to run on your CE device. E.g.
  6. In the Start Menu->Run dialog of your CE device, run CEMGRC with the parameters listed in the eV Tools dialog (see tip above to simplify this step in the future). For example,
    CEMGRC.EXE /T:TCPIPC.DLL /Q /D:192.168.0.30:1322
  7. Click Ok on your PC. The devices should connect successfully.
  8. You can now run any of the CE remote tools from your PC or begin a remote debugging session.
NOTE:The PC will prompt you to run CEMGRC each time you run a different tool; only the last four digits of the parameters will change.

Edited by akidder 6-Nov-2003: Add example of comand line settings; clarify SDK selection.
Go to Top of Page

jnosek

3 Posts
Posted - 06 Sep 2006 :  11:26:37  Show Profile  Email Poster
CE 4.2 and 5.0

Update for CE.NET 4.2 and 5.0

To use TCP/IP debugging, do the following:
  1. In eMbedded Visual C++, select Configure Platform Manager... from the Tools menu.
  2. Select the ADS device (e.g. IABitsyX for XScale, ADS XScale 4.2, ADS CE 5.0, or applicable SDK) and click the Properties... button.
  3. Select TCP/IP Transport for Windows CE for Transport
  4. Click the Configure... button and set to Fixed Port with the default value of 5000, and set Host IP to Use fixed address. Click Ok.
  5. Select Manual Server for Startup Server
  6. Click the Test button
    The PC will pop up a dialog box with instructions about what to run on your CE device
  7. From the command prompt of your CE device, run CEMGRC with the parameters listed in the eVC++ dialog. For example:
    CEMGRC.EXE /S /T:TCPIPC.DLL /Q /D:192.168.0.93:5000
  8. Click Ok on your PC. The devices should connect successfully.
  9. You can now run any of the CE remote tools from your PC or begin a remote debugging session.
Note:
The PC will prompt you to run CEMGRC each time you run a different tool.
Go to Top of Page
  Topic  
 Forum Locked  Topic Locked
 Send Topic to a Friend
 Printer Friendly
Jump To:
Eurotech Support Forums © Eurotech Inc. Go To Top Of Page
This page was generated in 0.03 seconds. Snitz Forums 2000