Embedded Development Tools and Debuggers for XC2000, TriCore, PowerPC, ARM, Cortex, SH-2A » Products » Microcontroller Debugger » UDE Features
| Print |

Universal Debug Engine - High Level Language Debugger and Emulator Tool

UDE Debugger for XC166, XC2000, XE166, TriCore, PowerPC, ARM, Cortex, XScale, SH-2A

UDE  - Universal Debug Engine - is the state-of-the-art development workbench for application development with the C166, C166CBC, C166S V2, ST10, XC166, XC2000, XE166, TriCore®, PowerPC™, PowerArchitecture®, Cortex™-M0, Cortex™-M3, Cortex™-M4, Cortex™-R4, Cortex™-A8ARM7™, ARM9™, ARM11™,  XScale™ and SuperH™ SH-2A microcontrollers family. 

With UDE you can organize your projects, it supports you while building applications and you can run and test your software in a convenient and cost-efficient way.
UDE stands quintessentially for new debugger architecture and tool concept based on a customizable set of standard components and core specific add-ons.

It offers a collection of tools including source file management, project building and powerful HLL debugger with various high-speed communication paths to the customer's hardware target system with target monitor. All components work together in an optimized manner. 

UDE as a part of the package is a powerful HLL debugger and emulator to test microcontroller applications created in C/C++ language and/or Assembly. Together with the Universal Access Device, the communication add-on of UDE and the possible used target monitor it offers realtime execution between breakpoints on the customer's target system.

The profit is on you when using the Integrated Development Environment with integrated tools. There is just one Graphical User Interface for Development, Debugging and Emulation. Multiple high-speed interfaces allow a very flexible target system access.

The Universal Debug Engine is an open platform offering different interfaces to other tools. Optionally, it can be feature-enhanced by the following components that can be included into the workbench:

  • Evaluation Boards from different vendors for a quick start with new XC166, XC2000, XE166, TriCore, PowerArchitecture, PowerPC, Cortex-M0, Cortex-M3, Cortex-M4, Cortex-R4, Cortex-A8, ARM7, ARM9, ARM11, XScale and SuperH SH-2A derivatives.
  • Portable Monitor Development Kit to use the UDE debugger on any application specific hardware.
  • CASE Tool with interface to debugger Universal Debug Engine supporting Enhanced Nassi-Shneidermann-Charts - a great help for reengineering, maintenance and program documentation.
  • Real-Time Operating Systems with detailed support within the debugger Universal Debug Engine to use reliable software components for standard programming tasks.

Operating System Microsoft Windows® XP, Windows® Vista, Windows® 7, Windows® 8 ( 32 Bit (x86) or 64 Bit (x64) versions) supported.

User Definable Enhancements with Scripts and Macros

Being an integrated part of UDE, the open interface for User Definable Enhancements enables you to easily create completely new types of applications:
  • HTML Scripts based on standard UDE ActiveX Control and customer-specific controls together with PERL and JAVA scripts provide fully customized hardware visualization and control.
  • The Automation Interfaces of the UDE components even allow using basic UDE services for controlling the debugger and processing target communication, program flow control and symbol processing by external C/C++, VisualBasic and VBA applications.
  • Substitution of the standard UDE desktop client by a customized desktop to fit the requirements of service tools, Matlab or another third-party tool integration by using the COM interface.

Unrivalled Flexible Target System Access via DAP, JTAG, SWD, Nexus, ETM, ETB

  • DAP, the 2- or 3-wire debug interface for TriCore AUDO Future and other upcoming devices is supported.
  • JTAG OCDS L1 and EmbeddedICE are fully supported by UDE offering direct high-speed access to the MCU's internal units and features like breakpoints, stepping in ROM/FLASH as well as complex trigger conditions without any external hardware or software resources.
  • MCDS trace, OCDS L2 trace, ETM/ITM® trace, ETB trace and Nexus trace support allows the watching of the flow of a running program in realtime within the process environment for core, PCP, PCP2, DMA, if available.
  • Target monitor and bootstrap loader solutions for a flexible access via a wide variety of debug channels (ASC, SSC, 3Pin, CAN) are available.

Target System Communication

UDE features various target communication channels: 

  • ASC0/ASC1 asynchronous RS232
  • ASC0/ASC1 asynchronous TTL
  • ASC0/ASC1 synchronous RS485 (PROFIBUS compatible)
  • SSC synchronous RS485
  • SSC synchronous TTL
  • 3Pin Interface (Software SSC) RS485
  • 3Pin Interface (Software SSC) TTL
  • 3Pin Interface (Hardware) TTL
  • Full Speed CAN
  • JTAG, Device Access Port (DAP)
  • Communications On-chip Processor (COP)
  • Embedded Trace Macrocell (ETM)
  • Embedded Trace Buffer (ETB)
  • JTAG OCDS L1 and L2
  • Serial Wire Debug (SWD)
Please note that the offered communication features depend from your Hardware Communication Device.

FLASH Programming for XC166, XC2000, XE166, TriCore, PowerPC, ARM, Cortex, XScale, SH-2A

FLASH / OTP Memory Programming In-System

Universal Debug Engine integrates High-Speed FLASH / OTP Memory Programming Support - UDE MemTool for internal FLASH/OTP, external FLASH EPROMs (NOR-FLASHs AM29F xxx, i28F xxx family, Serial EEPROMS via I2C and SPI, NAND-FLASHs) and any other JEDEC-compatible FLASH Memories.

