User manual

 iSYSTEM, September 2014 21/23
Example 3 Trace Result
The first one is to use the non-real-time trace mode, which stalls the CPU until the FIFO buffer
becomes ready for new messages and then resumes the execution. This trace mode is turned on by
checking the ‘Stall CPU to avoid overflows’ option in the Trigger pane. Since this is a severe
intrusion in the real-time program execution it is not a recommended solution unless the user is fully
aware of the consequences.
The second and better solution is to limit the amount of the generated data access messages. The
existing trace configuration records all data accesses although the user might be interested only in
data accesses to a specific, limited region or even just to a few variables.