Have you ever seen your embedded system behave strangely and had that sinking feeling that you might have a memory leak? Tracealyzer offers several different methods to detect memory leaks.
What if you want to visualize some application data in Tracealyzer, measure the time between two events or monitor a state machine? In this post, we will show how you can set up this kind of custom logging.
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.
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.
This week we released version 4.3.7 of Tracealyzer, which includes an update to the recorder to be compatible with with the latest release, v3.07.00, of µC/OS-III, as well as various bug fixes.
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