Hi Ajith,

OpenCSD is a trace decode library that is designed to be integrated
into a tool to decode trace. It is not a trace decode tool itself.

You have two choices:-

1) Write a program to use the library and decode the trace. The
'trc_pkt_lister' test program and source
[decoder/tests/source/trc_pkt_lister.cpp] is a good example of how to
use the library.
Use the decode tree object / api to build a decoder for your configured system.

2) Limited decode can be obtained if your data is presented as a trace
snapshot to the 'trc_pkt_lister' program - this will then do some
decoding of your trace.
The format specification is defined in decoder/docs/specs/"ARM Trace
and Debug Sanpshot file format 0v2.pdf"
Example snapshots are seen in decoder/tests/snapshots.
The decode from this program is limited to outputting either raw trace
packets, or executed instruction ranges. Additional work will be
required to provide disassembly / source code attribution of the
decoded trace.

Either way you will need the following:-
a) Trace data in a binary file.
b) configuration information for the ETM hardware at the time of trace capture.
c) Any memory images of programs executed while capturing the trace data.

I advise building the documentation for the library using the doxygen
file in decoder/docs for additional information.

Regards

Mike


On 15 February 2018 at 00:51, Ajith Kurian Issac

<ajith-kurian.issac@broadcom.com> wrote:
> Hi,
>
>  We are trying to us the Open CSD for decoding a onchip trace in our ETB.
> The trace was enabled and is captured in the ETB.
> We read the trace back and dumped it into a text file.
> I am attaching it.
>
> How can I use the CSD tool to decode it?
>
> Thanks
> Ajith
>

> _______________________________________________
> CoreSight mailing list
> CoreSight@lists.linaro.org
> https://lists.linaro.org/mailman/listinfo/coresight
>



--
Mike Leach
Principal Engineer, ARM Ltd.
Blackburn Design Centre. UK