Compilers for C166, ST10, ARM, TriCore, PowerArchitecture, PowerPC, XC166, XC2000, XE166, Cortex, SuperH SH-2A

For your convenience, UDE supports all of the available C/C++ Compilers:

C166/ST10 Compiler

  • C166/ST10 C/C++ Compiler (Tasking)
  • CA166 Compiler (Keil)

XC16x Compiler

  • XC16x C/C++ Compiler (Tasking)
  • CA166 Compiler (Keil)

TriCore Compiler

  • TriCore Compiler C/C++ (Tasking)
  • GNU TriCore C/C++ (HighTec)
  • TriCore C/C++ (Green Hills)
  • TriCore C/C++ (Wind River)

PowerArchitecture and PowerPC Compiler

  • Wind River C/C++ (Wind River)
  • GNU PowerPC C/C++ (HighTec)
  • CodeWarrior C/C++ Compiler (Freescale)
  • Green Hills C/C++ Compiler (Green Hills)
  • Byte Craft eTPU C Compiler (Byte Craft)

ARM, Cortex Compiler

  • ARM Compiler /C++ (Tasking)
  • RealView MDK-ARM Compiler (Keil)
  • GNU C/C++ for ARM7/9 (HighTec)
  • ADS ARM® Developer Suite (ARM®)
  • Wind River C/C++ (Wind River)
  • ImageCraft Compiler (ImageCraft)
  • CodeComposer (TexasInstruments)

VaST/Synopsys Simulator Support

The coupling of the PLS UDE and VaST/Synopsys tools reduces test times on the real hardware as the joint solution allows more detailed analysis of timing behavior and performance of an embedded application at a very early phase of system design. This prevents downstream errors that cause redesigns and significantly reduces development cost and schedule.

Interoperability Description and Customer Benefit

The Universal Debug Engine (UDE) can establish a connection to Synopsys virtual prototypes of SoC's created with the CoMET-METeor platform. The support includes multicore designs with TriCore and ARM cores. The solution offers debugging of software at high level language level on the virtual target with configuration and control of the processor models. Thanks of the modular structure of the UDE connection to the Synopsys/VaST tools is established via a special target interface component. If the real hardware is available a simple exchange of this component allows a smooth continuation of work.

UDE Graphical Diagram Display Window

The UDE graphical display window is a powerful visualization tool, which helps to accelerate the evaluation of complex target program data from process environment and by the verification of complex software algorithms. It can be used with all microcontroller families supported by UDE.

The UDE window displays pre-processed target system data as curves of a 2-dimensional scientific diagram. This feature makes it easier to visualize and evaluate target data to accelerate the verification of complex software algorithms and input from process environment.

Basic features of the Graphic Display Window:

  • Multiple curves in one diagram window
  • Separate x- and y-axis for each curve
  • Flexible calculation of curve data points from target program data with UDE expressions
  • Update of data after program hold or with programmable refresh rates during running and stopped target program
  • Legend, Cursor, Zoom, Pan, Axis markers
  • Save and restore of complex settings in UDE workspace and separate file
  • Printer support.
Further helpful features to evaluate data are the zoom-, pan- and cursor functions. This functions help to view details of the current curves. The cursor function makes it easy to access to the particular data values at specific coordinates of the curve.

Triggered Transfer

The UDE TTF Recorder uses the Triggered Transfer feature of new Infineon microcontrollers. Triggered Transfer is part of the on-chip debug support implemented on these controllers. It allows transferring the value of a single memory location via the JTAG debug interface.

The transfer is triggered by a debug event of the onchip debug support (OCDS) unit. There are several types of debug events that can trigger the transfer depending on the actual type of controller. A typical use case provided by all supported controller types is to trigger on write accesses on a single variable and to transfer the new value of the variable.

The recording is done while the target system is in running state.

CAN recorder with plug-in for CANopen visualization

The UDE CAN recorder tool provides the visualization of CAN bus communication and can be used as an add-in or as a stand-alone application. Equipped with the CANopen message formatter plug-in the CAN recorder can visualize the CANopen communication or a user-defined CAN-layer-7-protocol.

The recorder can be configured for filtering and for displaying of symbolic information and can export CAN message streams to a file. A send bar provides the sending and stimulating of the CAN bus. CAN baud rates from 50 kbit/s up to 1Mbit/s and standard / extended CAN identifier are supported.

The UDE CAN recorder supports a Common Object Model (COM). This feature allows the usage of UDE CAN recorder as plug-in of user applications as well as the script-controlled by other applications.

The CANopen message formatter is a plug-in for the UDE CAN recorder and can visualize the CANopen communication. The plug-in scans and interprets DCF-files automatically. This makes data of CANopen networks and CAN nodes available. If no DCF-file is available the message formatter interprets all CANopen standard objects corresponding to the default specification.
In other cases the CANopen message formatter handles an interpretation file for the visualization functionality of the UDE CAN recorder. This file can be edited and manipulated by the user, for example for visualization of a user-defined CAN-layer-7-protocol.

CAN Monitoring with On-chip Debug Support and CAN Bootstrap Loader of XC166, XC2000, XE166 and TriCore

