2370205_en-US

[#1]

Arm CoreSight RT1176CVM8A no Trace Clock

I have a custom board using the RT1176CVM8A and wish to get the arm trace working.  Using the script from here https://kb.segger.com/i.MXRT1176 I'm able to get the arm trace working on the EVK for the zephyr sample basic\blinky.

My problem is when trying to transition to my board I'm unable to get the ARM_TRACE_CLK out of the board.  I have confirmed using GPIO that the board has the GPIO_DISP_B2_06 (ARM_TRACE_CLK -- ALT3) connected to the correct PIN.  Using the clock observe feature I have confirmed that I can configure the CSTRACE_CLK_ROOT to 100 MHz the same as on the EVK.

Is there anything different between the two processor when it comes to enabling the Arm Trace?  Where can I find a detailed description of the Arm Trace register to see if they are being enabled correctly?

Re: Arm CoreSight RT1176CVM8A no Trace Clock

Hi @spencermacdonald,

The issue is most definitely not on the trace clock signal or muxing, but I would just like to make sure you have adequate the following restriction that exists on the EVK to your custom board:

As mentioned on the MIMXRT1170EVKHUG as well as AppNote AN14071, JTAG_nTRST is driven low by default and this can block the trace feature. On these documents we recommend setting this pad as a GPIO to work around this block and allow for the trace feature to function properly on the EVK. I understand that the issue is present on your custom board rather than the EVK, but my suggestion is to check whether your custom board also sets up TAG_nTRST driven low that could cause this issue.

BR,
Edwin.