Tracealyzer offers unprecedented insight into the runtime world of RTOS-based firmware, allowing for improved development productivity, reduced time-to-market and better software quality.

Source code alone does not give the full picture of how RTOS-based firmware actually behaves. The real-time behavior also depend on many other factors, like the timing of your tasks and interrupts, inputs and RTOS configuration. With Tracealyzer you can record the real-time behavior and get amazing visualizations that give unprecedented insight into the runtime world. This benefits and accelerates your development, validation and debugging of RTOS-based firmware.

“Tracealyzer has doubled our development speed. Problems that otherwise would take days to solve are obvious with this tool and just a quick fix. We use it all the time.”

Alex Pabouctisids, Lead Firmware Engineer, Flyability.

  • Faster Troubleshooting:

    Tracealyzer allows for capturing rare, sporadic errors which otherwise can be very hard to reproduce and analyze. Many embedded software problems can be solved in a fraction of the time otherwise required. Tracealyzer recording can be used in parallel with existing debuggers in the lab, or deployed in field systems to capture rare sporadic errors.

  • Better Software Quality:

    Tracealyzer is not only a “fire extinguisher” to use on specific hard problems. You can also discover and avoid potential future problems, such as blocking system calls that are close to a timeout. Moreover, Tracealyzer gives you a better understanding of the current system run-time dynamics, so when designing new features, you can avoid unsuitable designs that could cause problems related to timing, CPU usage, scheduling or other task interactions.

  • Better Performance:

    The improved insight also allows you to find new ways of improving the embedded software performance. There might be “low hanging fruits”, where small changes in task timing may give substantial performance improvements. Tracealyzer provides several ways of finding “hot-spots” where tasks are delayed by higher prioritized tasks, that possibly could run a bit earlier or later to reduce resource conflicts. Without suitable visualization, such optimizations are very hard to find. This way, you can get a more responsive software system, or fit more software functionality in the same hardware platform.

  • Control system tuning:

    Control system developers can benefit from the support for plotting custom application data, what we call user events. Plots of e.g. control signals (sensor inputs and actuator outputs) can be correlated with the software timing in order to better understand anomalies in the control performance. Moreover, plots of task timing (e.g., periodicity) can be used to study software timing variations that affects control performance.

  • Other benefits:

    The improved level of insight also allows for faster introduction of new developers and better possibilities to evaluate the performance of new third party software, such as embedded databases, touch screen drivers or communication stacks. Finally, since we support several common operating systems for embedded software, you can often keep the Tracealyzer support even if switching to another operating system.

Learn more

Download Tracealyzer for your RTOS and try the visualizations using the included demo. And don’t miss these articles about Tracealyzer and RTOS-based firmware development.