Percepio Tracealyzer

We use percepio as our main platform to troubleshoot and diagnose our embedded applications in real time, both as a method to find bugs and to evaluate the performance of our code regarding use of resources and timing.

This is a perfect tool to debug complex bugs in your system, especially in regards to inter-task communication. It is also a great tool for beginners, as the documentation is accessible and the support given by the company is excellent

The Intervalzero’s RTX64 product contains the percepio Tracealyzer tool as part of its SDK. The IntervalZero monitoring session logs can be loaded by Tracealyzer to help our customers get a detailed graphical view of their real-time application’s behavior. Tracealyzer allows our customers to find memory leaks, deadlocks, and even performance issues. The design of the UI allows for complex applications that run across multiple cores to be easily viewed by our customers to determine what is happening in their applications.

Tracealyzer allows our customers to find memory leaks, deadlocks, and even performance issues within applications.

I have been using Percepio Tracealyzer since I first discovered in on the FreeRTOS site. It has been my go to too for 3 companies, especially with useful for debugging nasty crashes and performance issues. It is one of the first tools I purchase and have successfully used it both with FreeRTOS and Linux. I greatly appreciate the ability to view the internal workings of complex multithreaded systems with massive debug overhead. As an early adopter I provided initial ports for the microchip DSPIC/24 and Xilinx PPC families and this required very little coding even back in the early days. Since then all the families I’ve used have been supported. Given the viewer itself is written using the .net framework it is a little cleaner directly on Windows but generally runs fine on Linux. Far and away one of my favorite tools for embedded systems.

It’s been useful to the organizations I’ve worked at for all manner of embedded systems debug.

We use Tracealyzer built within uCOSIII to visualize and debug issues.

It's very helpful when it works, but may take some tweaking to get it to that point.

Tracealyzer allowed me to quickly identify embedded OS and code use issues using standard interfaces and hardware tools that far surpass writing custom debug routines, parsers, corresponding software tools in a fraction of the time. I can't really imagine writing code for an embedded OS target without having visualization tools like Tracealyzer at the ready.

Tracealyzer is great for a embedded target with enough memory that uses an OS. If you're trying to run a OS on a very limited resource constrained system, use can be a bit difficult.