Global Sources
EE Times-Asia
Stay in touch with EE Times Asia
EE Times-Asia > Controls/MCUs

Debug engine handles 32-bit Power Architecture MCUs

Posted: 19 Aug 2010 ?? ?Print Version ?Bookmark and Share

Keywords:universal debug engine? MCUs? automotive? multicore debugging?

PLS Programmierbare Logik & Systeme announces that its Universal Debug Engine (UDE) 2.7 supports Freescale's MPC5668x series of 32b Power Architecture MCUs.

The automotive MCUs that were designed for use as central body electronics controllers and for automotive gateway applications clock at up to 116MHz and feature an e200z650 core as master and an e200z0 core as slave I/O processor, 2MB flash and up to 592KB of SRAM.

The modular architecture of the UDE has full effect when multicore debugging within one user interface. For example, the four code breakpoints and two watchpoints per core, which are supported by on-chip hardware, can be used by the developer direct in the program and watch window of the respective core.

All other on-chip trigger possibilities are also obviously fully supported by the UDE 2.7. In doing so, the debugger independently takes over administration of the on-chip resources.

Connection to dual-core devices is typically carried out via a single JTAG interface. The JTAG extender of the Universal Access Device family (UAD2/UAD3+) from PLS allows a distance of several meters between target and host PC with high immunity to interferences and transfer rates of up to 1 MBps. This not only ensures users of the MPC5668x series an extremely fast flash programming and short turn-around times during development, but also the possibility of using the Universal Debug Engine for maintenance and service.

The existing Nexus unit on all the MPC5668x family enables memory access by the debugger during program run-time. This feature can be used, among other things, for real-time visualization of variables and expressions of them to represent measured values.

This enables a virtual I/O interface that is implemented via the JTAG debug channel. The UAD2+ with trace option or the UAD3+ enable program trace and data trace via the Nexus interface, whereby in both cases the 12-bit wide trace data port of the MPC5668x series is used. With the UAD3+ up to 4 GB of memory are available for recording.

Each sample can contain eight additional external hardware signals. The recording of the samples takes place synchronously to the Nexus clock frequency. This enables an optimal use of the trace memory and application optimized timestamps.

Start and stop of the recording can be controlled via pre-trigger, mid-trigger, post-trigger or address-trigger. The trace window in the user interface offers the developer a direct link from the trace samples to the associated source code, display of the program run-time on the basis of the timestamps as well as search functions.

The UDE 2.7 also supports variable length encoding (VLE), which is implemented in the core architectures Power e200z650 and Power e200z0. This alternative instruction set, consisting of 16-bit and 32-bit wide instructions, enables a high code density.

Both Freescale�s CodeWarrior for MPC56xx devices and the Power Architecture compilers from Greenhills and WindRiver and the GNU implementation from HighTec EDV-Systeme can be used together with the UDE 2.7.

- Colin Holland
EE Times

Article Comments - Debug engine handles 32-bit Power Ar...
*? You can enter [0] more charecters.
*Verify code:


Visit Asia Webinars to learn about the latest in technology and get practical design tips.

Back to Top