
239
CHAPTER 16 INTERRUPT FUNCTION
User’s Manual U15017EJ2V0UD
16.1.1 Software interrupts
Interrupts by software consist of the BRK instruction which generates a vectored interrupt and the BRKCS
instruction which performs context switching.
Software interrupts are acknowledged even in the interrupt disabled state, and are not subject to priority control.
16.1.2 Operand error interrupts
These interrupts are generated if there is an illegal operand in an MOV STBC, #byte instruction or MOV WDM,
#byte instruction, and LOCATION instruction.
Operand error interrupts are acknowledged even in the interrupt disabled state, and are not subject to priority
control.
16.1.3 Non-maskable interrupts
A non-maskable interrupt is generated by the watchdog timer.
Non-maskable interrupts are acknowledged unconditionally
Note
, even in the interrupt disabled state. They are not
subject to interrupt priority control, and are of higher priority than any other interrupt.
Note
Except during execution of the service program for the same non-maskable interrupt, and during execution
of the service program for a higher-priority non-maskable interrupt
16.1.4 Maskable interrupts
A maskable interrupt is one subject to masking control according to the setting of an interrupt mask flag. In addition,
acknowledgment enabling/disabling can be specified for all maskable interrupts by means of the IE flag in the program
status word (PSW).
In addition to normal vectored interrupt, maskable interrupts can be acknowledged by context switching and macro
service (though some interrupts cannot use macro service: refer to
Table 16-2
).
The priority order for maskable interrupt requests when interrupt requests of the same priority are generated
simultaneously is predetermined (default priority) as shown in Table 16-2. Also, multiprocessing control can be
performed with interrupt priorities divided into 4 levels. However, macro service requests are acknowledged without
regard to priority control or the IE flag.