User’s Manual
（
Preliminary
）
IECUBE2 main (QB-V850E2)
ZUD-CD-10-0092 11/19
1.3.4
Trace function (program execution history)
The trace function can be used to check the CPU execution history (trace). Items (1) to (7) can be recorded in
the execution history.
(1) Program counter (PC) of branch source and branch destination
The PCs of a branch source and a branch destination can be recorded in the history.
Consequently, practically all executed programs can be checked, because programs executed between
branch points also will be clarified. The amount of trace memory used can be saved and more history
items can be traced by that amount, by recording only branch information. (The amount of traces that can
be traced back depends on the number of branches.)
(2) Access data/access address
Access addresses for memories and peripheral I/O registers, and access data can be recorded in the history.
Read and write operations can also be recorded in the history.
Caution Accesses to CPU program registers (such as r1 and r2) and system registers (such as PSW
and EIPC) cannot be recorded in the history.
(3) Time stamp
The time elapsed from the trace start point can be added to each trace information. The timer performance
for time stamps is the same as that of the time measurement function.
(4) DMA access address, data, status, channel number, transfer count
When the DMA function of the target microcontroller is being used, the DMA access can be recorded in the
history.
- Access address
- Access data
- Access status (R/W)
- DMA channel number
- Transfer count
(5) History of specific sections (section trace)
Only specific sections can be recorded in the history by using the event function in combination. For
example, the execution history of from the start to the end of a function can be recorded.
(6) History of specific phenomenon occurred (qualify trace)
Only the occurrence of specific phenomena can be recorded in the history by using the event function in
combination.
For example, a history of having accessed to only a variable can be recorded.
(7) Recording histories before and after specific phenomenon has occurred (delay trigger trace)
The history after a specific phenomenon has occurred can be recorded by using the event function in
combination. This is similar to being able to observe a signal waveform by assuming an edge as a trigger,
when using an oscilloscope to observe a signal.
For example, the program execution histories before and after a write access has been performed for a
variable can be viewed.
