Official response

<p>Hello Jun,</p> <p><br></p> <p>This is expected when using on-chip trace with selective trace.</p> <p>If you open the ETM window, you will notice that the time mode in your case is set to Off or Cycle accurate. To get timing information, you need to set it to Cycle Accurate, which generates timestamps from the chip. note that this also requires full program trace (not just selective trace with traceenabled braekpoint). So you have to trace the full program flow and then with the Trace.find you can filter the trace to display the interrupt calls only.</p> <p>Alternatively, you can use off-chip trace (if you have the Power Trace module) with External time mode, which relies on the tool’s timing. This approach is less accurate than cycle-accurate timing but generates significantly less bandwidth and provides a much larger trace buffer. You can also use cycle-accurate timing with off-chip trace tools if needed.</p> <p>Please refer to the link below for more details about the possible tools configuration for AM6422:</p> <p><a href="https://www.lauterbach.com/supported-platforms/chips/am6422" title="https://www.lauterbach.com/supported-platforms/chips/am6422">https://www.lauterbach.com/supported-platforms/chips/am6422</a></p> <p>Please let me know if you have any questions.</p>