P0700WSD7-N4E

Notes on SuperHTM RISC engine Simulator/Debugger

Thank you for using the SH Series Simulator/Debugger (hereinafter referred to as

simulator/debugger).

Please note the following when using this version of the simulator/debugger.

1. Source-Level Execution

1.1 Step

Even standard C libraries are executed by steps. To return to a higher-level function, enter the
[Step Out] button. In a for statement or a while statement, executing a single step does not move
execution to the next line. To move to the next line, execute two steps.

2. Line Assembly

2.1 Radix

Regardless of the Radix setting, the default for line assembly input is decimal. Specify H' or 0x as
the radix for a hexadecimal input.

3. Watch

3.1 Local Variables at Optimization

Depending on the generated object code, local variables in a C source file that is compiled with the
optimization option enabled will not be displayed correctly. Check the generated object code by
opening the disassembly window.

If the allocation area of the specified local variable does not exist, displays as follows.

Example: The variable name is asc.

asc = ? - target error 2010 (xxxx)

page 1 of 7
3.2 Variable Name Specification

When a name other than a variable name, such as a symbol name or a function name, is specified,
no data is displayed.

Example: The function name is main.

main =

3.3 Array Display

When array elements exceed 1000, elements after 1000 will not be displayed.

3.4 Modification of Variable Contents

When modifying variable contents, do not select the Japanese character string as the input data
type. For Japanese character string input, use the [Localized Dump] window.

4. Symbol Description for Expression

Enclose the symbol name within braces ({ }) when using, in an expression, a symbol that satisfies
all of the following conditions.

1. The symbol is defined in the Symbols dialog box.

2. The symbol name includes a character other than an alphanumeric character.
ex. {ASM_DATA1[10]}

5. Memory Resource Modification Function

5.1 Memory Resource Modify Dialog Box

Note that the specifications of the memory resource modification function of the
simulator/debugger differ from those of Hitachi emulators.

The specifications for the simulator/debugger are as follows:

• When the memory attribute (Read, Write, or Read/Write) is the same after the memory
resource is modified:
The simulator/debugger assumes the memory resource size has been modified and changes the
memory resource size to the specified value.

page 2 of 7
• When the memory attribute (Read, Write, Read/Write) changes due to modification of the
memory resource:
The simulator/debugger assumes the memory resource attribute has been modified and
changes the memory resource attribute of the specified range to the specified value.

6. Trace Function (only for the SH3, SH3E, and SH-3DSP)

6.1 FPU, MAC, or DSP Register Access Information

When an instruction is executed to write data in the FPU, MAC, or DSP register, the
simulator/debugger does not display access information in the trace information.

6.2 FMOV Instruction Access Info rmation

When data is written to the memory using the FMOV instruction, the simulator/debugger does not
display access information in the trace information.

6.3 Pipeline Display

For instructions that programming manuals do not describe as writing back data to registers, and if
data is written to registers as a result of the execution of such instructions, the simulator/debugger
displays such an operation as a stage of memory access and write back in the trace information.
The cycle numbers are correctly displayed.

Trace display by the simulator/debugger Description in the

programming manual

IF DE EX MA SW IF DE EX MA SW
05 NOP 06 05 06 05
06 TRAPA #H'10 07 06 05 -- 06
-- - - - - - -- -- 06 -- -- 06
-- - - - - - -- -- 06 06 -- -- 06
-- - - - - - -- -- 06 06 -- -- 06
-- - - - - - -- -- 06 06 06 (06):SSR<-60000001 -- -- 06
-- - - - - - 08 -- -- 06 06 (06):SPC<-00001006 07 -- --
-- - - - - - 09 08 -- -- -- 08 07 --

page 3 of 7
7. Entry Point

7.1 Setting the Entry Point

Even when an entry point is specified by the ENTRY option of the linkage editor, the entry point
address is not set for the PC during program downloading. Set the PC before program execution.

8 Utilizing Previously Installed HDI Systems

HDI systems with different versions cannot be used together. Therefore, when using a previously
installed HDI system after installing the current HDI system, the previously installed HDI system
must be installed again.

When using an HDI with a different debugging platform, initiate the HDI with the following
procedure:

• Open the [Run...] menu from the [Start] menu on the task bar.
• In the [Run...] menu, enter the following to initiate this HDI with the /n option selected.
<Directory path name in which the HDI is installed>\hdi /n (RET)

/n initiates the HDI without loading the previously used session files.

If session files for a different debugging platform exist, the following error message is displayed
when initiating this HDI.

invalid target system: <previously used debug platform name>

9. Operation During File Access

