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.
Comments (4)
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.
Trace.SAVE has to be executed on each instance when you have an APM setup.