• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 119 subscribers
  • Views 288 views
  • Users 0 members are here
Options
Related

NXP iMX8QM can not trace to DDR by ETR TMC

MoveMOVEMove

Hi ARM:

I am using Arm development studio（Dstream debugger） trace For iMX8QM, using ETR trace to system Mem， but it Cannot work.

But it can debug by Jtag

The config is below:

In Linux Kernel, I have make the 0x880000000 reserved, and cannot visable by linux.



The Chip is broken or any other issue?

Thanks very much.

  • 0

    In Commands it display some warnings:

    Execution stopped in EL1h mode at breakpoint 4: EL1N:0xFFFF800080D20414
    EL1N:0xFFFF800080D20414 RET
    WARNING(DTS51): Failed to complete manual flush (FOnMan stayed high in FFCR)
    WARNING(DTS50): Failed to stop formatter (FtStopped bit stayed low in FFSR)
    WARNING(DTS286): STS.TMCReady stayed low

  • 0

    observer the memory in trace addr, it can change.

  • 0 Arm Employee Badge in reply to MoveMOVEMove

    Hi

    My name is Stephen and I work at Arm.

    WARNING(DTS51): Failed to complete manual flush (FOnMan stayed high in FFCR)
    means that the Debugger has initiated a flush of the ATB bus by writing to the FFCR register on the TMC-ETR, but the flush did not complete in the time available.

    Which version of Arm DS are you using?  Look in Help > About.  It is possible that the Debugger is not waiting long enough.  In the latest version Arm DS 2025.1/.b, the poll duration has been increased, so please try that.

    In your screenshot, it looks like you have 32.1 KB of trace in buffer.   Does the Debugger not decode it?

    Does your target board support Embedded Trace FIFO (ETF)?  If so, try selecting that instead in the Trace Capture dropdown because ETF is the simplest approach.  The Embedded Trace Router (ETR) is a bit more complicated, because you have to ensure some spare memory is available at an address, and it isn't being used by anything else.  I can see that you've accounted for this, but it would be a good idea to try the simpler ETF first.

    If you are still unable to obtain decoded trace, then I suggest you "Open a Support Case" using the link at the bottom of this page, so that our Support Team can investigate further.

    Hope this helps,

    Stephen

  • 0 in reply to Stephen Theobald

    Hi Stephen：

    Thanks for your help, 

    Arm DS version is: 

    Version: 2024.1
    Build: 202410918

    IMX8QM cannot trace to FIFO，

    It has trace in buffer，but cannot decode，when I continue running and stop，the trace buffer is change，but cannot decode. I using another debuger, Dstream ST， still cannot decode the trace buffer. 

    I will try DS 2025.1/b,

    Thanks very much.