Hello Jay,

My understanding of the CE debug process is a bit shaky as well, but here's some things to try until the pros some to the rescue.

I assume you are debugging through KITL and ethernet, so the things I go through when building a debug image are:

- Remove the networking driver from the project feature view
- add the environment variables for shared ethernet as described in the app note "Building a WinCE image on the LH7A400"
- add kitl:true to your boot script

If you are using KITL to connect, I guess the kitl:true is the critical issue here.

Let us know how it goes,

Andreas

Hi Andreas

I agree with you that understanding WinCE Debug process is cryptic.
Through trial and error I realised that one solution that works consistently is
- Change network driver for Local Area Networking(LAN) devices from the "lpd_SmSC_91C111_Async_rel_100" to "Cisco 802.11b PC Card".

This is for the benefit of others struggling to get CE in debug mode using KITL.

Thank you.
Jay.

Hi Jay,

File that under non-obvious solutions to WinCE debug problems.

Could you please confirm if your debug process still fails if no ethernet driver at all is used? (delete driver so there is no entry for networking under 'Device Drivers' in your platform builder tree).

In the Logic docs, it is explained that the ethernet driver should be removed for KITL debug as KITL provides it's own driver.

Thanks,

Andreas

Jayesh,

Are you trying to include the SmSC Ethernet driver in the debug image? Debugging via KITL and using that stand alone Ethernet driver are mutually exclusive. Other than that, debug should work fine. At least we haven't had any problems here and no-one else seems have reported any major issues.

As to ActiveSync, if you look in the registry file for the USB function driver, most likely found here:

X:\WINCE420\PUBLIC\lpd_Drivers\lpd_LH7A400_USBF_rel_100\lpd_LH7A400_USBF_rel_100.reg

you will see a comment detailing all of the components you need for ActiveSync to work on your device.

I'll repeat them here for your convenience:

; * In order for ActiveSync to work properly, you must include the
; * following components in your Windows CE image:
; *
; * - ActiveSync (Applications - End User)
; * - Dial Up Networking (Communication Services and Networking->WAN)
; * - Telephony API (Communication Services and Networking->WAN)
; * - Network User Interface (Shell and User Interface->User Interface)
; * - Working COM port

Best regards,

--mikee

I'm having issues with getting the debug functionality going as well. I have a different target (blank PC server box) and use the CEPC BSP... and the debugger runs fine. I have 1. compared the two workspaces side by side, 2. have looked over this message board and 3. the tutorial mentioned in this thread. I'm at a loss or just don't see my problem. Any help would be greatly appreciated. I am using TeraTerm and have the serial port connected to the target, the host and target connected via Ethernet and have a touch screen connected. The image downloads and starts up fine. I know I'm missing something stupid.

Host:
* Windows XP
* Platform Builder 4.2
* TeraTerm 2.3

Target:
* 80000116 - 0001 REV F03
* LogicLoader Version 1.4.3-LLH7a400_10 0001

The following are a list of things configured in my workspace:

* I removed "Networking" component under Device Drivers of the BSP as instructed.
* KITL transport component added under Platform Manager
* Under Platform Settings in the Build Options tab I have defined the following:
- Enable CE Target Control Support
- Enable Eboot Space in Memory
- Enable Kernel Debugger
- Enable KITL

The rest I do not have defined...which include:
- Enable Event Tracking During Boot
- Enable Full Kernel Mode
- Enable Image for Flash
- Enable Images Larger than 32MB
- Enable Profiling
- Flush Events to Release Directory

* Both 'Download:' and 'Kernel Transport:' under "Configure Remote Connection" are set to Ethernet and configured properly (I get the LOCE_* string).

* The Default Device under "Configure Windows CE Platform Manager..." has KITL for Transport and CESH for the Startup Server.

* After successful download and checksum, I use "Send file..." under TeraTerm to send the following boot parameter string:
- exec rtc:rtc_a400_int:dbg_serial:A400_UART:share_eth:1:kitl:true:disp_num:2

* After the exec boot parameters are executed, I get the following messagein the debug window of Platform Builder:
Kernel debugger is waiting to connect with target.

After I click the disconnect button in Platform Builder I get the following
messages in the debug window of Platform Builder:
Kernel debugger failed to connect with target (KDBG open stream failed).
Debugger could not initialize connection.

Thanks,
Matt

matt123,

Everything looks pretty good, except I think that you are missing a couple of items from the 'exec' command line. You need to ensure to include the following keys and correct values (Complete documentation should be found in the LoLo User's Manual):

dbg_enet:91C111 (Tells the OAL which Enet driver to use)
dbg_enet_base:0x70000000 (Location of Enet chip)
dbg_enet_irq: (Which IRQ the chip is hooked to)

Values are:
0x0000001a for a rev-A Card Engine
0x00000007 for a rev-B Card Engine

Also, look in the file x:\WINCE420\PLATFORM\LoCE_A400_rel_xxx\platform.bat and read the documentation concerning the environment variables BSP_NOSHAREETH and IMGNOSHAREETH to ensure that they are set the way you want them.

Let me know if this helps.

--mikee