Direct debugging via CAN-Bus is provided by means of the On-Chip Debug System (OCDS) with standardized close connection to the JTAG interface due to support by the latest software package UDE-mon/LII. The using of OCDS enables hardware breakpoints for debugging within the FLASH memory and data breakpoints, which allow for dedicated hold with read or write access to program variables. With the UDEmon/LII target monitor the described functions are now available for all members of the XC16 and TriCore families also via CAN-Bus without limitations. Besides the extended application capabilities the user also benefits from substantially reduced system costs, since there is no more specific adaptation necessary for the user hardware.

The target monitor requires approximately 16 kByte FLASH memory and 1 kByte RAM for the TriCore derivatives and approximately 4 kByte FLASH memory and 100 Byte RAM for members of the XC16x family. Also a message object and a CAN identifier need to be provided.

A shared utilization of one CAN module by the application and the target monitor is as easily implemented as the access to a separate CAN module of TwinCAN or MultiCAN units of the respective microcontroller. The monitor software includes the C and assembler text for the various common compiler packages and can be integrated into existing applications in a simple way.
The usage of the CAN bootstrap loading mechanism is supported by UDE and UDE MemTool.

Realtime Data Monitoring and Collection

With UDE it is possible simple program variables, contents of complex terms and physical terms from multiples of these system variables to record in realtime and evaluate within the UDE. It is, therefore, possible to analyze the real-time behaviour of the developed software and to recognize and repair problems with the distribution of the processor performance as well as synchronization problems between multiple parallel running program routines. In order to minimize the influence of the system behaviour, only debug interfaces are used, which allow a transparent read-out of the system information in the background of the active program.

The visualization takes place by means of a two-dimensional graphical representation of multiple signals over a common time axis in a curve diagram. All necessary signal data can be extracted as a result of scanning: values from individual variables, elements from complex data structures or even via any complex combination from multiple single data. The option to compute complex physical values in real-time from program variables helps the user thereby, as far as possible, to simplify the interpretation and evaluation of the displayed diagrams.

The data is pre-processed in the Universal Access Device 2 (UAD2) or Universal Access Device 2+ (UAD2+);INSERT INTO `jos_content` VALUES , which is connected directly to the target system. The UAD2 and UAD2+ were also designed by pls Programmierbare Logik & Systeme and thanks to an inherent 32 Bit controller offer an extremely powerful communication equipment, which allows that even with complex expressions a minimum sampling period in the range of 1 millisecond (1 ms) is assured. Following this, the computed data is buffered in the Universal Access Device. 32 MByte of main memory ensures that data with up to 30 minutes storage time are not lost until read-out by the UDE. Furthermore, the data can be stored in parallel in XML-Format, whereby a subsequent evaluation of the data via script or another program (e.g. Excel) is possible. An optimal display of the recorded data is offered by multiple selectable modes of the viewing window. Moreover, the graphical representation enables the use of additional functions - such as zoom, data cursor and switch able function markers - for the examination of details.

Profiling Support via IPSnooping, MCDS, OCDS L2 trace, ARM SOC trace

The knowledge of CPU load distribution of the running target application is a basic requirement to optimize their real-time behaviour. UDE supports the profiling of code trace data from different sources:

  • "IP - Snooping" trace - UAD2+ polls instruction pointer of TriCore or XC16x CPU periodically with minimum poll period of 1 millisecond
  • OCDS L2 trace / ETM code trace
  • MCDS code trace
  • ARM SoC-Designer PCP2 simulator trace

The instruction pointer trace data will be collected due their occurrence in the functions of the application. If the value cannot be assigned to any known function, it will be assigned to the known code section of the program (depends from availability of debug information).

The evaluation counts the trace hits of the appropriate ranges and calculates the execution time of the range due to execution time of the trace samples. The results are available as chart diagram and as numeric result table. Additional the UDE profiling page enables, that the results can be saved in a free selectable XML base data sink for later processing.
This data sink can be processed in a normal MS Excel 2003 environment or can be processed by Windows Script languages and MS XML parser function (which are installed by UDE). All functions to access to the generated profiling data are also available via UDE object model to allow creating internal and external script for automatic post-processing.

Automated Testing with Tessy

The test system Tessy from Razorcat offers automated module testing of C code directly on the target system using Universal Debug Engine (UDE) debugging technology. It supports the whole unit testing cycle and works transparently on all target platforms currently supported by UDE.

  • Systematic test case design using the classification tree method: Intuitive, easy to learn graphical representation of test specifications.
  • Quick overview of test objects interface and variable usage within interface browser tools.
  • Easy creation of module environment: Definition of unresolved references and all necessary stubs.
  • Automatic test driver generation, test execution and evaluation of test results.
  • Test driver in client/server technology allows unlimited number of test cases and minimum code/data requirements on the target system.
  • Powerful support for regression testing: An interface browser tool shows both old and changed interfaces and provides comfortable interface assignment that allows automatic reusage of test data.
  • For C166/ ST10 and TriCore target systems Tessy is available with Universal Debug Engine (UDE).

VaST/Synopsys Simulator Support

The coupling of the PLS UDE and VaST/Synopsys tools reduces test times on the real hardware as the joint solution allows more detailed analysis of timing behavior and performance of an embedded application at a very early phase of system design. This prevents downstream errors that cause redesigns and significantly reduces development cost and schedule.

Interoperability Description and Customer Benefit

