Re: Debugging Kernel using eXDI interface from Platform Builder
From: Dariusz Czarnecki (Dariusz.Czarnecki_at_lumel.com.pl)
Date: 06/08/04
- Next message: Fred: "How to know the device name to operate on it?"
- Previous message: Tweeeek: "Bootloader wince.net 4.2"
- In reply to: dan: "Debugging Kernel using eXDI interface from Platform Builder"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 8 Jun 2004 15:55:10 +0200
Hi,
I'm using JTAG (EPI MAJIC) to debug the kernel and other modules.
> 1. How to download the image throught the eXDI interface(JTAG)?
I have ethernet bootloader burned in Flash an I'm downloading image to RAM
that way.
I know that it is tool to download via eXDI but I is probably much slower
than ethernet.
The tool is "Microsoft's RAMDAX (RAM Download and Execute) Utility Plugin" I
have never used it.
> 2. Which kind of image is used, release or debug?
Probably debug will be better because of optimised release code is harder to
debug, but debugging release is also possible.
> 3. Should the image built with special memory configuration in order
> to match the breakpoint to the source code during debugging?
I have no special memory configuration for hardware debugging.
I have problem debuging exe files (other than nk.exe) as I described in my
previous post. I described in that post my solution for debugging exe files
(processes) so maybe it will be helpfull.
- Next message: Fred: "How to know the device name to operate on it?"
- Previous message: Tweeeek: "Bootloader wince.net 4.2"
- In reply to: dan: "Debugging Kernel using eXDI interface from Platform Builder"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
