890
Chapter 28
On-Chip Debug Unit
Preliminary User’s Manual U17566EE1V2UM00
28.5 Restrictions and Cautions on On-Chip Debug
Function
• Do not mount a device that was used for debugging on a mass-produced
product (this is because the flash memory was rewritten during debugging
and the number of rewrites of the flash memory cannot be guaranteed).
• If a reset signal (reset input from the target system or reset by an internal
reset source) is input during RUN (program execution), the break function
may malfunction.
• Even if reset is masked by using a mask function, the I/O buffer (port pin,
etc.) is reset when a pin reset signal is input.
• With a debugger that can set software breakpoints in the internal flash
memory, the breakpoints temporarily become invalid when pin reset or
internal reset is effected. The breakpoints become valid again if a break
such as a hardware break or forced break is executed. Until then, no
software break occurs.
• The RESET signal input is masked during a break.
• The POC reset operation cannot be emulated.
• The on-chip debugging unit uses the exception vector address 60
H
for
software breakpoint (DBTRAP, refer to
“Interrupt Controller (INTC)” on
page 187
). Thus the debugger takes over control when one of the following
exceptions occur:
– debug trap (DBTRAP)
– illegal op-code detection (ILGOP)
– ROM Correction
The debugger executes its own exception handler. Therefore, the user's
exception handler at address 60
H
will not be executed.
electronic components distributor