Version 4.2 of he Universal Debug Engine (UDE) from PLS Programmierbare Logik & Systeme features greatly enhanced control and test methods for multicore targets, optimized visualization options during system level testing, as well as dedicated support for a wide range of the very latest 32-bit multicore SoCs.
The trace framework of the Universal Debug Engine 4.2 has also been equipped with numerous new features. For example, relocation of the data processing in a separate process not only increases the speed of the evaluation, but also allows persistent storage of trace sessions for analysis at a later time without direct access to the target. Furthermore, comprehensive filters and the possibility to individually color recorded events of various trace sources simplify a clear presentation of the results.
An enhancement of the proven Universal Emulation Configurator (UEC) of the Universal Debug Engine (UDE) ensures an even more efficient use of the Emulation Devices offered by Infineon, Freescale and STMicroelectronics for some SoCs. Programming of the additional trigger logic contained on the Emulation Devices is performed by a graphical configuration of trace tasks, by which signals and actions are linked via a state machine.
With PLS’ Universal Access Device 3+ (UAD3+), a hardware tool with 4 GB external trace memory is available for recording trace data. An Aurora trace pod supports four serial high-speed lanes each with 3.25 gigabit per second (Gbit/s) transfer rate and a parallel trace pod for recording signals up to 500 MHz.
A fast and safe evaluation of immense volumes of trace data is supported by a new module that complies with ISO 26262 requirements, which for the first time also enables coverage analysis of optimized code. At the same time, the DWARF format that is typically used for debugging information has been extended so that control flow changes triggered by the compiler are recognizable for the debugger. In addition to bar graphs for a quick overview, the report generated contains a detailed list of statement and branch coverage per function, source text lines and individual machine instructions. Likewise, code not executed, only partially covered areas of code or jumps not executed can be located very quickly. The report can be used as proof of the software quality assurance in the context of the documents required by the ISO 262626 standard.