Skip to main content
Contact Us

New to Lauterbach Support? Register for an account

Need a password reminder?

Is it possible to concatenate multiple trace recordings? - Knowledgebase / Tracing - Lauterbach Support

This Article Category Knowledgebase

Is it possible to concatenate multiple trace recordings?

  • Last updated: Aug 7, 2024 by Lauterbach

It is possible to concatenate multiple trace recording when using the Trace method Analyzer, CAnalyzer or Onchip.

First save the trace contents to a file using the Trace.SAVE command:

Trace.SAVE my_joinfile1.ad
...
Trace.SAVE my_joinfile2.ad
...

The first saved trace recording can then be loaded with the command Trace.FILE:

Trace.FILE my_joinfile1.ad

Subsequent trace recordings can then be appended using the command Trace.JOINFILE:

Trace.JOINFILE my_joinfile2.ad
Trace.JOINFILE my_joinfile3.ad
...
Trace.JOINFILE ; execute command without parameter to close loaded trace file

The loaded trace file has to be closed by executing Trace.JOINFILE without parameters.

The option /TIMEGAP can be used to allow a seamless concatenation with regard to the timestamp:

Trace.JOINFILE my_joinfile2.ad /TIMEGAP 0.1us

Refer for more information to the documentation of the Trace.JOINFILE command in General Commands Reference Guide T

Note: streaming files saved with Trace.STREAMFILE and loaded with Trace.STREAMLOAD cannot be concatenated. You first need to save the files with Trace.SAVE and concatenate the resulting *.ad file.

Helpful Unhelpful

4 of 4 people found this page helpful

Comments (4)

Ramanujan Rangan
Is Trace data can only be saved in *.ad format? or is it possible to save it as *.bin?
Khaled Jmal
You can also save the trace in different other formats including binary. Please refer to the description of the .EXPORT command group in https://www.lauterbach.com/pdf/general_ref_t.pdf
Howerton, Jason
is Trace.Save work per each core instance? So if running in AMP mode on TC375TE and I have all 3 main cores open in their own instance, it seems I have to run trace.save from each instance to make 3 files and then trace.load in each instance to view them again. I thought the trace buffer was all one and each instance was just picking out the core.assigned to that instance. Could there be an option for trace.save to save all cores captured instead of just the core assigned to that instance? Yes, I know I could run in SMP, but sometimes , like with HSM on TC3xx, it is Arm and will not run in SMP with the main cores.
Khaled Jmal
Hello Jason, Trace.SAVE has to be executed on each instance when you have an APM setup.

Add a comment

ID-0
To prove you are a human, please tell us the text you see in the CAPTCHA image
This Article Category Knowledgebase
Date Created
Jul 26, 2023