Hi Maryem,
CSAL is a library can be used to program up CoreSight trace components
and subsequently extract the trace data through the register
interface. This library principally manipulates the register sets of
Coresight components. This can be used in bare metal systems or on
Linux by mmaping the hardware memory locations of the components. The
library provides a few worked example programs illustrating the
programming and extraction of trace data.
OpenCSD is a library that will process captured trace data into a
generic output format - this is usually a list of instruction address
ranges representing executed code.
OpenCSD does not have the capability to program trace hardware for
capture, nor convert the processed trace data into assembly language.
This must be done using client programs. The DS-5 dumps you refer to
were created using ARM's DS-5 debugger tool.
The key point here is that both CSAL and OpenCSD are libraries that
are to be used as part of a larger program.
For example in the perf-opencsd-master Linux kernel tree we provide
extensions to perf (which does not use CSAL, but uses the linux
CoreSight drivers directly) that will capture trace data, and
subsequently use the OpenCSD library to process that data. Using the
'perf script' command, and an appropriate python script (also supplied
in the perf-opencsd-master), it is possible to process the trace data
captured by perf, through the OpenCSD library to generate traced
instruction ranges and then passthe traced instruction ranges to
objdump to output a disassembled sequence.
Best Regards
Mike
On 10 August 2017 at 14:49, Maryem Ayadi <maryem.ayady(a)gmail.com> wrote:
> Hi Mark,
>
> I am working with the Opencsd library under linux in order to collect and
> decode the trace.
> I just discovered The CoreSight Access Library (CSAL) and I want to know
> what's the difference between both libraries.
> Besides, is it possible to work only with the opencsd library to collect and
> decode traces on-target?
>
> I am also trying to generate trace data coded in assembly language like the
> contents of the files existing within
> decoder/tests/snapshots/juno_r1_1/ds-5-dumps in the Opencsd library. It
> would be helpful to send me any steps I should follow.
>
> Best regards,
> Maryem Ayadi
--
Mike Leach
Principal Engineer, ARM Ltd.
Blackburn Design Centre. UK
On 25 July 2017 at 21:49, yoma sophian <sophian.yoma(a)gmail.com> wrote:
> hi Mathieu:
>>
>> Get (and recompile) the latest revision of the openCSD library - that
>> should do the trick.
> after using the latest revision of the opcdCSD library, compile is pass.
> But I have some question about trace collection and decode flow
> 1. for trace collection, shall we ask perf to save some other places?
> such as USB or somewhere alse
We welcome patches.
> 2. from HOWTO document, is perf.data the trace data from ETM?
The perf.data file contains the trace data from the ETM devices, the
metadata associated with the ETM configuration and miscellaneous perf
events recorded during the session.
> 3. Why we need .debug directory?
That is where all the binaries that were involved in the trace session
are collected. Those are needed by the decoding library for proper
handling of the trace data.
> thanks ur help in advance.
+ coresight mail list
On 9 August 2017 at 18:54, Maryem Ayadi <maryem.ayady(a)gmail.com> wrote:
> Good morning,
Hi,
>
> I am focusing on OpenCSD library and looking for information about the
> difference between OpenCSD and CSAL library.
> As I noticed, CSAL is for interacting directly with CoreSight trace devices
> on target and programing the tracers while OpenCSD is for collecting the
> trace and decode it.
> Is there any other information you can provide me ?
Have you ever accessed to OpenCSD github [1]? Probably you can get
more information about OpenCSD from there.
I'm not familiar with CSAL though, I can forward an Mike's email in
which he introduced a lot about that library.
I suggest you to cc coresight mail list when you have some question
about CoreSight. There is a lot of knowledgeable people on there.
Regards,
Chunyan
[1] https://github.com/Linaro/OpenCSD/blob/master/HOWTO.md
>
> Best Regards,
> Maryem Ayadi
>
> 2017-08-04 6:42 GMT+01:00 Chunyan Zhang <zhang.chunyan(a)linaro.org>:
>>
>> On 3 August 2017 at 22:47, Maryem Ayadi <maryem.ayady(a)gmail.com> wrote:
>> > Good morning,
>>
>> Hi,
>>
>> >
>> > I am doing an internship at STMicroelectronics and I am new to decoding
>> > traces.
>> > I just red your article entitled "System Trace Module (STM) and its
>> > usage"
>> > and the article "HOWTO-using the library with perf" and started working
>> > on
>> > System Trace Module.
>> > Unfortunately, I can't find stm_source directory. Is it only available
>> > on
>> > certain Kernel versions ?
>>
>> Yes, those patches got merged in v4.10-rc1, and you have to ensure
>> 'STM_SOURCE_FTRACE' is selected when compiling the kernel code.
>>
>> Chunyan
>>
>> >
>> > Best Regards,
>> > Maryem Ayady
>
>
Hello everyone,
Thanks for making this lovely tools, it looks very useful.
I am attempting to use OpenCSD to decode some traces I pulled off of an ARM DSTREAM using it's RDDI interface. However I've run into some trouble, and I have a few questions.
In the ocsd_etmv3_cfg struct, what register is meant by the reg_ctrl? Do they mean the ETM's main control register?
What config settings does TPIU TDATA need to be decoded with? If anyone is familiar with the API, does data from RDDI need any pre-processing before giving to openCSD? Do I need to remove the DSTREAM trace data block footer? A few of the docs reference raw DSTREAm data, so I'm a little hopeful that there's some documentation I've just missed.
- Thanks all!
Hi Mike,
I am trying to decompress trace data produced using the sysfs interface on my Juno r2 board, get back to the assembly code that was executed.
I have read through This Post<https://wiki.linaro.org/WorklingGroups/Kernel/Coresight/traceDecodingWithDS5> on the Linaro wiki, which explains how to do this with DS-5, which I do not have installed on the Juno.
I would like to know if there is a way to use the OpenCSD library, or a part of it, that will allow me to do this.
With your advice in your previous email, I have been able to use the 'trc_pkt_lister' executable, to list trace packets in a human-readable form.
I saw in the documentation for the snapshot format that there is a [dump] section for files describing a core, which might describe an area of memory containing the program executed by the core.
Can this information be used by 'trc_pkt_lister' ? I tried using it on the provided 'juno_r1_1' test snapshot, with '-decode' or with '-decode-only', but these do not appear to be what I am looking for.
Basically, Assuming I have the compiled ELF binary and the associated trace (either in text form using the output of trc_pck_lister, or using the openCSD API), which only gives me virtual addresses executed by the program and indications about taken branches, how do I know where is my program relocated?
This is the part that I am missing, I need to know how the addresses I am seeing in the trace relate to the compiled program.
I would welcome any advice on the subject.
Best regards,
Thierry
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hello,
I'd like to subscribe.
I am trying to get guidance on taking raw TPIU data from a DSTREAM trace session and have OpenCSD as the decoder. Do the TDATA words need to be processed in some way before giving them to OpenCSD? Is there a particular format I need or some processing?
I am also curious as to what the reg_ctrl is for the config struct, is that the master control register for the ETM?
Thanks
- Akira
