Accessing the Target System the Way You Like ?

Overview about communication channels with the supported microcontrollers

Controller Peripheral	Transfer rate1)	Speed rate2)		Monitor	UAD2 compact	UAD2+	UAD2	UAD	fast -PC6x	Host PC4)
Reference Board3) ASC	RS232 57600 bps	1
ASC0/ASC1	RS232 1 Mbps	3
ASC0/ASC1	TTL 1 Mbps	3
SSC	RS485 2,5 Mbps	10
SSC	TTL 2,5 Mbps	10
3PIN (SoftwareSSC)	RS485 variable	2
3PIN (SoftwareSSC)	TTL variable	2
3PIN (Hardware3Pin)	TTL variable	10
CAN	CAN 1 Mbps	5
JTAG (C166CBC)	LVTTL 20 MHz	74 57		no
JTAG (XC16x)	LVTTL 20 MHz	35 179		no
JTAG (TriCore)	LVTTL 50 MHz	140 222		no
JTAG (ARM7, ARM9)	LVTTL 20 MHz	35 71		no

Controller Peripheral	Interface	Speed rate2)		Monitor	UAD2 compact	UAD2+	UAD2	UAD	fast -PC6x	Host PC4)
JTAG5) Parallel Port	TTL	2		no

For a detailed description of the available communication interfaces please use the MCU and Tool Selection form.

Debugging via Monitor Solution

• Available for ALL C16x, XC16x, ST10 and TriCore derivatives
• Access to even the latest derivatives when emulators are not yet available
• Supports communication to the host PC via different high-speed serial interfaces
• Even if the application uses all of the serial ports, debugging is possible via generic port pins
• Portable Monitor Toolkit for accessing proprietary target system hardware
• Service Monitors for above mentioned communication path available - the ideal solution for on-site application parameter setup
• ASC Bootstrap loader + ASC / SSC / CAN / 3Pin (depends from supported derivative) combines availability of special interfaces with the convenience of ROMless debug target systems
• CAN Bootstrap loader (depends from supported derivative) makes the debugging of ROMless debug target systems faster (for ST10F276 available and for XC16x and TriCore in preparation)
• Service Monitors for all interfaces available for integrating into the product. Especially useful for on-site control and parametering the application.

To be able to use the various communication interfaces, monitor programs are required for the target sytems. Two ways of generating and loading of the monitor code are available:

1. ROM Monitor Solution: The monitor code may be derived and built from a monitor source library according to the user's demand. This monitor hex code can be flashed into the nonvolatile target memory, i.e. into FLASH or EPROM memory. After the "flashing" of the monitor code, the monitor will be executed directly after the power on.
2. Bootstrap loader / RAM Monitor Solution: A configurable predefined monitor may be adapted to the used target hardware. This monitor will be downloaded via ASC Bootstrap loader or CAN Bootstrap loader into the target and executed before every debug session. The CAN Bootstrap loader is available for ST10F276 and other new devices only.

The following communication channels are available as ROM Monitor or as ASC Bootstrap loader / RAM Monitor:

• Asynchronous serial RS232 interface via ASC0 Interfac.
• Asynchronous serial TTL interface via ASC0 Interface.
• Asynchronous serial RS485 interface via ASC0 Interface.
• Synchronous serial RS485 interface via SSC Interface.
• Synchronous serial TTL interface via SSC Interface.
• 3Pin RS485 interface ( Software SSC via 3 Port Pins).
• 3Pin TTL interface ( Software SSC via 3 Port Pins).
• 3Pin TTL interface ( Hardware Interface via 3 Port Pins).
• CAN serial interface. The CAN interface may be shared with the application.

The utilization of the target communication channel depends on the used interface solution. Within the Universal Debug Engine following devices are supported:

• Universal Access Device 2+
• Universal Access Device 2
• Universal Access Device
• fast-PC67C/PCI
• fast-PC65C/PCMCIA

Debugging via JTAG OCDS L1

JTAG OCDS (On-Chip Debug Support) offers direct access to microcontrollers with an On-Chip Debug Support module (e.g. EGOLD, UTAH, XC161, XC164, XC167 and the TriCore derivatives TC1130, TC1920, TC1796). JTAG OCDS provides a direct serial interface to the controller-internal functional units (registers, busses, control unit etc.). This way, debugging is performed without monitor software or emulators.

OCDS is the base of the latest generation of development environments with new features:

• Event Triggering by the on-chip trigger unit, by software breakpoints or by the Break Input pin
• Additional execution of data transfers
• Complex trigger conditions
• Symbolic conditions for enhanced definitions
• Automatic selection and optimized usage of the on-chip resources
• Task-specific breakpoints
• Access to the entire address space of the controller without any external hard- or software resources
• Hardware breakpoints for debugging in On-Chip FLASH or EPROM
• Optimum support for single-chip applications.

JTAG OCDS is supported by the Universal Access Device and Universal Access Device 2 add-on of the Universal Debug Engine.

Debugging via JTAG

JTAG offers direct access to microcontrollers (e.g. ARM7 and ARM9). JTAG provides a direct serial interface to the controller-internal functional units (registers, busses, control unit etc.). This way, debugging is performed without monitor software or emulators.

JTAG is supported by the Universal Access Device 2+ and Universal Access Device 2 add-on of the Universal Debug Engine.

TriCore Instruction Trace via OCDS L2 Trace Add-On

In depth real-time debugging requires close interaction with the processor. Tracing shall provide a chronological picture of a system's inner workings - before or after a critical event - mainly to help analyzing a faulty program. OCDS L2 was defined for this purpose and is available for the TriCore derivatives. The OCDS L2 unit of the TriCore derivatives supports the recording of a program's execution. In combination with the JTAG OCDS L1 unit it is possible to comfortably watch the program flow in realtime. UDE, the universal debug engine, basically supports the OCDS unit through the Universal Access Device add-on.

OCDS L2 Instruction Trace is supported by the Universal Access Device - Trace Board option of the Universal Debug Engine.

ETM Instruction Trace

TriCore Instruction Trace via MCDS

Debugging via Emulator

With the Integrated Development Environment UDE an extensive emulator support is offered. Using the same GUI as for the monitor-based debugger, UDE offers a developer-friendly and easy-to-use solution.

Even when working on a project in workgroups a mixture of both, UDE monitor debug solutions as well as emulator solutions, is the best way to create a cost-efficient development environment with the priceless advantage of only having to learn and operate one single user interface instead of two or more.

• Additionally to the monitor solution, a trace functionality is available
• Debugging single-chip applications without external RAM
• Complex breakpoints / triggering on events possible
• Simulation memory available
• Real-time execution for extremely time critical applications