One of the important aspects is the unique modular construction of the UDE, which allows real multi-core debugging within one user interface. This is particularly useful with the dual-core versions of MPC5516 and MPC5514. For example, the four code breakpoints and two watch points per core, which are supported via on-chip hardware, can be used by the developer direct in the program and watch window of the corresponding core. Needless to say, all further on-chip trigger options of the MP5516 are also fully supported by the Universal Debug Engine 2.4 (UDE 2.4). In the process, the debugger allocates the necessary on-chip debug resources automatically.
The connection to dual-core devices, such as the MPC5516, typically takes place via a single JTAG interface. In combination with pls Universal Access Device 2+ (UAD2+), download rates of up to 1 Mbyte/s can be achieved with the UDE 2.4. This guarantees users of the MPC5510 family a fast FLASH programming and also a short turnaround time during development.
The existing Nexus unit on all devices of the MPC5510 family enables memory access by the debugger during run-time. For example, this feature can be used for real-time visualization of variables and expressions of them to represent measured values. Furthermore, in this way, a virtual input/output interface is implemented via the JTAG debug channel.
The core architectures Power e200z1 and Power e200z0 support VLE, which stands for variable length encoding. This alternative instruction set consists of 16-bit and 32-bit wide instructions and enables a high code density. The Universal Debug Engine provides transparent use of VLE.
An additional advantage is the support of the most important compilers. Freescale s CodeWarrior for MPC55xx devices as well as Wind River's PowerPC Compiler and the GNU implementation can be used together with pls UDE 2.4.