AutoFocus User’s Guide
30
©1989-2018 Lauterbach GmbH
Fifofull
The trace output Fifo has overflowed. The amount of trace data generated by the trace logic was greater
than the trace port band width. To reduce the risk of a Fifo overflow:
•
Increase the port size if possible.
•
Restrict the
DataTrace to read cycles
(write accesses can be reconstructed via
CTS
).
•
Restrict the
DataTrace to write cycles
, a Fifo overflow becomes less likely.
•
Reduce amount of trace data by using filters: use the filter
TraceEnable
or
TraceData
•
STALL the CPU if a Fifo overflow is likely to happen, if supported.
•
Suppress the output of the data flow information if a Fifo overflow is likely to happen, if supported
(
ETM.DataSuppress
).
Trace Test Failure Messages
Trace.TestFocus
supports a built-in trace test. This command loads a short test program to the target
memory (RAM) and traces its execution. Afterwards the recorded program flow and data pattern will be
checked for any errors.
“Analyzer data capture o.k.” will be shown if the test was successful.
Test failures might be caused by a variety of reasons, usually error messages such as:
“Trace test failed: not enough samples in the trace”
will give you a clue as to what might have caused
the failure.
For explanations of the error messages, refer to
”Error Message Emulator”
in
“Error Messages”
(error.pdf).
Trace macrocells are not always able to prevent overflows of the internal Fifo. Even
when STALL is enabled overflows may occur.