CoMET-METeorThe Universal Debug Engine (UDE) can establish a connection to Synopsys virtual prototypes of SoC's created with the CoMET-METeor platform. The support includes multicore designs with TriCore and ARM cores. The solution offers debugging of software at high level language level on the virtual target with configuration and control of the processor models. Thanks of the modular structure of the UDE connection to the Synopsys/VaST tools is established via a special target interface component. If the real hardware is available a simple exchange of this component allows a smooth continuation of work.

pls Development Tools is System-Level Catalyst Member.

RTOS - Real Time Operation System Supoort

rcX for netX

The rcX real-time operating system , which is specifically tailored to the architecture of the Hilscher's netX controllers, is a pre-emptive, multitasking operating system with a very low resources requirement.

CMX Real Time Operating System Support

The CMX-RTX® Real-Time Operating System (RTOS) is a fully preemptive operating system with a powerful set of system functions, very moderate memory requirements and fast system response time.

MicroC/OS-II Real Time Operating System Support

µC/OS-II, the Real-Time Kernel is a portable, ROMable, scalable, preemptive real-time, multitasking kernel for microprocessors and microcontrollers. µC/OS-II can manage up to 63 application tasks.

Nucleus Real Time Operating System Support

UDE features the visualization of the Nucleus RTOS objects in a clearly arranged and comfortable manner. UDE uses the debug communication channel for getting of RTOS object data. All other controller peripheral channels are user available.

PXMON Support

PXROS stands for Portable eXtendable Realtime Operating System. PXROS is a sophisticated Real-Time Operating System and allows you to design modern, object-oriented applications with independent tasks and associated handlers for high priority actions. UDE supports the PXMON Task Level Debugger.

OSEK® ORTI Support

UDE features ORTI, the OSEK® run-time interface of the OSEK operating system regarding the visualisation of OSEK object information as OS state, performance, task states etc.

OSE 166 Illuminator Support

The new Illuminator communication mode using the JTAG OCDS L1 interface of C166CBC microcontrollers supports System Level Debugging within the Illuminator's Run Mode. All other communication interfaces of the target system may be used by the OSE application without any restrictions. Universal Debug Engine provides fast application downloading and easy FLASH/OTP programming.

As a sophisticated HLL Debugger, Universal Debug Engine offers all standard features to debug applications at kernel level. The JTAG OCDS bus provides a significant higher communication speed compared to the standard serial interface. Additionally, no further hardware resources are required for the debug channel.

Graphical Real Time Monitoring Tool with StethoScope

StethoScope is the real-time graphical monitoring tool for Universal Debug Engine (UDE). StethoScope gives you a window into the very heart of your application, presenting a live analysis of your program while preserving real-time performance. You can immediately see the effects of code changes, parameter changes, or external events. It allows you to look at any variable or memory location in your system. You can watch any set of variables, see peak values and glitches you would otherwise miss, trigger collection on specific events, and save all your data to disk. With Universal Debug Engine and StethoScope together, you can make your system work.
StethoScope is developed by Real-Time Innovations, Inc. (RTI). RTI is a leading developer of new tools for the growing real-time software market.

OCDS L2 Instruction Trace

Hard real-time debugging requires close interaction with the processor. Tracing shall provide a chronological picture of a system's inner workings up to, starting from or in the vicinity an event, mainly to guide a human in understanding a faulty program. OCDS L2 was defined for this purpose and is available on the TriCore derivatives. The OCDS L2 unit of the TriCore derivatives supports the recording of a running program's trace. In combination with the JTAG OCDS L1 unit a comfortable watching of the program flow in real-time is possible. UDE, the Universal Debug Engine, supports basically the OCDS unit by the Universal Access Device add-on. OCDS L2 Instruction Trace is supported by the Universal Access Device - Trace Board option.

MCDS Instruction Trace for TriCore

Multicore Debug Solution (MCDS) support is an Add-in available for UDE and is used to capture processor states in real-time using JTAG connection to the derivative. This can only be done with the MCDS onchip trace features of special versions of TriCore TC1796ED, TC1797ED and XC2000ED derivatives.

ETM and ETB Instruction Trace for ARM

The Embedded Trace Macrocell (ETM and ETB) of ARM derivatives is supported by UDE and is used to capture processor states in real-time using a dedicated connection to the derivative. The ETM v1.2 is supported via 4/8 bit port width, Halfrate Clock Mode is supported too.

Nexus Instruction Trace for PowerPC

UDE supports program trace via the Nexus interface. This function is currently available for the Power Architecture® derivatives MPC55xx and MPC56xx from Freescale as well as SPC56xx from STMicroelectronics.

A 2 Bit, 4 Bit or, with the MCUs of the MPC55xx family, even 12 Bit wide trace data port with up to 180 MHz clock frequency are supported, whereby up to 1 megasamples can be recorded. With a compression of the trace data direct by the trace hardware, this represents a multiple of machine commands.

Update and Upgrade, Technical Support

When you purchase an UDE Development Environment, you get a FREE Update Service for the UDE Debugger and the UDE-Mon Portable Monitor Development Kit for 12 months. The Update Service includes approximately two new software releases of the products including documentation, regular product news and updates or upgrades of other development environment components ( software, compiler, editor, evaluation hardware...) at a favorable price. For questions or problems we offer you our Technical Support Hotline. We specialize in supporting your whole development environment including interaction between the tools.

Supported Microcontrollers in detail

