This product is a simulator debugger which allows you to run and evaluate your application program without any target hardware on Renesas integrated development environment "High-performance Embedded Workshop". It provides a source-level-debugging environment with abundant break features and advanced functions such as coverage measurement and virtual interrupts. In addition, its user friendly interface and multi-window (overlappable) will offer stress-free debugging environment.

This product is a component of the compiler package and assembler package. Installing one of the above packages allows you to debug using this simulator debugger under a High-performance Embedded Workshop environment (Renesas IDE).

Features

  • I/O script function (peripheral I/O simulation such as a timer)
  • Interrupt simulation function
  • Programing a target system using the GUI Input Window and GUI Output Window for simple targetless debugging
  • Comfortable debugging environment provided by drag & drop operation
  • C language and assembly language source level debugging and many other basic debug features
  • RAM monitoring
  • On-line help in HTML
  • Learn More

Release Information

Latest Ver.: V.1.02 Release 00

Released: Sep 16, 2006

Details of upgrade (See Tool News)

Operating Environment

Documentation & Downloads

Title Other Languages Type Format File Size Date
User Guides & Manuals
High-performance Embedded Workshop V.4.09 User's Manual 日本語 Manual PDF 4.16 MB
High-performance Embedded Workshop HewTargetServer User's Manual 日本語 Manual PDF 1.85 MB
740 Simulator Debugger V.1.02 User's Manual (for 740 Family) 日本語 Manual PDF 3.92 MB
Introducing I/O Script Sample Programs (Simulator Debugger for 740 Family) – Manual PDF 81 KB
Tool News
A Note on Using Debugger Products for the M16C and 740 Families of MCUs 日本語 Tool News - Note PDF 195 KB
A Note on Using the Debuggers for the M16C Family; the H8/300H Tiny Series, H8 Family; and the 740 Family of MCUs 日本語 Tool News - Note PDF 194 KB
A Note on Using Debuggers for the SuperH RISC engine, M16C, H8SX, H8S, H8, and 740 MCU Families 日本語 Tool News - Note PDF 195 KB
A Note on Using the Debuggers for the M32R, M16C, H8 (H8/300H Tiny Series Only), and 740 MCU Families 日本語 Tool News - Note PDF 198 KB
Other
High-performance Embedded Workshop V.4.09 Release Note 日本語 Release Note PDF 307 KB
740 Simulator Debugger V.1.02.00 Release Notes 日本語 Release Note PDF 132 KB
info: For device-specific or order-specific documentation, submit a support request.

Functions

[Basic Functions]

Functions Description
Register Window Displays/changes content of flags and registers particular to the MCU.
Memory Window Displays memory content together with the address and label. Display format can be selected from among binary, decimal, hexadecimal, ASCII, SJIS (for Japanese) or JIS (for Japanese) .
RAM Monitor Window Displays memory content changed during target program execution. The area read during program execution is displayed in green, and the area written is displayed in red. (You can set colors of your choice.)
ASM Watch Window Monitors changes in memory content and variable content declared on the assembly language level. Display format can be selected from among binary, decimal, and hexadecimal. If the specified address is within the real-time RAM area, the area read is displayed in green, and the area written is displayed in red. (You can set colors of your choice.)
C Watch Window Displays C variable contents. In addition to a window that displays variable formula of your choice, there are windows that display external variables, local variables within a file, and local variables within a function.
Script Window Window for executing commands from the keyboard or script files. An area is provided for displaying command execution results and command history. Execution results can be output to a file.
S/W Break Point Setting Window Enables set / cancel the software break points. You can set up to 64 break points (OR condition).
H/W Break Point Setting Dialog Enables set / cancel the hardware break points. You can set up to 64 break points (OR condition).
Basic Functions

[Advanced Functions]

Functions Description
I/O Timing Setting Window Inputs/outputs to a port, and sets/displays interrupts. It is also possible to check cycle-by-cycle data input, definition of interrupt, and change of output data. And, a timer interrupt occurrence at time intervals in units of msec/µsec is enabled. (Note that the CPU operating frequency need to be specified.) Besides, there is the I/O script function that can simulate peripheral I/O (timer, analog to digital converter, etc.) operation. By registering I/O script of peripheral I/O (written in script format in a file) in the I/O window, you can simulate operation of that device. For example, to simulate timer operation, register the following script with "while" and "if":

[I/O script defining example of timer operation] 
	{
	 	while(1){
			; Down count of Counter
				waitc [0x0020] + 1
			; Occur timer interrupt
				int FFEE
		}
	}
GUI I/O Window Window for creating key input panels or output panels for the user target system by simple mouse operation.
[Input panel]: You can define operation of data input or interrupt for the created keys. Pressing the key while the program is running generates data input or interrupt.
[Output panel]: You can display by LED or label according to the value of the output data.
Coverage Window Shows coverage measurement results of C language functions. Start/end addresses and coverage can be checked. Double-clicking the line to be checked opens a coverage source window to show executed/unexecuted in a line of source.
Advanced Functions

Specifications

Functions Description
I/O simulation Data can be input/output cycle-by-cycle.
Interrupt simulation Interrupt occurrence in units of cycles or time (msec/µsec) is enabled.
Execution time measurement Execution time is worked out by the CPU operating frequency and the number of CPU execution cycles. (Note1)
RAM monitor display Any 1K byte of memory is displayable.
Coverage measurement Coverage of all memory area can be measured.

Note

  1. This simulator debugger is an instruction set simulator and does not include bus width, queue, or wait events when counting the number of cycles. Rather, it uses the values indicated in the microcomputer software manual for the number of cycles.