Technical information

Section 3 Software Specifications when Using the SH7080 Series/SH7146 Series/SH/Tiny Series

Rev. 5.00 Aug. 18, 2009 Page 25 of 78

REJ10J1237-0500

Section 3 Software Specifications when Using the SH7080

Series/SH7146 Series/SH/Tiny Series

3.1 Differences between the MCU and the Emulator

1. When the emulator system is initiated, it initializes the general registers and part of the control

registers as shown in table 3.1. The initial values of the MCU are undefined. When the

emulator is initiated from the workspace, a value to be entered is saved in a session.

Table 3.1 Register Initial Values at Emulator Link Up

R0 to R14 H'00000000

R15 (SP) Value of the SP in the power-on reset vector table

PC Value of the PC in the power-on reset vector table

SR H'000000F0

GBR H'00000000

VBR H'00000000

MACH H'00000000

MACL H'00000000

PR H'00000000

2. The emulator uses the H-UDI; do not access the H-UDI.

3. Low-Power States (Sleep, Software Standby, and Module Standby)

⎯ When the emulator is used, the sleep state can be cleared with either the clearing function

or with the [STOP] button, and a break will occur.

⎯ The memory must not be accessed or modified in software standby state.

⎯ When the emulator is used, do not use the deep software standby mode.

4. Reset Signals

The MCU reset signals are only valid during emulation started with clicking the GO or STEP-

type button. If these signals are enabled on the user system in command input wait state, they

are not sent to the MCU.

Note: Do not break the user program when the _RES, _BREQ, or _WAIT signal is being low. A

TIMEOUT error will occur. If the _BREQ or _WAIT signal is fixed to low during break,