Our debugging software escorts you either way. Please find the following overview about the different debug and emulator solutions and their support. Typical variants for remote debug connection using the debugger Universal Debug Engine regarding the available communication interfaces on the C166, ST10, XC166, XC2000, XE166, TriCore, PowerPC, ARM7, ARM9, ARM11, Cortex, XScale and SH-2A MCU hardware.
  • Actel SmartFusion® Cortex-M3 A2F060M3E, A2F200M3F, A2F500M3G
  • AMCC PowerPC PPC440SPe, PPC440EP, PPC440GP, PPC440GR, PPC440SP, PPC460GT
  • Analog Devices ARM7 ADuC7019, ADuC7020, ADuC7021, ADuC7022, ADuC7024, ADuC7025, ADuC7026, ADuC7027
  • Atmel Cortex-M3 AT91SAM3S1x, AT91SAM3S2x, AT91SAM3S4x, AT91SAM3U1x, AT91SAM3U2x, AT91SAM3U4x
  • Atmel ARM7 AT91M40, ARM7 AT91SAM7A1, AT91SAM7A2, AT91SAM7A3 AT91SAM7S32, AT91SAM7S64, AT91SAM7S128, AT91SAM7S256 AT91FR40162
  • Atmel ARM9 AT91RM9200
  • Atmel ARM9 AT91SAM9260, AT91SAM9261, AT91SAM9263, AT91SAM9R64, AT91SAM9RL64, AT91SAM9XE128, AT91SAM9XE256, AT91SAM9XE512
  • Cirrus Logic ARM7 EP7309, EP7311, EP7312
  • Cirrus Logic ARM9 EP9301, EP9302, EP9307, EP0312, EP9315
  • EnergyMicro Cortex-M3 EFM32G2x0F16, EFM32G2x0F32, EFM32G2x0F64, EFM32G2x0F128, EFM32G8x0F32, EFM32G8x0F64, EFM32G8x0F128, EFM32TG110F4, EFM32TG110F8, EFM32TG110F16, EFM32TG110F32, EFM32TG200F8, EFM32TG200F16, EFM32TG200F32, EFM32TG230F8, EFM32TG230F16, EFM32TG230F32, EFM32TG840F8, EFM32TG840F16, EFM32TG840F32
  • Freescale® Power Architecture MPC5514E, MPC5514G, MPC5515S, MPC5516S, MPC5516E, MPC5516G, MPC5517S, MPC5517E, MPC5517G, MPC5533, MPC5534, MPC5553, MPC5554, MPC5561, MPC5565, MPC5566, MPC5567
  • Freescale® Power Architecture MPC5601D, MPC5602D, MPC5603B, MPC5603C, MPC5604B, MPC5604C, MPC5605B, MPC5606B, MPC5607B
  • Freescale® Power Architecture MPC5601P, MPC5602P, MPC5602PE, MPC5603P, MPC5602PE, MPC5604P, MPC5604PE
  • Freescale® Power Architecture MPC5602S, MPC5604S, MPC5606S
  • Freescale® Power Architecture MPC5632M, MPC5633M, MPC5634M
  • Freescale® Power Architecture MPC5643L, MPC5643L_DP (LockStep/DP-Mode)
  • Freescale® Power Architecture MPC5645S
  • Freescale® Power Architecture MPC5642A, MPC5643A, MPC5644A
  • Freescale® Power Architecture MPC5644B, MPC5645B, MPC5646B
  • Freescale® Power Architecture MPC5644C, MPC5645C, MPC5646C
  • Freescale® Power Architecture MPC5668E, MPC5668G
  • Freescale® Power Architecture MPC5673F, MPC5674F
  • Freescale® Power Architecture MPC5673K, MPC5673K_DP, MPC5674K, MPC5674K_DP, MPC5675K, MPC5675K_DP (LockStep/DP-Mode)
  • Freescale® Power Architecture MPC5676R
  • Freescale® Power Architecture MPC5744P, MPC5744K, MPC5746M, MPC5777M (MCA)
  • Freescale® ARM11 i.MX31, i.MX35, i.MX37
  • Freescale® ARM9 MC9328MX1 i.MX1, MC9328MX21S i.MX21S,  MC94MX21 i.MX21, i.MX25, i.MX27
  • Freescale® ARM7 PAC72x1, PAC72x2, MAC71x1, MAC71x2, MAC71x4, MAC71x5, MAC71x6, MAC7241, MAC7242
  • Freescale® Cortex-M4 Kinetis MK10N32, MK10N64, MK10N128, MK10N512, MK10N1M0, MK10X32, MK10X64, MK10X128, MK10X256, MK10X512
  • Freescale® Cortex-M4 Kinetis MK20N32, MK20N64, MK20N128, MK20N512, MK20N1M0, MK20X32, MK20X64, MK20X128, MK20X256, MK20X512
  • Freescale® Cortex-M4 Kinetis MK30N512, MK30X64, MK30X128, MK30X256
  • Freescale® Cortex-M4 Kinetis MK40N512, MK40X64, MK40X128, MK40X256
  • Freescale® Cortex-M4 Kinetis MK50N512, MK50X128, MK50X256, MK51N256, MK51N512, MK51X128, MK51X256, MK52N512, MK53N512, MK53X256
  • Freescale® Cortex-M4 Kinetis MK60N256, MK60N512, MK60N1M0, MK60X256, MK60X512, MK61N1M0, MK61X512
  • Freescale® Cortex-A8  i.MX51 IMX508, IMX512, IMX513, IMX514, IMX515, IMX516
  • Hilscher ARM9 NetX10, NetX50, NetX100, NetX500
  • Infineon C166 80C166, 83C166, 88C166
  • Infineon C166 C161, C163, C164, C165UTAH, C165H, C167
  • Infineon C166 Vecon, EGOLD
  • Infineon XC166 XC161, XC164, XC167
  • Infineon XC2000 XC2264, XC2267, XC2268, XC2269, XC2285, XC2286, XC2287, XC2288, XC2289 (XC2200 Body)
  • Infineon XC2000 XC2200H, XC2200I, XC2200L, XC2200M, XC2200N, XC2200U
  • Infineon XC2000 XC2310, XC2320, XC2365, XC2387 (XC2300 Safety)
  • Infineon XC2000 XC2300A, XC2300B, XC2300C, XC2300D, XC2300E, XC2300S
  • Infineon XC2000 XC2766, XC2786 (XC2700 Powertrain)
  • Infineon XC2000 XC2700S
  • Infineon XE166 XE162, XE164, XE167 (Industrial)
  • Infineon XE166 XE166xU, XE166xL, XE166xN, XE166xM, XE166xH
  • Infineon Cortex-M0 XMC1000, XM1100, XMC1201, XCM1202, XMC1203, XMC1301, XMC1302
  • Infineon Cortex-M4 XMC4000, XMC4100, XMC4200, XMC4400, XMC4500
  • Infineon TriCore TC11IB, TC1100, TC1115, TC1130, TC1161, TC1162, TC1163, TC1164, TC1165, TC1166, TC1167, TC1197
  • Infineon TriCore TC1724, TC1728
  • Infineon TriCore TC1736
  • Infineon TriCore TC1762, TC1765, TC1766, TC1766ED, TC1767, TC1767ED
  • Infineon TriCore TC1775
  • Infineon TriCore TC1782, TC1784
  • Infineon TriCore TC1791, TC1793, TC1796, TC1796ED, TC1797, TC1797ED, TC1798, TC1798ED
  • Infineon TriCore TC1910, TC1912, TC1920
  • Infineon TriCore TC22x, TC23x, TC23xED, TC24x, TC24xED
  • Infineon TriCore TC26x, TC26xED, TC275T, TC27x, TC27xED, TC29x, TC29xED AURIX (MCA)
  • Infineon TriCore AUDO-NextGeneration, AUDO-NG, AUDO-Future, AUDO-MAX (AUtomotive unifieD processOr)
  • Infineon TriCore AURIX (AUtomotive Realtime Integrated neXt generation architecture) (MCA)
  • LuminaryMicro Cortex-M3 LM3S1xx, LM3S3xx, LM3S6xx, LM3S8xx, LM3S11xx, LM3S13xx, LM3S14xx, LM3S15xx, LM3S16xx, LM3S17xx, LM3S18xx, LM3S19xx, LM3S1Jxx, LM3S1Nxx, LM3S1Pxx, LM3S1Rxx, LM3S1Wxx, LM3S1Zxx
  • LuminaryMicro Cortex-M3 LM3S21xx, LM3S22xx, LM3S24xx, LM3S25xx, LM3S26xx, LM3S27xx, LM3S29xx, LM3S2Bxx
  • LuminaryMicro Cortex-M3 LM3S36xx, LM3S37xx, LM3S38xx, LM3S3Jxx, LM3S3Nxx, LM3S3Wxx, LM3S3Zxx
  • LuminaryMicro Cortex-M3 LM3S56xx, LM3S57xx, LM3S59xx, LM3S5Bxx, LM3S5Kxx, LM3S5Pxx, LM3S5Rxx, LM3S5Txx, LM3S5Yxx
  • LuminaryMicro Cortex-M3 LM3S61xx, LM3S64xx, LM3S65xx, LM3S66xx, LM3S67xx, LM3S69xx,
  • LuminaryMicro Cortex-M3 LM3S85xx, LM3S86xx, LM3S87xx, LM3S89xx
  • LuminaryMicro Cortex-M3 LM3S97xx, LM3S99xx, LM3S9Bxx, LM3S9Lxx
  • Marvell/Intel XScale PXA255, PXA270
  • Marvell/Intel XScale IXP420, IXP421, IXP422, IXP423, IXP425, IXP455, IXP460, IXP465
  • Micronas C166 SDA6000, SDA6001
  • NetSilicon ARM7 NET+15, NET+20, NET+40, NET+50
  • NetSilicon ARM7 NS7520
  • NetSilicon ARM9 NS9360, NS9750, NS9775
  • NXP ARM9 LH7A400N0, LH7A404N0
  • NXP Cortex-M0 EM773
  • NXP Cortex-M0 LPC1102, LPC1111, LPC1112, LPC11C12, LPC1113, LPC1114, LPC11C14
  • NXP Cortex-M0 LPC1224, LPC1225, LPC1227
  • NXP Cortex-M3 LPC1311, LPC1313, LPC1342, LPC1343, LPC1345, LPC1346, LPC1347
  • NXP Cortex-M3 LPC1751, LPC1752, LPC1754, LPC1756, LPC1758, LPC1759, LPC1763, LPC1764, LPC1765, LPC1766, LPC1767, LPC1768, LPC1769, LPC1772, LPC1774, LPC1776, LPC1777, LPC1778, LPC1785, LPC1786, LPC1787, LPC1788
  • NXP Cortex-M3 LPC1812, LPC1813, LPC1815, LPC1817, LPC1822, LPC1823, LPC1825, LPC1827, LPC1833, LPC1837, LPC1853, LPC1857, LPC1800DUAL
  • NXP Cortex-M4 LPC4072, LPC4074, LPC4076, LPC4078, LPC4088
  • NXP Cortex-M4 LPC4310, LPC4320, LPC4330, LPC4350, LPC4312, LPC4313, LPC4315, LPC4317, LPC4322, LPC4323, LPC4325, LPC4327, LPC4333, LPC4337, LPC4353, LPC4357, LPC4300DUAL
  • NXP ARM7 LPC2114, LPC2119, LPC2124, LPC2129, LPC2131, LPC2132, LPC2134, LPC2136, LPC2138, LPC2142, LPC2144, LPC2146, LPC2148, LPC2194
  • NXP ARM7 LPC2212, LPC2214, LPC2220, LPC2292, LPC2294
  • NXP ARM7 LPC2364, LPC2366, LPC2368, LPC2378, LPC2387
  • NXP ARM7 LPC2468, LPC2470, LPC2478, LPC2880, LPC2888
  • NXP ARM9 LPC2915, LPC2917, LPC2919
  • NXP ARM9 LPC2921, LPC2923, LPC2924, LPC2927, LPC2929
  • NXP ARM9 LPC2930, LPC2939
  • NXP ARM9 LPC3180
  • NXP ARM9 LPC3220, LPC3230, LPC3240, LPC3250
  • Renesas SuperH SH-2A SH7201, SH7211, SH7251, SH7254, SH7266, SH7267
  • Siemens/Renesas ARM9 Ertec200, Ertec200p, Ertec400
  • STMicroelectronics® C166 ST10R163, ST10F163, ST10R165, ST10R167, ST10F167, ST10F168, ST10F169, ST10R172
  • STMicroelectronics® C166 ST10F251, ST10F252, ST10F269, ST10R271, ST10R272, ST10R273, ST10F275, ST10F276, ST10F280, ST10F282, ST10F296
  • STMicroelectronics® ARM7 ST30F771, ST30F772, ST30F774
  • STMicroelectronics® ARM7 STR710, STR711, STR712, STR720, STR730, STR731, STR750
  • STMicroelectronics® ARM9 STR910, STR911, STR912
  • STMicroelectronics® Power Architecture SPC560B40, SPC560B44, SPC560B50, SPC560B54, SPC560B60, SPC560B64, SPC560C40, SPC560C44, SPC560C50, SPC560D30, SPC560D40
  • STMicroelectronics® Power Architecture SPC560P34, SPC560P40, SPC560P42, SPC560P44, SPC560P50, SPC560P54, SPC560P60,
  • STMicroelectronics® Power Architecture SPC56AP54, SPC56AP60
  • STMicroelectronics® Power Architecture SPC560S50, SPC560S54, SPC560S60
  • STMicroelectronics® Power Architecture SPC563M60, SPC563M64
  • STMicroelectronics® Power Architecture SPC564A70, SPC564A74, SPC564A80
  • STMicroelectronics® Power Architecture SPC564B64, SPC564B70, SPC564B74
  • STMicroelectronics® Power Architecture SPC56EC64, SPC56EC70, SPC56EC74
  • STMicroelectronics® Power Architecture SPC56EL60, SPC56EL60_DP (LockStep/DP-Mode)
  • STMicroelectronics® Power Architecture SPC56HK70, SPC56HK70_DP (LockStep/DP-Mode)
  • STMicroelectronics® Power Architecture SPC574P, SPC574K (MCA)
  • STMicroelectronics® Cortex-M3 STM32F10xx4, STM32F10xx6, STM32F10xx8, STM32F10xxB, STM32F10xxC, STM32F10xxD, STM32F10xxE, STM32F10xxF, STM32F10xxG, STM32F100x4, STM32F100x6, STM32F100x8, STM32F100xB
  • STMicroelectronics® Cortex-M3 STM32F102x4, STM32F102x6, STM32F102x8, STM32F102xB
  • STMicroelectronics® Cortex-M3 STM32F105x8, STM32F105xB, STM32F105xC
  • STMicroelectronics® Cortex-M3 STM32F107x8, STM32F107xB, STM32F107xC
  • STMicroelectronics® Cortex-M3 STM32F205xB, STM32F205xC, STM32F205xE, STM32F205xF, STM32F205xG
  • STMicroelectronics® Cortex-M3 STM32F207xC, STM32F207xE, STM32F207xF, STM32F207xG
  • STMicroelectronics® Cortex-M3 STM32F215xE, STM32F215xF, STM32F215xG
  • STMicroelectronics® Cortex-M3 STM32F217xE, STM32F217xG
  • STMicroelectronics® Cortex-M3 STM32L151x8, STM32L151xB, STM32L152x8, STM32L152xB, STM32W108xB
  • STMicroelectronics® Cortex-M3 STM32TS60
  • STMicroelectronics® Cortex-M4 STM32F302xB, STM32F302xC, STM32F303xB, STM32F303xC, STM32F313xB, STM32F313xC
  • STMicroelectronics® Cortex-M4 STM32F373x8, STM32F373xB, STM32F373xC, STM32F383x8, STM32F383xB, STM32F383xC
  • STMicroelectronics® Cortex-M4 STM32F401xB, STM32F401xC, STM32F405xE, STM32F405xG, STM32F407xE, STM32F407xG, STM32F415xG, STM32F417xE, STM32F417xG
  • STMicroelectronics® Cortex-M4 STM32F427xG, STM32F427xI, STM32F429xG, STM32F429xI, STM32F437xG, STM32F437xI, STM32F439xG, STM32F439xI
  • TexasInstruments ARM9 OMAP5912
  • TexasInstruments ARM7/Cortex-M3 TMS470R1A64, TMS470R1A128, TMS470R1A256, TMS470R1A288, TMS470R1A384, TMS470R1B512, TMS470R1B768
  • TexasInstruments Cortex-R4 TMS570LS10116, TMS570LS10206, TMS570LS10216, TMS570LS20206, TMS570LS20216
  • TexasInstruments Cortex-A8 OMAP3503, OMAP3515, OMAP3525, OMAP3530
  • TexasInstruments ARM9/Cortex-A8 AM3505, AM3517, AM3703, AM3715, DM3725, DM3730, AM3892, AM3894
  • ARM11 ARM1136J, ARM11MP
  • Xilinx XC5VFX Virtex® 5 Integrated Power Architecture based Core (PPC440) XC5VFX30T, XC5VFX70T, XC5VFX100T, XC5VFX130T, XC5VFX200

