Troubleshooting DSTREAM-PT Trace

Troubleshooting problems encountered when capturing DSTREAM-PT trace


Introduction Troubleshooting Steps Platform Configuration RTM Log Analysis Check 1 Check 2 Check 3 Manual delay setting Results Example RTM Log

Check 2

Look for a stable trace clock frequency

  1. Look for a Trace frequency stable message in the RTM log.
    • If Trace frequency stable: true, go to Check 3.
    • If Trace frequency stable: false, perform the following steps.
  2. Save a copy of the .sdf, .rcf, or .rvc file before any modifications are made.
  3. Open the platform configuration .sdf, .rcf, or .rvc as a text file.
  4. Set RTM_FREQUENCY_OVERRIDE_ENABLE to 1 (i.e. <RTM_FREQUENCY_OVERRIDE_ENABLE Type = "Int32">1</RTM_FREQUENCY_OVERRIDE_ENABLE>).
  5. Set RTM_FREQUENCY_OVERRIDE_VALUE to either the last RTM_MEAS_FREQ value shown in the RTM log or to the actual target trace port clock frequency.

    Note: If you are setting the RTM_FREQUENCY_OVERRIDE_VALUE to the actual trace port clock frequency, the RTM_FREQUENCY_OVERRIDE_VALUE format is the clock frequency in Hz divided by 100 and converted into hex.  The below formula applies:

    RTM_FREQUENCY_OVERRIDE_VALUE = converted into hexadecimal (trace port clock frequency in Hz / 100)

  6. Click FileSave.
  7. Start a new dbghw_log_client session using a new log file as output (like <writable path>\log1.txt).
  8. If you are editing the .sdf, .rcf, or .rvc outside Arm Development Studio, rebuild the configuration database in Arm Development Studio by clicking WindowPreferencesArm DSConfiguration DatabaseRebuild database.
  9. If you are currently connected to the target with Arm Development Studio, disconnect and then re-connect to the target.
  10. Perform the trace capture again.
  11. Look for a RTM lock not achieved message in the new RTM log.
    • If there is an RTM lock not achieved message, go to Check 3.
    • If there is not a RTM lock not achieved message, go to Results.
Previous Next