Arm Cortex: Parallel trace doesn't work after switching applications

19-Oct-2024

On many Arm devices, the trace clock is directly related to the CPU clock set by your application. Be aware of this dependency when using the same winIDEA workspace to trace different applications, as it is possible that values from a previously performed trace line calibration may not work for your newly downloaded application.


Possible solution

After switching your application, redo the Trace line calibration and apply the recommended values from the calibration. 


See the reference manual of your device to find out more about the relation between the trace clock and the CPU clock. Note that various factors restrict the maximum possible trace clock frequency.


More resources in winIDEA Help

Was this answer helpful?