2.23.15
Reset microcontroller (CPU)
- | [EZ Emulator]
In the event of an internal reset, the emulator cannot control the CPU. Do not allow any modules (e.g. watchdog timer) to cause an internal reset. |
- | [EZ Emulator]
Return from the deep software standby mode involves an internal reset. Thus, the emulator cannot control the CPU in this state. |
- | [EZ Emulator]
If the reset signal is input through the reset pin while the program is running, the program may become uncontrollable. Although the emulator attempts to internally input a reset signal and resume execution of the program after it detects a reset input through the reset pin, this may lead to a break in execution. |
- | [E1] [E20] [EZ Emulator]
An error message "A timeout error. The MCU is in the reset state. The system was reset." is displayed in cases of contention between a reset (e.g. input of a reset signal through the reset pin, or reset of the CPU by the watchdog timer) and operations by the emulator system to the microcontroller (e.g. memory reference in the Memory panel. The emulator is initialized and the user program stops running. After the system is reset, trace records are initialized too. You can continue with debugging. |
- | If a reset input through the reset pin or an internal reset occurs under either of the following conditions, refer to Figure 2.195, showing the notes on the input of a reset signal through the reset pin, or Figure 2.196, showing the notes on internal resets. The points to note depend on the operating mode of the microcontroller and communication interface of the emulator.
[Conditions]
- While the user program is being executed in on-chip ROM disabled extended mode or user boot mode
- While the user program is being executed via FINE communication interface |
Figure 2.195 | Notes When a Reset Signal has been Input through the Reset Pin |
|
|
|
|
|
|
RX610, RX621, RX62N
|
JTAG
|
On-chip ROM disabled extended
|
The reset is canceled by the emulator.
Therefore, the reset timing here differs from when the actual microcontroller is operating singly.
|
|
RX71M, RX651, RX65N, RX64M, RX630, RX631, RX63N, RX63T, RX634
|
JTAG
|
User boot
On-chip ROM disabled extended
|
|
RX71M, RX651, RX65N, RX64M, RX630, RX631, RX63N, RX63T,
RX210, RX21A, RX220, RX231, RX23T, RX24T, RX110, RX111, RX113, RX130
|
FINE
|
Any mode
|
|
RX210, RX21A, RX220, RX231, RX23T, RX24T, RX110, RX111, RX113
|
FINE
|
User boot
On-chip ROM disabled extended
|
When a reset signal has been input through the reset pin during the execution of the user system, the timer measurement counter values and the acquired trace data are initialized.
|
Figure 2.196 | Notes When an Internal Reset has Occurred |
|
|
|
|
|
|
RX610, RX621, RX62N
RX630, RX631, RX63N, RX63T, RX634
|
JTAG
|
On-chip ROM disabled extended
|
Debugging can be performed after the reset is canceled and the microcontroller operating mode is set to the on-chip ROM disabled extended mode in the user program.
|
|
RX71M, RX651, RX65N, RX64M, RX630, RX631, RX63N, RX63T, RX634
|
JTAG
|
User boot
|
In the event of an internal reset, the emulator cannot control the CPU.
Do not allow any modules (e.g. watchdog timer) to cause an internal reset.
|
|
RX71M, RX651, RX65N, RX64M, RX630, RX631, RX63N, RX63T,
RX210, RX21A, RX220, RX231, RX23T, RX24T, RX110, RX111, RX113, RX130
|
FINE
|
Any mode
|
- | [E1] [E20] [EZ Emulator]
A software reset does not occur if either of the following operations is performed at the address of an instruction that is supposed to cause a software reset. |
- | Run in a state where a software or hardware (pre-execution) breakpoint is set |
This restriction only applies to JTAG communication.
Do not cause a software reset during FINE communication. Otherwise the emulator will not be able to control the microcontroller.