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 3

Look at the trace clock alignment

The RTM_ALIGN_0 and RTM_ALIGN_90 vectors in the RTM log tell us whether the trace clock is aligned with the clock signal edge or whether it is aligned with the edge inverted 90 degrees respectively.  The RTM assumes the trace clock is aligned to the edge by default.

To determine which alignment the RTM should use, count the number of consecutive bits that are set.  The alignment with the most consecutive bits set is the alignment that the RTM should use.  For example, if RTM_ALIGN_0 = 0x00000007 and RTM_ALIGN_90 = 0x019fffff, the trace clock edge alignment should be inverted 90 degrees because RTM_ALIGN_90 has 21 consecutive bits set and RTM_ALIGN_0 only has 3 consecutive bits set.

  1. Check RTM_ALIGN_0 and RTM_ALIGN_90 from the RTM log.
    • If RTM_ALIGN_0 has the most consecutive bits set or the RTM_ALIGN_0 and RTM_ALIGN_90 vectors have the same number of consecutive bits set, go to Manual delay setting.
    • If RTM_ALIGN_90 has the most consecutive bits set, continue following these instructions.
  2. Save a copy of the .sdf, .rcf, or .rvc file before any modifications are made.
  3. Open the platform configuration .sdf, .rcf, .rvc as a text file.
  4. Set RTM_ALIGNMENT_OVERRIDE_ENABLE to 1 (i.e. <RTM_ALIGNMENT_OVERRIDE_ENABLE Type = "Int32">1</RTM_ALIGNMENT_OVERRIDE_ENABLE>).

  5. Set RTM_ALIGNMENT_OVERRIDE_VALUE to 1 (i.e. <RTM_ALIGNMENT_OVERRIDE_VALUE Type = "Int32">1</RTM_ALIGNMENT_OVERRIDE_VALUE>).
  6. Click FileSave.
  7. Start a new dbghw_log_client session using a new log file as output (like <writable path>\log2.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 Manual delay setting.
    • If there is not a RTM lock not achieved message, go to Results.
Previous Next