2.13.2 Collecting an execution history up to a halt

The debug tool has a pre installed function to collect an execution history of the program from when it starts running to when it stops.

Thanks to this, when the program starts running, collection of trace data begins automatically, and it is finished at the same time the program stops.

For details on how to check the collected trace data, see "2.13.6 Displaying an execution history".

Caution

[Simulator]
With string manipulation instructions and multiply-and-accumulate instructions, only a history of the first and final accesses is collected.

Remark

This function is actuated by an unconditional trace event, one of the built-in events that are set in the debug tool by default.
Note that this unconditional trace event and the trace event described later (see "2.13.3 Collecting an execution history in a section" and “2.13.4 Collecting an execution history only when conditions are met“) are used exclusively of each other. Therefore, if the trace event is Enabled, the unconditional trace event is automatically Disabled.
When no trace event has been set, trace data is collected even if the check box for the unconditional trace event is deselected (i.e. Disabled).