The TASKING Embedded Debugger
TASKING Embedded Debugger for TriCore/AURIX
As I mentioned in my first blog, when we think about embedded software development tools, we usually think of the compiler. But, just as important is the debugger. Few if any projects do not have some bugs that must be located and eliminated.
In any major project, you have access to a high-end debugger that can not only verify your code function, but can also perform complex timing analyses that are so critical during software integration and prototyping.
The thing is, the majority of the time you actually spend with a debugger is not running these timing-critical analysis, but simply verifying that your code functions properly and takes the guzintas and produces the correct guzoutas.*
Since that high-end debugger has a high-end price tag to go with it, the number of licenses are generally limited. This can cause a problem with access: when you want to debug the code you’ve been working on, a license may not be available…so you have to wait.
And, if you’re like me, if you have to wait, you lose a little bit of that momentum…that train of great thought that helped you work out a clever solution to the problem you were working on. Sometimes, that’s hard to get back, especially if you have to wait a while.
So what we did is listen to our customers, and provide a streamlined debugger at a streamlined price. That way, your company can have the high-end debugger it needs for timing-critical applications, but can then afford several of our streamlined debuggers. That way, you can almost always access a debugger when you need it! A true win-win arrangement.
These embedded debuggers are available as stand-alone products to augment the debugger that comes with the TASKING VX Toolset for TriCore. Tune in to our webinar and take a look at how your team’s productivity can go up and you can maintain your coding momentum with TASKING Embedded Debuggers.
Start the Embedded Debugger Webinar by clicking here. And, be sure to download an evaluation to try with your own code at https://www.tasking.com/trial .
*If you are not familiar with my terminology, a guzinta (goes into) are the variables that come into your module; a guzouta are the terms that exit your module.