This is the documentation page for Percepio Trace Exporter, Percepio’s Atmel Studio Extension for Tracealyzer. You can download the extension here; please see our Atmel page for the full story on how to work with Tracealyzer and Atmel Studio.

When installed, the extension adds a “Percepio” top-level menu to Atmel Studio.

Exporter Diagnostics

This is a view that shows some of the current Exporter settings; it can be used to help checking if something is wrong.

The diagnostics show both current options and runtime information.

Options Dialog

From the Options menu alternative, you can set up the Tracealyzer path, where to save traces, and which RTOS you are using.

The extension will normally detect your Tracealyzer installation, but in rare cases the executable file must be located manually. For Tracealyzer version 4.2 and newer, there is built-in support for creating snapshot traces directly from Tracealyzer, using the Snapshot Tool. See Tracealyzer User Manual for more information about this.

Older versions of Tracealyzer are also supported, select the correct Version if Tracealyzer 3.x is used.

The Trace Directory specifies where traces should be saved when created by the extension. Default is to have nothing set for Trace Filename, which will generate a new trace each time with a timestamp in the name, but it is also possible to set a filename (either full path, or just the name). When a filename is set, the same file will be overwritten each time a snapshot is taken.

Same File Handling specifies what to do when a trace file is overwritten. If Tracealyzer is running and has the trace file open, it will detect that the file has changed and ask if the trace should be reloaded. The extension does then not have to do anything, and the default option is therefore Do nothing. The other possible choices are Ask every time, and Always launch new Tracealyzer.

If you are using an RTOS with an integrated Percepio Trace Recorder, like e.g. FreeRTOS, the expressions to find the trace buffer address and size are already known. For others, like ThreadX, there is a default name that can however be changed by the user, so in those cases you may need to modify Buffer Address and Buffer Size.

It is always possible to select Other as RTOS Type. This allows any expression (including hard coded decimal or hexadecimal values) to be used to locate the buffer.