Qorivva MPC5xxx/SPC5xx Debugger and NEXUS Trace
58
©1989-2021 Lauterbach GmbH
Correlation of the Trace Timestamp with Other Tool Timestamps
If the
tool generated timestamp
is used, then this timestamp is automatically correlated to all other
hardware and software timestamps of TRACE32 tools. The trace recording can be immediately correlated to
recordings of PowerProbe, Integrator and to the Logic Analyzer Probe integrated into the PowerTrace
modules and to software features like the
. It is even possible to correlate trace recordings made
by multiple PowerTrace modules that are synchronized via the PodBus interface.
If
processor generated timestamps
are used, this absolute correlation of all debug tool timestamps is not
possible. If a common event is known, then the recordings can be correlated manually (see
As the clock sources of tool generated and processor generated timestamps are not synchronized, the time
offset can increase with higher distance of the measurement from the common event.
Implications of Using the Processor Generated Timestamps
As already mentioned above, processor generated timestamps increase the amount of generated trace data
by 25~35%, which will reduce the absolute run-time that fits into the (on/off-chip) trace buffer and can also
cause overflows of the on-chip message FIFOs.
Processor generated timestamps can be used to make run-time measurements in a filtered trace recording
even if an Aurora NEXUS trace port is used.
As this processor series does not generate timestamp overflow messages, trace events must be frequent
enough so that not more than one timestamp overflow can occur between two events. Assuming a 300MHz
core frequency, the 30-bit timestamp will overflow every 3.58 seconds.
