In some cases CPU is not able to stream the trace data quickly enough which results in overflow errors. Errors are displayed in the Analyzer Output window and indicated in the Trace window with brown coloured lines.
(e.g. task/irq switches, functions, runnables). For example, configure Code Areas/Data Areas in the Analyzer Configuration dialog / Profiler.
Unchecking the Analyzer Configuration dialog:
Increase Lane link speed in Hardware menu / CPU Options / Aurora.
An idle loop in the code constantly calls a function which returns immediately. Such programming generates excessive amounts of messages and prevents long recordings. For example, instead of:
Limitations inside the CPUs also exist (e.g. on some CPU architectures only 1-bit Aurora is supported). Generated data can fill the internal buffer even before the BlueBox is able to fetch the data from the CPU. It is necessary to find a balance between the accuracy of recorded data and how much information to record.
Refer to topic Trace overflows.
Sorry this article didn't answer your question, we'd love to hear how we can improve it.
Note: This form won't submit a case. We'll just use it to make this article better.