11 May 2017
TASKING Embedded Debugger is available.
If you have ever experienced
- the situation of waiting in the queue to get access to a debugger for your embedded projects or
- that you need to use an expensive, high-end solution while you rather wanted to do a simple verification and keep ‘coding momentum’ - we have great news for you!
As of today the new TASKING Embedded Debugger is available. It comes as a separate tool to TASKING compiler toolsets and can be installed, used and maintained independent from the compiler workflow.
TASKING Embedded Debugger integrates into your existing Eclipse GUI, or you use the Eclipse IDE coming with it to download the executable code to the target and control program execution. Plus, common debugging tools and functions are all available such as evaluating expressions, single stepping through both source code and disassembled code, setting and configuring breakpoints (including conditional breakpoints), and the ability to inspect and modify registers and memory. In addition, the automation of the debugger lets you control its functions using the integrated script language. Printf from the development board to the Windows shell works out of the box with TASKING run-time libraries. To further keep costs under control, the debugger uses low-cost debug probes to connect to the physical targets and supports software simulators without probes, if no physical hardware is available.
For the price of a single high-end debugger, organizations can provide developers with several TASKING Embedded debuggers to minimize interruptions and keep coding efficient and effective