Datasheet

Section 4 Exception Handling
R01UH0166EJ0600 Rev. 6.00 Page 111 of 1434
Mar 02, 2011
H8S/2633 Group, H8S/2633 F-ZTAT
TM
,
H8S/2633R F-ZTAT
TM
, H8S/2695
Section 4 Exception Handling
4.1 Overview
4.1.1 Exception Handling Types and Priority
As table 4.1 indicates, exception handling may be caused by a reset, trace, direct transition, trap
instruction, or interrupt. Exception handling is prioritized as shown in table 4.1. If two or more
exceptions occur simultaneously, they are accepted and processed in order of priority. Trap
instruction exceptions are accepted at all times, in the program execution state.
Exception handling sources, the stack structure, and the operation of the CPU vary depending on
the interrupt control mode set by the INTM0 and INTM1 bits of SYSCR.
Table 4.1 Exception Types and Priority
Priority Exception Type Start of Exception Handling
High Reset Starts immediately after a low-to-high transition at the RES
pin or MRES pin, or when the watchdog overflows. The
CPU enters the power-on reset state when the RES pin is
low, and the manual reset state when the MRES pin is low
Trace
*
1
Starts when execution of the current instruction or exception
handling ends, if the trace (T) bit is set to 1
Direct transition Starts when a direct transition occurs due to execution of a
SLEEP instruction
Interrupt Starts when execution of the current instruction or exception
handling ends, if an interrupt request has been issued
*
2
Low Trap instruction (TRAPA)
*
3
Started by execution of a trap instruction (TRAPA)
Notes: 1. Traces are enabled only in interrupt control mode 2. Trace exception handling is not
executed after execution of an RTE instruction.
2. Interrupt detection is not performed on completion of ANDC, ORC, XORC, or LDC
instruction execution, or on completion of reset exception handling.
3. Trap instruction exception handling requests are accepted at all times in program
execution state.