In this post, we visualise the custom interval and state machine information available in Tracealyzer and explore how we can use it to better understand our application.
Within Tracealyzer’s trace view, tasks, events and state machines are now organized into view fields, collections of tasks, intervals or events. In this post, we are going to examine how you can use those views to simplify working with Tracealyzer.
We have had a few customers asking us if they can use Tracealyzer to detect when a task holds two mutexes at the same time. The answer is yes, there are in fact several ways you can do this.
Percepio announces the immediate availability of Tracealyzer version 4.4 with support for embedded Linux. The new version adds several views optimized for Linux tracing to Tracealyzer and leverages CTF, the Common Trace Format, and the widely supported LTTng open source tracing framework.
Join Percepio, Crank Software and ST for a one-hour webinar Wednesday 28 October at 11.00 EDT (16.00 CEST) to learn about developing user interfaces on STM32 microcontrollers.
FreeRTOS, an ST microprocessor and Tracealyzer are some of the building blocks for this rocket, built by Swiss students and named after the equally Swiss mathematician Euler.
Today’s post dives into a key component of a Linux device driver, the interrupt handler, and shows how Tracealyzer can give you feedback on the performance of your handler.
While there are mechanisms native to the Linux kernel to ensure that the functionality of a custom-written driver is correct, evaluating performance is not straightforward. Here’s how you can use Tracealyzer for Linux to assess the performance and identify any deficiencies.
FreeRTOS, an ST microprocessor and Tracealyzer are some of the building blocks for this rocket, built by Swiss students and named after the equally Swiss mathematician Euler.
We serve cookies. If you think that's ok, just click "Accept all". You can also choose what kind of cookies you want by clicking "Settings".
Read our cookie policy