System Requirements / Compatibility

  • Microsoft Windows® compatibel Personal Computer
  • 1 GHz or faster 32 Bit (x86) or 64 Bit (x64) processor
  • 1 GByte RAM (32 Bit) or 2 GByte RAM (64 Bit)
  • 1 GByte available hard disk space
  • Operating System Microsoft Windows® XP, Windows® Vista, Windows® 7, Windows® 8 ( 32 Bit (x86) or 64 Bit (x64) versions supported)
  • .NET Framework 3.5 SP1
  • Windows Scripting Host V5.6 required for scripting support
  • Microsoft Internet Explorer® 6.0 or higher
  • Adobe® Acrobat Reader 4.0 or higher
  • 300 MByte space on local hard-disk
  • CDROM drive for installation
  • Administrator permissions for the current login during installation.

Trademarks : Altium, TASKING and their respective logos are trademarks or registered trademarks of Altium Limited. ARM, EmbeddedICE and Thumb are registered trademarks of ARM Limited. ARM7, ARM9 and Embedded Trace Macrocell, are trademarks of ARM Limited. AUDO, AURIX are trademarks of Infineon Technologies. Freescale is a trademark of Freescale Semiconductor, Inc. Green Hills Software and the Green Hills Software logo are registered trademarks of Green Hills Software, Inc. Keil Software and the Keil Software Logo are registered trademarks of Keil Software, Inc. Nuvoton and NuMicro are a trademark of Nuvoton Technolgy Corporation. PowerPC is a trademark of IBM Corporation. Smart Fusion is a trademark of Actel Corporation. ST is a registered trademark of companies belonging to the STMicroelectronics Group. STMicroelectronics is a registered trademark of STMicroelectronics, Inc. SuperH is a trademark of Renesas Technlogy Corporation. TriCore is a trademark of Infineon Technologies. Virtex is a trademark of Xilinx, Inc. XScale is a registered trademark of companies belonging to the STMicroelectronics Group. Windows XP, Windows Vista, Windows 7 are trademarks of Microsoft Corporation. All other brands or product names are the property of their respective holders.


