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 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