Debug Applications Using a Device Without KITL (Compact 2013)

  • Article

3/26/2014

In some instances, you may want to connect to a device without Kernel Independent Transport Layer (KITL). The following procedure provides instructions for doing so.

To debug application using a device without KITL

  1. Copy the device-side CoreCon binary files from the Application Builder installation folder, for example C:\Program Files (x86)\Common Files\Microsoft Shared\Embedded Tools\CoreCon\11.0\Target\wce800. If you are targeting ARM, copy the entire contents of the armv7 folder. If you are targeting x86, copy the entire contents of the x86 folder. You will see the following device side binary list:

    • clientshutdown3.exe
    • CMAccept3.exe
    • ConmanClient3.exe
    • DeviceAgentTransport3.dll
    • eDbgTL3.dll
    • TcpConnectionA3.dll

  2. Set the SYSGEN_NETUTILS variable in your OS design to include ipconfig.exe. This setting will allow you to provide the IP address to the remote tools shell on the desktop.

  3. Create an application. For more information, see Create Your First Application.

  4. In the Project Properties pane of your application project, in the Debugging/IP Address text box, enter the IP address of the device.

  5. Establish the TCP connection by launching ConmanClient3.exe and CMAccept3.exe on the device.

    Note

    CMAccept3.exe will time out after three minutes if the desktop does not accept the connection, and you will need to re-launch CMAccept3.exe.

  6. Set a breakpoint, and then press F5 to run the application.
    The remote debugging session is established, and the breakpoint for the application will stop the application.

    Note

    If you disconnect the debugging session (for example, if you close Visual Studio), you will need to re-launch CommanClient3.exe and CMAccept3.exe to establish the TCP connection for the next debugging session.