This website uses cookies so that we can provide you with the best user experience. To read more about the cookies we use and to change your settings see our Cookies Policy.
To effectively record large Trace Recording Data ( TRD) files via winIDEA Analyzer you must understand potential causes and their solutions. Trace data is captured by an on-chip trace engine, which stores it in an on-chip buffer or streams it through a trace port to the debugger. Trace Rec...
RH850 Software Trace uses a small FIFO that can easily overflow when too many trace messages are generated. This can cause sampling time to decrease or overflow error messages in the Analyzer Trace window (indicated by brown colored lines). Possible solutions Increase the LPD-4 clock Open ...
When trying to run Analyzer from winIDEA, trace fails and an error message displays Disk quota exceeded . Possible solution 1. In the Analyzer window press Options . 2. In theGeneral tab adjust thesettings in Remaining disk quota in GB . 3. Verify how much disk space you actually have on a...
Possible solutions File size is limited Trace file size is software-limitedby the Recording Size Limit setting in theRecorder Configuration dialog. Make sure you set a large enough limit (e.g. can be specified in GB, as well as TB). Enough disk space available Ensure that the drive on whic...
Error message AGBT FIFO overflow indicates that TriCore’s internal FIFO overflowed, which means that in a short time too many trace messages were written into FIFO. The below steps explain in the TC3xx example how to define custom triggers, use an algorithmic approach, halving the range to...
Error message AGBT FIFO overflow indicates that TriCore’s internal FIFO overflowed, which means that in a short time too many trace messages were written into FIFO. The below steps explain on the TC3xx example how to define custom triggers and use an algorithmic approach to find two or mor...
winIDEA stores various temporary files in %TEMP%/iSYSTEM , or if specified, %ISYSTEM_TEMP% directory. Most of the created files are meant to speed up your debugging experience and they remain there even after winIDEA is closed. winIDEA will clean up such files regularly, but depending on w...
This topic visualisessteps on how to define custom triggers and use an algorithmic approach to find two or more problematic functions that generate too many trace messages in a wider range which are described in the topic How to find two or more problematic functions in a wider range if AG...
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 theTrace window with brown colored lines. Possible solutions Limit the scope of the recorded variables (e.g. task/irq...
When the Analyzer stops sampling with the note Trace sampling stopped, reason: Buffer full,a situation hasoccurredin which the trace RAM buffer of the BlueBox is full and no longer able to accept new data. This happens when trace data is being received faster than the BlueBox is capable of...
First check, whether your CPU supports trace - refer to the topic Trace is not licensed . Possiblesolutions Trace Buffer is configured in Hardware | CPU Options | SoC. Default The option Use all available memory for trace buffer should work in most cases assuming that complete TCM memory i...