
( 12 / 52 )
IMPORTANT
Notes on Interrupts:
• Even while the user program is not being executed (when the user program is paused or while debug
programs are running), the evaluation MCU is operating for controlling debug programs.
Therefore, take note that timers and other functions are not stopped while the user program is not
being executed.
• When a maskable interrupt is generated in user program execution (when the user program is
paused or while debug programs are running), the interrupt cannot be accepted, because the
emulator disables interrupts. If an interrupt is requested while a user program is not being executed
and the user program allow the interrupt, the interrupt is accepted immediately after the user
program execution is started.
Note on Accessing Address 00000h:
•With the M16C/10 Series MCUs, when a maskable interrupt is generated, the interrupt data
(interrupt No. and interrupt request level) stored in address 00000h is read out. Also, the interrupt
request bit is cleared when address 00000h is read out. Consequently, when the address 00000h
readout instruction is executed or when address 00000h is read out in the cause of a program
runaway, a malfunction occurs in that the interrupt is not executed despite the interrupt request,
because the request bit of the highest priority interrupt factor enabled is cleared.
For this malfunction, when the reading out to the 00000h address is generated excluding the interrupt,
the yellow LED lights up to alarm. When this LED lights, there is a possibility of wrong access,
therefore check the program. This LED is turned off by the RESET switch of the emulator main unit.
Note on Stop and Wait Modes:
•Do not perform step execution at addresses in the stop or wait mode. It may cause communication
errors.
Note on Software Reset:
• Do not use a software reset.
Note on BRK Instruction and BRK Instruction Interruption:
• With this emulator system, BRK instructions and BRK instruction interruptions are exclusively
used for software break functions. Therefore, you can not use them for your program.
Notes on Address-Match Interrupt:
• Do not set software breaks at the same addresses as address-match interrupts as the program may
run out of control.
• Do not set a hardware break within 4 instructions before an address at which an address-match
interrupt occurs. If you do set a hardware break in this range, the program will run out of control.
•When an address at which an address-match interrupt occurs is executed in one-step mode, the
program stops after executing the first instruction after returning from the address-match interrupt
processing.
Comentários a estes Manuais