On-Chip Debugging

Unrivalled Flexible Target System Access

• JTAG OCDS L1 and EmbeddedICE are fully supported by UDE offering direct high-speed access to the MCUs internal units.
• OCDS L2 trace and ETM trace supported.
• ETB trace as internal buffer of trace data is supported by UDE.
• Target ROM monitor and bootstrap loader/RAM monitor solutions for a flexible access via a wide variety of debug channels (ASC, SSC, 3-Pin, CAN) are available (not required to access C166CBC, XC16x, XC22x, TriCore and ARM targets).

Debugging via JTAG - Support of OCDS L1, L2, EmbeddedICE, ETM, ETB

• 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
• task-specific breakpoints automatic selection and optimized usage of the on-chip resources
• access to the entire address space of the controller without any external hard- or software resources
• hardware breakpoints for debugging in ROM or on-chip FLASH
• optimized support for single-chip applications.

OCDS L2 and ETM support the recording of the running program's trace of the core, PCP, PCP2 and DMA activity, if available. This allows the watching of the flow of the running program in real-time within the process environment. Timing measurements of critical sections are also possible. ETB is supported. UDE supports JTAG by the Universal Access Device (UAD2) hardware add-on. OCDS L2 and ETM trace are supported by the Universal Access Device - Trace Board option.

Monitor solution for C16x, XC16x, ST10

Package Contents

• The content depends from the supported derivative. In generally the source code for various communication paths between target and host PC is available:
  1. Asynchronous serial interface via ASC0/ASC1
  2. Asynchronous serial interface with ASC bootstrap loader support via ASC0/ASC1
  3. Synchronous serial interface via SSC
  4. 3Pin serial interface (emulated Software SSC)
  5. CAN serial interface. The CAN interface may be shared with the application
• Monitor Main Code in multiple object files for the C16x, XC16x, ST10 controller derivatives
• Source examples for monitor reset code
• Manual
• Software is for free use in customer applications (no royalties), but not for resale as a development tool
• For your convenience, the first monitor adaptation to your target system is FREE of charge.

• Basic UDE-Mon/B: Monitor software including one fully configured adaptation depending on the customer requirements. Support during start-up of the customized monitor via telephone or e-mail. Additional customer specific configurations may be generated by the user. Configuration services by pls available upon request.
• Basic UDE-Mon/AC: Additionally to Basic: One additional customized adaptation.
• Source UDE-Mon/LII: Additionally to Basic: All sources for target routines including source updates via Internet and customized adaptations for one year.

Resources required by the monitor

• 3...4 kByte ROM, 100 Bytes of RAM
• Trap Number 0x7E
• communication channel interrupt
• optional one timer (for execution time measurement)
• when using CAN Monitor: 2 message objects, group of 4 identifiers
• when using 3Pin-Interface Monitor: 3 available port pins

Special Solutions available

• ASC bootstrap loader + ASC / SSC / CAN / 3Pin combines availability of special interfaces with the convenience of ROMless debug target systems
• Service Monitors for all interfaces available for integrating into the product. Especially useful for on-site control and parametering the application.

Monitor solution for TriCore

The portable monitor toolkit is available for the Tasking and the GNU (HighTec) compilers.

Any order must include the Monitor Configuration Form (available from pls or distributors). The specific demands of the customer will be accepted by acknowledgement of the order.

Resources required by the monitor

• 18 kByte ROM, 400 Bytes of RAM
• up to 16 CSA areas
• IOPC Trap (Class 2)
• communication channel interrupt
• optional one timer (for execution time measurement)
• when using CAN Monitor: 2 message objects, group of 4 identifiers

Package Contents

• The content depends from the supported derivative. In generally the source code for various communication paths between target and host PC is available:
  1. Asynchronous serial interface via ASC0/ASC1
  2. CAN serial interface. The CAN interface is shared with the application
• Source examples for monitor reset code
• Manual
• Software is for free use in customer applications (no royalties), but not for resale as a development tool
• For your convenience, the first monitor adaptation to your target system is FREE of charge.