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.
Percepio announces an open beta test program for the upcoming Tracealyzer version 4.4, which provides much improved support for visualization and analysis of embedded Linux® software.
It is quite simple to extend Percepio’s trace recorder library to work with a new processor. Today’s article shows how to do it, using an Intel Nios II soft-core CPU as an example.
Version 4.3.8 of Tracealyzer updates the target-side recorder to work with the most recent version of FreeRTOS, v10.3, and adds two new hardware ports.
The goal was to minimize transmitted radio frequency distortions, under tight real-time deadlines. Using Tracealyzer, RFI Technology Solutions could evaluate various solutions before committing themselves.
We got the question from a customer if we could host the Percepio License Manager server for them. And we thought – why not? That sounds like a good idea.
It could take our customer days to locate and fix a memory leak, but when they deployed Tracealyzer the same bug hunt was completed in a matter of hours.
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