User`s manual

25
3.4 Support of the Target MCU
3.4.1 Memory Space
The architecture of the MCU allows for a 16-Mbyte memory space.
(1) On-Chip I/O Area
If an attempt is made to access the on-chip I/O area, the on-chip I/O area in the MCU installed in the
emulator is accessed. To break user program execution when the on-chip I/O area is written to or accessed,
use the hardware break or internal break.
(2) On-Chip ROM/RAM Area
If an attempt is made to access the on-chip ROM/RAM area, the on-chip ROM/RAM area in the MCU
installed in the emulator is accessed. To break user program execution when the on-chip ROM/RAM area is
written to or accessed, use the hardware break or internal break.
3.4.2 Power-Down Modes (Sleep and Software Standby)
For reduced power consumption, the MCU has sleep and software standby modes.
(1) Sleep and Software Standby Modes
• Break
The MCU can be taken out of the sleep and software standby modes either in the normal ways or
through satisfaction of a break condition (forced break). When restarting after a break, the user program
will restart at the instruction following the SLEEP instruction.
• Trace
Trace information is not acquired in these modes.
• Memory access with emulator functions
For information on displaying and modifying the contents of memory in the sleep and software standby
modes, refer to section 5.4, Displaying and Modifying the Contents of Memory, in the Debugger Part.
3.4.3 Interrupts
During execution and step execution, the user can interrupt the MCU.
Interrupt sources are retained while emulation is halted (break mode). In such cases, interrupt processing
commences immediately after emulation is restarted.