Open Interface Specifications: GDI and KDI

 Back to TASKING Products Page >>>
To satisfy almost any target environment - both in terms of hardware platform and software platform - TASKING's CrossView Pro debugger is designed with two important open standards. These APIs guarantee easy access and interfacing to CrossView Pro for customers, RTOS vendors, and manufacturers of target run control hardware (ICE, JTAG, BDM, etc.).
These two interfaces are:
  • KDI (Kernel Debug Interface)
  • GDI (Generic Debug Instrument Interface)
KDI describes the CrossView Pro interface to a kernel. Using KDI, a kernel vendor can implement a DLL turning CrossView Pro into an RTOS aware debugger. Rather than looking at kernel objects as raw data, the RTOS awareness allows CrossView Pro to present kernel data (queues, tasks, interrupts, events, etc.) in a format meaningful to the programmer. In addition, the capability of task qualified run control can be added.

GDI defines the interface between the execution environment (e.g. simulator, ROM monitor, emulator) and CrossView Pro. GDI supports enhanced features such as execution trace, code/data coverage and performance analysis. This open standard is the result of work done for the OMI/DEBUG project by the European Open Microprocessor Initiative (OMI). TASKING and a number of the world's leading ICE vendors participated in this initiative.

All available TASKING CrossView Pro debuggers conform to GDI and the KDI standards.

The KDI and GDI interface specifications are publicly available. RTOS vendors and hardware vendors can use them to make their product suitable for CrossView Pro or any other debugger supporting GDI and KDI.

Page Last Updated: November 28, 2002 11:08

Nohau UK Home >>>