TASKING has been providing debuggers for Infineon TriCore™ microcontrollers for over 20 years. Until recently these debuggers were released as a component of the TASKING TriCore VX Toolset only, and were not available as stand-alone tool. Many customers observed that this debugger provided all features to handle the majority of their debug tasks and have asked to make it available as a stand-alone tool for their software developers independent from the compiler toolset. This has led to the release of the TASKING Embedded Debugger which offers streamlined single and multicore debugging for up to six TriCore cores, and debugging of auxiliary controllers such as GTM/MCS, SCR, HSM and PCP. The debugger is an ECLIPSE based stand-alone tool, or can be integrated as a plugin into existing Eclipse Mars environments. All features that streamline the debug process are available such as loading a program to RAM and/or FLASH memory, C/C++ and Assembly level symbolic debugging -- also of highly optimized binaries --, code breakpoints and data watchpoints, concurrent debugging of all cores, run-control with multi-core start/stop synchronization, Autosar-OS aware debugging, full symbolic access to all device control registers (SFRs), and more. Developer productivity is further enhanced by out-of-the box board support, wizard-guided project setup and task execution, extensive online help and user documentation, and responsive customer support. The TASKING Embedded Debugger provides high-speed access to the target device via the JTAG or DAP protocol using a low-cost probe, the Infineon DAP miniwiggler. Features that require expensive hardware probes such as elaborate tracing and complex timing analysis are not supported. If no physical hardware is available the debugger can connect to the instruction-set-simulators that are included in the package.
Communication between the debugger and probe is implemented through the Infineon Device Access Server (DAS) protocol. This assures interoperability between the debugger and other tools that require device access such as calibration tools, and offers remote access to the target device enabling developers to connect from their office desk to a target device in the lab. This way, the device can also be time-shared among multiple developers. Finish your projects faster, spend less, reduce schedule risk, and eliminate developer down time. Most of the debugging time spent by developers is not with complex issues, but rather simple code verification. Rather than purchase a few high-end debuggers that developers have to share, a better solution is fewer expensive debuggers along with several streamlined debuggers that can analyze the majority of issues. Interrupting the developers edit-compile-debug cycle to wait for a debugger license is not only inefficient, but developers usually develop a “momentum” when coding... a string of contiguous thought about how to solve the problem. If this is interrupted, it can take time to regain that train of thought. Enough TASKING Embedded Debuggers can be deployed to keep coding efficient, maintain coding momentum, and stay within budget.