Enables real-time trace mode. In this mode, some trace packets may be lost, but the core executes at the same speed as it would if trace was disabled. When you disable this option, no trace packets are lost, but the core may stall occasionally.

Enables timestamps. When timestamps are enabled, the trace collection device records a timestamp with each packet. Timestamps are displayed in the Trace List and are used by the MULTI Profile window, PathAnalyzer, and EventAnalyzer.

Enables the trigger GUI. For simple events, such as executing a function, the GUI is sufficient. However, the IECUBE also supports sophisticated event configuration that is not available via the trigger GUI. If you need access to more advanced features, you can clear this box and control all events by using debug server commands such as bra, brs, and trace.

Enables branch program counter (PC) trace packets. This option is sufficient for fully reconstructing the instruction sequence the target executed. It is also sufficient for use with TimeMachine. For information, see the documentation about TimeMachine.

Enables instruction program counter (PC) trace packets, which results in the target outputting a trace packet for each instruction. This can yield more accurate timing information when timestamps are enabled. It also increases the probability that the trace buffer overflows in real-time trace mode.

Causes the target to output a program counter (PC) trace packet for every instruction that performs a memory access. This option is usually unnecessary.

Enables data/address trace packets for memory accesses.

Enables real-time trace mode. In this mode, some trace packets may be lost, but the core executes at the same speed as it would if trace was disabled. When you disable this option, no trace packets are lost, but the core may stall occasionally.

Enables timestamps. When timestamps are enabled, the trace collection device records a timestamp with each packet. Timestamps are displayed in the Trace List and are used by the MULTI Profile window, PathAnalyzer, and EventAnalyzer.

Enables the trigger GUI. For simple events, such as executing a function, the GUI is sufficient. However, the IECUBE2 also supports sophisticated event configuration that is not available via the trigger GUI. If you need access to more advanced features, you can clear this box and control all events by using debug server commands such as bra, brs, and trace.

Enables data read trace packets for memory accesses.

Enables data write trace packets for memory accesses.

Enables branch program counter (PC) trace packets. This option is sufficient for fully reconstructing the instruction sequence the target executed. It is also sufficient for use with TimeMachine. For information about TimeMachine, see the documentation about TimeMachine.

DMA read trace packets.

Enables DMA write trace packets.

Specifies the time resolution of trace packet timestamps. This field defaults to 5000 picoseconds when timestamps are enabled.

Specifies the behavior when the trace buffer fills. You can choose to overwrite old trace data with new data, stop trace collection, or halt the process. If you stop trace collection or halt the process, note that this option can only preserve trace data acquired since the last time the target was halted, rather than all of the data acquired since the last time data was retrieved. When the Long Term Trace extension (QB-V850E2-SP trace memory extension) is used with IECUBE2, Stop Execution is not supported.

Specifies the behavior when a Delay Trace trigger is hit. It can be configured to stop trace collection or stop execution.

This option is only available if a Delay Trace trigger has been set up.

Specifies the desired position of the Delay Trace trigger in the trace buffer, after trace has stopped. Last means trace will stop very soon after hitting the trigger (so the trigger will end up being near to the last thing in the trace buffer). First means trace will continue to be collected until the trigger is near the beginning of the buffer. Middle means trace continues to be collected until half of the buffer has been filled.

This option is only available if a Delay Trace trigger has been set up.

Enables real-time trace mode. In this mode, some trace packets may be lost, but the core executes at the same speed as it would if trace was disabled. When you disable this option, no trace packets are lost, but the core may stall occasionally.

Enables timestamps. When timestamps are enabled, the trace collection device records a timestamp with each packet. Timestamps are displayed in the Trace List and are used by the MULTI Profile window, PathAnalyzer, and EventAnalyzer.

Enables the trigger GUI. For simple events, such as executing a function, the GUI is sufficient. However, the IECUBE2 also supports sophisticated event configuration that is not available via the trigger GUI. If you need access to more advanced features, you can clear this box and control all events by using debug server commands such as bra, brs, and trace.

Enables data read trace packets for memory accesses.

Enables data write trace packets for memory accesses.

Enables branch program counter (PC) trace packets. This option is sufficient for fully reconstructing the instruction sequence the target executed. It is also sufficient for use with TimeMachine. For information about TimeMachine, see the documentation about TimeMachine.

Causes the target to output a trace packet for each software trace instruction (DBCP, DBTAG, DBPUSH).

Causes the target to output a program counter (PC) trace packet for every instruction that performs a memory access. This option is usually unnecessary.

Enables DMA read trace packets.

Enables DMA write trace packets.

Specifies the time resolution of trace packet timestamps. This field defaults to 5000 picoseconds when timestamps are enabled.

Specifies the behavior when the trace buffer fills. You can choose to overwrite old trace data with new data, stop trace collection, or halt the process. If you stop trace collection or halt the process, note that this option can only preserve trace data acquired since the last time the target was halted, rather than all of the data acquired since the last time data was retrieved.

Specifies the desired position of the Delay Trace trigger in the trace buffer, after trace has stopped. Last means trace will stop very soon after hitting the trigger (so the trigger will end up being near to the last thing in the trace buffer). First means trace will continue to be collected until the trigger is near the beginning of the buffer. Middle means trace continues to be collected until half of the buffer has been filled.

This option is only available if a Delay Trace trigger has been set up.