ICD In-Circuit Debugger

The TRACE32 In-Circuit Debuggers are highly cost effective tools for debugging on assembler or HLL level. The ICD-Debugger are mainly used as stand-alone debugger on a PC or workstation. But they are also offered as an extension to the In-Circuit Emulator TRACE32-ICE using the PODBUS connector on the ECU32. In this configuration they can be used to debug a second CPU on the target.

Host Interfaces

The ICD-Debuggers are connected to the host system via a high speed serial bus, the PODBUS. The PODBUS interface is available as:

Parallel interface through printer port (20-100 KByte/s in EPP mode)
(for upgrade only, not recommended for new systems)



Ethernet interface for PC and workstation (50-800 KByte/s pipelined)
(for upgrade only, not recommended for new debugger systems)

Additional pure software debuggers through RS232 interface are available for selected processor families (e.g. 68k, C167, H8S).

Debugger Configurations

The ICD-Debugger is based on the on-chip debug interface (e.g. BDM, ONCE, JTAG etc.). TRACE32-ICD supports all extra features offered by on-chip debug interface like hardware breakpoints or trigger capabilities. An optional EPROM/FLASH Simulator is provided to allow the settting of breakpoints in the ROM area.

Debugger BDM/JTAG Debugger
(not recommended for new systems)


PowerDebug BDM/JTAG Debugger with RISC Controller and USB Interface


PowerDebug BDM/JTAG Debugger with RISC Controller and USB/Ethernet Interface


PowerDebug II BDM/JTAG Debugger with RISC Controller and USB/Ethernet Interface

Integrated Debugger/Trace Configurations

For microcontrollers with NEXUS port an integrated Debugger/Trace/Performance-Analyzer System is on development.

PowerNexus NEXUS Debugger


PowerTrace BDM/JTAG Debugger with RISC Controller, Trace and USB/Ethernet Interface



PowerTrace BDM/JTAG Debugger with RISC Controller, Trace and USB/Ethernet Interface

ROM Monitor Configuration

The ICD-Debugger is based on a ROM Monitor solution. An 8KB monitor program may be located anywhere in the address space. The monitor can be linked and loaded separatly or ist can be linked and loaded along with the user program. To implement the monitor, some interrupt vectors must be reserved for the monitor program use and these must be allowed for in the target software design.
The communication between the Debugger on the host and the monitor program is done using an EPROM/FLASH simulator. The EPROM simulator can support two 8-bit or one 16-bit EPROM. The combination of several modules allows 32- or 64-bit configurations to be supported. During the simulation the EPROM configuration of the target system can be imitated by the software in the EPROM simulator. Using this technique paged or banked EPROM‘s can be simulated. For more information on the EPROM simulator refer to its documentation.

EPROM/FLASH Simulator

ICD Trace

The ICD trace module is a extension the TRACE32-ICD In-Circuit Debuggers. It is connected to the ICD Interface (and optional the ESI EPROM/FLASH Simulator) via the POD-Bus. The performance of TRACE32-ICD Debuggers can be considerably expanded by adding this trace capabilities. The extension now provides program flow information for debugging. This will also facilitate identification of which instructions or system states have caused a particular program state.

RISC Trace Module

PowerProbe Logic and Protocol Analyzer

The state/timing analyzer module is a full 64 channel logic analyzer module. It is connected via the POD-Bus.

PowerProbe Logic Analyzer

PowerIntegrator Logic Analyzer

The state/timing analyzer logic analyzer is especially designed for system integration. It is connected via the POD-Bus.

PowerIntegrator Logic Analyzer with MICTOR probes

Stimuli Generator

The Stimuli Generator is a extension the TRACE32-ICD In-Circuit Debuggers. 64 digital and 12 analog channels are available.

Stimuli Generator

Trigger Probe

The trigger probe enables the usage of external trigger events in an in-circuit debugger system.

Trigger Probe

Clip Set

Clip Set

PowerSupply

Power Supply

Multiprocessor Debugging

One PODBUS can controll up to 4 independent devices. Each device or each combination of devices is controlled by a different user interface. The TRACE32 software allows to start and stop multiple devices synchronously to offer multiprocessor debugging. Using this configuration e.g. one master can controll up to 3 slaves.