The improved trace recorder library is the biggest change in Tracealyzer v3.1, at least for FreeRTOS, Micrium and SafeRTOS. We have merged snapshot and streaming support into a single recorder module that support both modes, and improved the API and documentation to make it easier to use. If you are using an older version of the [...]
Floating network licenses offer a flexible licensing solution for most development teams. With a floating license, you can install the tool on any number of computers, but the number of concurrent users is limited by the license server. Our floating licenses have a linger time, i.e., a minimum session time during which the license is [...]
If you have a node-locked license for a Percepio Tracealyzer software and wish to move it to another computer, please complete Percepio License Migration Request and send a signed copy to firstname.lastname@example.org.
I’m using/developing an operating system that does not have Tracealyzer support. What is involved in porting Tracealyzer to my operating system?
Our Trace Recorder Library used for FreeRTOS+Trace, SafeRTOS+Trace and Micrium µC/Trace is quite easy to port, as we have made a significant effort to generalize it. All kernel-specific definitions are located in trcKernelPort.c/.h, but you need to insert instrumentation in the kernel and add new fields to the kernel object data types. We welcome new [...]
The first version of Tracealyzer was created in 2004, during Dr. Kraft's PhD work at Mälardalen University. A simple trace visualization was needed to verify schedling simulations, but when ABB Robotics began using the tool systematically in 2005 (on VxWorks), the project started its evolution into something much larger. Between 2005 and 2008, the tool [...]
The name is latin and means "to percieve", i.e., to see, understand or sense.
Percepio is not about sensor technology, we develop software that lets you "sense" what your software in runtime, through powerful visualization of recordings.