Hello,
Is there a way to dump the ETM trace (using DTSL) from a VE_AEMv8x1 FVP? I would like to store the RAW trace somewhere so I can process it later.
Thank you,
Andrei
Hi Andrei,
Firstly, I must apologise for the delay in getting back to you on this.
Yes this is easy, to dump the trace out of any trace capture device, be it on the model or hardware, you can use the 'trace dump' command.
It will require a directory to be specified and then it will dump out the raw CoreSight-formatted trace data.
The command might be :
trace dump c:\temp\mytracedump
and then within c:\temp\mytracedump the raw trace data is contained within the FMTrace_0.bin in this case.
I hope that answers your question and I must again apologise for the delay.
Regards,
Stuart
Hi Stuart,
Thanks for the answer! I have one more question: which format is used for storing the FMTrace_0.bin file? It does not start with an ETM/PTM A-sync packet.
I mention that when storing the trace from an actual hardware, everything is fine (I am able to read the PTM format).
Ah, it is stored in the CoreSight formatted trace data format, as specified in the CoreSight Architecture Specification v2.0, sec. D4.2 'Frame descriptions'
(see http://infocenter.arm.com/help/topic/com.arm.doc.ihi0029d/IHI0029D_coresight_architecture_spec_v2_0.pdf p.129)
This is (generally) the raw format that the trace data is stored in a trace capture buffer when using DS-5.
It is formatted like this because there may be trace data from multiple sources contained within.
So what you want is the raw trace data for a given trace data source, so instead do :
trace dump c:\temp\mytracedump FMT_0
as the 'FMT_0' is the trace source of the AEMv8 FVP (look under the 'Source' tab in the Trace view)
If you do :
help trace dump
then you will see the list of options available for dumping trace.
I hope that helps ?
As far as I've seen the two trace files, FMTrace_0.bin and FMT_0_0.bin are almost the same, except 256 0-bytes at the end of FMTrace_0.bin.
Also, in the DS-5 Trace view, the source encoding is specified as "Fast Models Instruction trace". Is there a spec somewhere for this encoding?
Thanks,