Percepio’s TRACELALYZER for SEGGER embOS RTOS
Percepio’s TRACEALYZER for embOS gives an unprecedented level of insight into the run-time world of SEGGER embOS applications. This allows you to solve complex software problems in a fraction of the time otherwise needed, develop more robust designs to prevent future problems and find new ways to improve your software’s performance.
Multi-threaded software often has a complex behavior, where small changes in software timing may lead to unexpected behaviors. Timing-related problems are expensive as they manifest in late stages of testing, or worse, in deployed production code, and can be hard to reproduce. This risk is mitigated if the developers have a good insight into the software’s runtime behavior.
TRACEALYZER for embOS, the Tracealyzer version for SEGGER embOS, visualizes the run-time behavior of your embedded software through 25+ graphical views that complement the code-level debugger perspective with the “big picture”. You may have used a tracing tool before, but the Tracealyzer visualization is on a new level. The views are interconnected in innovative ways and are very simple and intuitive to use, which makes Tracealyzer a very powerful analysis tool.
Tracealyzer provides an unprecedented insight that gives several high-level benefits in your product development. Solve complex software problems in a fraction of the time otherwise needed, develop more robust designs to prevent future problems and find new ways to improve your software’s performance. Tracealyzer facilitates validation, debugging, profiling, documentation and training.
TRACEALYZER for embOS is designed for use with SEGGER J-Link debuggers and allow for continuous trace streaming on any J-Link debugger, for essentially unlimited durations. All you need is a SEGGER J-Link/J-Trace debug probe, an updated version of SEGGER embOS (version 4.06b or later) and our trace recorder library, included in the embOS-Trace installation. Percepio embOS-Trace uses software-defined trace, which makes it robust, flexible and easy to use. The events are written to a RAM buffer (a few KB) for temporary storage. The buffered events are then extracted by the SEGGER J-Link debugger via live memory reads, without interfering with executing system. The transfer is very fast and robust.
Like all Tracealyzer products, TRACEALYZER for embOS offers a 10-day fully functional evaluation period and also includes a pre-recorded demo trace.
The installer download is available here.
- Watch the video about TRACEALYZER for embOS RTOS and get a detailed insight what TRACEALYZER can do for you.
- Visit our focus page embos & TRACEALYZER for application notes, and example projects.
- For licensing options and pricing, please contact email@example.com.
The 25+ views include:
The main trace view shows you all recorded events visualized on a vertical time-line, including task execution timing, interrupts, system calls and custom user events. The task and interrupt trace are shown as colored rectangles. Events are shown as floating text labels. Zooming is very easy using a click-and-drag selection, which also works as a measurement tool. Tasks and events can be clicked and highlighted for additional information, including timing and event dependencies. The lower right corner contains a powerful filter, and the Finder dialog provides even more powerful filters. When zooming out, this view naturally transforms into an overview where patterns can be studied.
This view presents a horizontal time-line showing the total CPU usage, and also CPU usage per task/interrupt. The CPU Load Graph allows for navigating the main trace view, since a double click in the CPU Load Graph focuses the main trace view on the clicked interval. Zooming is allowed in this view as well, independently of other views, and filters are available for focusing on individual tasks or interrupts.
This is an example of several Actor Instance Graphs, each showing the distributions of a specific timing property for an actor, i.e., a task or interrupt routine. This includes execution time, response time, fragmentation, and several others. Each data point represents one specific execution of a task or interrupt handler. This graph, Response Time, shows the variation in response times for two selected tasks. Tasks instances with high response times may reveal resource conflicts, e.g., where several tasks or interrupts compete for CPU time in a busy interval. This view makes it easier to spot such locations that may indicate problems or possibilities for optimization.
All views with horizontal orientation can be combined in a single parent window, with synchronized scrolling. This includes most views except the main trace view, but the task and interrupt trace is available as a horizontal view as well. In this example, the CPU Load Graph is shown together with a plot of task response times. Combining views like this allows for spotting patterns that otherwise would be hard to see using individual views, e.g., how the response time depends on other events, and this also allows for greater customization of the user interface.
Many system calls allow for communication or synchronization between tasks. Tracealyzer for embOS understand these dependencies and the Communication Flow graph is a summary of all such dependencies found in the trace, in the form of a directed graph. This is a high-level view of the communication dependencies between tasks and interrupts, including the kernel objects used such as semaphores and message queues. Like in all views, double-clicking on a node opens a related view focused on the particular object. Double-clicking on a kernel object (e.g., a semaphore) opens the Object History view (shown below), a list of all events on the specific kernel object. If double-clicking on a task or interrupt, the Actor History view is opened showing all executions of the actor.
This view shows all events on a particular kernel object, such as a message queue, semaphore or mutex. The events are presented as a list, and double-clicking on a list item shows the corresponding system call in the main trace view. For message queues and similar objects with send/receive operations, it is possible to follow a specific message from send to receive, or vice versa, and also to inspect the messages (by sequence number) in the queue at any given time.
User-defined events, or User Events, allow you to log any event or data in your embedded application. This gives the flexibility of classic debug “printf” calls, but much faster as all string formatting is done offline. Since you get the events on the same time-line as the kernel trace, it is easy to correlate the application event with the other views. Data arguments can be stored together with labels, and plotted to visualize the data. The plotting is highly useful for analysis of control algorithms, as it allows you to correlate the plotted data with the other time-line views to find the cause of any anomalies in the plot.