Look for a stable trace clock frequency
- 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.
- Save a copy of the .sdf, .rcf, or .rvc file before any modifications are made.
- Open the platform configuration .sdf, .rcf, or .rvc as a text file.
- Set RTM_FREQUENCY_OVERRIDE_ENABLE to 1 (i.e. <RTM_FREQUENCY_OVERRIDE_ENABLE Type = "Int32">1</RTM_FREQUENCY_OVERRIDE_ENABLE>).
- 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)
- Click File → Save.
- Start a new dbghw_log_client session using a new log file as output (like <writable path>\log1.txt).
- If you are editing the .sdf, .rcf, or .rvc outside Arm Development Studio, rebuild the configuration database in Arm Development Studio by clicking Window → Preferences → Arm DS → Configuration Database → Rebuild database.
- If you are currently connected to the target with Arm Development Studio, disconnect and then re-connect to the target.
- Perform the trace capture again.
- Look for a RTM lock not achieved message in the new RTM log.