Hardware Assisted Debug for Windows CE via eXDI2
When using Microsoft's Platform Builder for development of a product based on XScale or other ARM - based embedded processor, interfaces
are provided so that you can link directly to the target for debug purposes.
There are two ways in which this link can be achieved.
If your target is networked, then you can make an Ethernet connection
via the KITL protocol. This will give you a certain level of target control,
but of course, since you are debugging the processor which is responsible
for the network connection, you cannot intervene in a way which will stop
the connection. For example, you cannot halt the processor, and expect
to maintain a debug connection!
However, if your target is not networked, if you are debugging the
bootloader or developing drivers, bringing up new hardware, or if you
prefer in-depth control of the target, then you can achieve hardware-assisted
debug by interfacing via the eXDI protocol directly to the on-chip debug
facilities of the ARM, XScale or MIPS processor, via the JTAG debug port.
To achieve this, you need a JTAG interface which is designed to support
your embedded processor, and also to talk to Platform Builder. The Sophia Systems EJ-Debug probe Interface is designed for this task.
When you install the EJ-debug interface, the supplied Watchpoint debugger connects to Platform Builder via its own eXDI2 driver, and appears as a plug-in in the Platform Builder environment, enabling your debug session to communicate transparently with the hardware. EJ-Debug is ideal for both BSP and application development, and is seamlessly integrated into the Microsoft environment.
Direct Insight are experts in Windows Embedded CE development for ARM, XScale and MIPS targets. Please don't hesitate to make contact if you think we might
be able to help. You can contact us to request
further information or call
our team on +44 1295 768800.
 |
Take The Next Step...
|
 |
|
|