iMX 8MNano trace support

[jemecj]

I’m an engineer working on trace support in our debug tool for the i.MX8M Nano. I’ve encountered an issue with the parallel trace, the ETB works fine, but I can’t capture any data using parallel trace. The pins are correctly configured (confirmed with a logic analyzer), but trace messages aren’t being propagated from the trace sources to the output pins.

Is there any known issue with any of the CoreSight components on this device, or anything specific I should be aware of?

Also, could someone please provide the debug schematic showing the trace connection path (from the ETM through all components to the TPIU)?

[Rita_Wang]

I think you already get the email for special spport for it, so close it now. Thanks.

[jemecj]

What about the replicator and ETB? I would assume that after the funnel, the trace goes through the replicator, which then splits it between the TPIU and ETB.

Could you also provide details on which funnel channel each ETM is connected to?

[jemecj]

Anything new? I am still looking for an answer.

[Rita_Wang]

I found some useful links, hope can do help for you

MITO8M-AN-001: Advanced multicore debugging, tracing, and energy profiling with Lauterbach TRACE32 -...

Setup of the Debugger for a CoreSight System

LCA14-210- ETM-ETB-Coresight BoF.pdf

[jemecj]

Hi,

thanks for reply, but this is to generic. I am quite familiar with ETM, ETB and other Coresight components.  Here, I am asking you about the iMX8MNano specifics, that are not described in general files you provided.

To properly connect trace path from sources to drains I have to know exactly how trace messages are propagated.  With that I mean for example which funnel's channel has connection to specific component. 

Best regards,
Jaka

[Rita_Wang]

I am not good at it, but do not worry I will confirm in my side for you, then give you reply. Thanks for your kinddly understandings.

[Rita_Wang]

The actual trace path is internal to the SoC and not exposed in public schematics.

• Verify ETM and TPIU are enabled in the device tree and kernel.
• Check trace funnel routing in the CoreSight topology.
• Ensure trace clock is active and matches your analyzer’s expectations.

I found this maybe do help for you:

www2.lauterbach.com/pdf/training_arm_etm.pdf