ESE Kongress 2014
Debugging at UML model level, UDE for Cortex-M devices inclusive DAVE 3 integration, Complete Eclipse based development platform for TriCore/AURIX applications and for Qorivva / SPC56 family

Read more ...

Crash Courses and Training
Multicore Debug Solution, MCDS, Architectures, UDE

Read more ...


UDE supports the
latest Qorivva
mulicore SoCs from


UDE and TESSY test
platform from Razorcat
enable automated
software tests directly
on the target system


PikeTecs TPT test
software and UDE
now permit model-
based tests directly
on the target platform


Universal Debug
Engine 4.2
real multicore
debugging even with
deeply embedded


Universal Emulation
up the full potential
of emulation devices
MPC57xx from


Universal Debug
supports Eclipse 4.x
platforms by an
own perspective

Hercules™ security
MCU platform
TMS570LS and RM4x
from Texas
Instruments now
supported by UDE
Optimized debugging
solution for
the new
ARM® Cortex™- M0
core-based XMC1000
family of Infineon

New Universal
Access Devcie 2pro

(UAD2pro) enables
also strong electrically
isolated connections
to the target


First optimized
test and debug
solution for the
new AURIX™
32-bit multi-
core MCUs
from Infineon


Proven debug
solution for new
multicore auto-
motive micro-
MPC57xx (Freescale)
and SPC57x (STM)


Optimized debug
tools for the
new XMC4000
of Infineon
available now


Complete debug
solution for the
Device of the
new TriCore

netX controllers
and rcX RTOS
from Hilscher
now supported by UDE
Dual-core debugging
of NXP's LPC4300
under the single user
interface of UDE

Kinetis MCUs
from Freescale
based on Cortex-
M4 core supported
by UDE


Complete new
toolchain for
Power Architecture
and Freescale
based on Eclipse,
GNU and
Universal Debug Engine

UAD3+ sets new standards in the field of high end trace and multicore / multi-target debugging