Do not perform operations while data is being saved through the Load Program, Verify Memory,
Save Memory, or Trace window; otherwise data may not be saved correctly.

10. Operation of the Program Window when the Displayed Program is

Modified
After modifying the program displayed in the program window and reloading the source files and
load modules, close the program window then open it again; otherwise the program displayed in
the window may not be correct.

page 4 of 7
11. The Number of Breakpoints and the Number of Stop-at Points in the
Run... Menu

Up to a total of 255 PC breakpoints and Stop-at points in the Run... menu can be specified. If 255
breakpoints are specified, no Stop-at points in the Run... menu can be specified. Specify 255 or
fewer points for the total numbers of PC breakpoints and Stop-at points in the Run... menu.

12. File Specification by Command File

The current directory may be moved depending on specification of the command file. It is
recommended that file specification in the command file be described by an absolute path so that
file specification is not affected by current directory moving.

Example: FILE_LOAD C:\\HEW\\HDI4_SH\\TUTORIAL\\SORT.ABS

13. Radix in [Register] Dialog Box

The default input radix in the [Register] dialog box is hexadecimal regardless of the Radix setting.
If you want to input the radix other than hexadecimal, specify the prefix code such as B’. The
Radix is changed to hexadecimal setting after a value has been input in the [Register] dialog box.
If you want to use the radix other than hexadecimal as default, reset the Radix.

14. Note on Moving Source File Position after Creating Load Module

When the source file is moved after the load module has been created, the [Open] dialog box,
which specifies the source file, may be displayed during debugging the created load module.
Select the corresponding source file and click the [Open] button.

15. Limitations when Using Old Version of Windows 95

When using the old released version (4.00.950a, etc.) of Windows  95, an illegal operation may
occur; for example, the HDI is abnormally terminated by an application error if [Options…] is
selected from the [Setup] menu. This is because of the old version of COMCTL32.DLL in the
System directory in the Windows directory. Download the updated program of COMCTL32.DLL
from the Microsoft  homepage, or update the version of Windows 95

16. Limitation of stack trace window

When the stack trace window is displayed with the interruption function executed, the display
before the interruption function becomes incorrect.

page 5 of 7
17. Limitation of profiler
Profiler does not support overlay function.

18. SH4 and SH4BSC Simulator/Debugger Limitations

• In SH4BSC simulator/debugger, if the lower three bits of the source and destination addresses
differ in a DMA transfer, the last data transferred will be invalid.
e.g. SAR0=2000 DAR0=4004 DMATCR0=2 CHCR0=5491
Memory contents of address H'2000: 0102030405060708
Contents of address H'4004 after DMA transfer: 0106
• In SH4 and SH4BSC simulator/debugger, even if an instruction is modified for an address
where decoding has been completed, the pipeline is not reset and executed.
• In SH4BSC simulator/debugger, if memory is accessed by a data size that differs from the size
specified by the break data, the program may not break when the break conditions are satisfied.
To avoid this, specify the same data size for the memory access data size and break data size.
• In SH4 and SH4BSC simulator/debugger, the pipeline execution for double precision FDIV
and FSQRT instructions in the SH4 simulator/debugger are different from those in the user
system. For the SH4 simulator/debugger, one more cycle is displayed for the F3 stage pipeline.

19. SH-3DSP Simulator/Debugger Limitations

• Exception Code During DSP Loop Execution
If an exception is generated during the DSP loop execution, the exception code set in the
EXPEVT (exception event register) will differ from that described in the programming manual.
The exception code in the DSP Loop
General exception events Programming Simulator
Manual
TLB miss exception/TLB invalid exception (Read) H'070 H'040
TLB miss exception/TLB invalid exception (Write) H'070 H'060
TLB protection exception (Read) H'0D0 H'0A0
TLB protection exception (Write) H'0D0 H'0C0
CPU address error (Read) H'070 H'0E0
CPU address error (Write) H'070 H'100
• X/Y Memory Access Conflict
If instruction code and data is allocated for the XRAM memory (or XROM, or YROM, or
YRAM), stalls will not be generated by conflict even if the same XRAM memory is accessed
by the instruction code fetch and the MOVX or MOVY instruction in the same slot. Therefore,
the cycle number of the two types of access will differ.

page 6 of 7
• Pipeline Execution from an Address other than a Multiple of Four
If a pipeline execution is performed from an address other than a multiple of four, the fetch
stages will differ from those described in the programming manual.
e.g. When pipeline execution is performed from an address other than a multiple of four
Programming Manual Simulator
IF IF ID EX IF ID EX
IF ID EX IF ID EX
if ID EX if ID EX

page 7 of 7