|
xIDE includes three highly
integrated portions: powerful cross development tools and utility
programs run on host computer and destination machine; High efficiency,
crop-able CPU instruction level simulator; Multiple telecommunication
forms, such as: Ethernet, serial cable, USB, ICE etc, connect host
computer with destination machine
xIDE supports two debugging
model:
|
|
|
 These two model can work on hardware , CPU
instruction level simulator ,or both.
For debugging application
programs, we use stub model. Witch communicates with debugging module
in operating system and debugger of destination machine. If the
operating system of destination machine supports debugging, program
can be debugged directly. In contrast, some software are needed
to take over all exception handler and part of interrupt handler
of destination machine, insert portal communication debugging module
and interact with the debugger of host computer.
The necessary function of
debugger:
- Debugger communicates with destination operation system through
specified communication channels (serial port, parallel port,
adapter card, USB).
- Destination operating system passes all the exception handling
and the currently occurred exception number to communication module.
Then the debugger show xIDE user which type (break point, memory
page lacking etc) the being debugged process throws.
- Debugger translates the request, from user for modifying and
controlling the being debugged program, into the access to the
address space of the program or certain registers on the destination
platform, to response the request through destination operating
system.
For OS or frameware debugging,
we use On Chip Debugging model. We control the ICE on hardware developing
card through GDB.
|
