1 Features

1. Features

This debugger has the following functions.

1.1 Real-Time RAM Monitor Function

This function allows you to inspect changes of memory contents without impairing the realtime capability of target program execution.

The compact emulator system has 1 Kbytes of RAM monitor area which can be located in any contiguous address location or in 4 separate blocks comprised of 256 bytes each.

1.2 Break Functions

Software Break

This function causes the target program to stop immediately before executing the instruction at a specified address.

Up to 64 breakpoints can be set. If multiple breakpoints are set, the program breaks at one of the breakpoints that is reached.

Hardware Break

This function causes the target program to stop upon detecting a data read/write to memory, instruction execution, or the rising/falling edge of the input signal fed from an external trace cable.

The contents of events that can be set vary with each target MCU. Specified hardware break events can be used in one of the following combinations: z

Break when all specified break points are effected.(And) z

Break when all specified break points are effected simultaneously.(And(Same Time)) z

Break when any one of the specified break points is effected.(Or)

Address Interrupt Break

This function stops the target program immediately before executing an instruction at a specified address.

This function is realized by using the MCU's address interrupt interrupt. When debugging the

MCU's address interrupt interrupt function, deselect the Enable the Address Match Interrupt

Break Function check box on the MCU tab of the Init dialog box. That way, the address interrupt break function is disabled.

1.3 Real-Time Trace Function

This function records a target program execution history.

Up to 64K cycles of execution history can be recorded. This record allows inspecting the bus information, executed instructions, and source program execution path for each cycle.

3

1.4 GUI Input/Output Function

This function simulates the user target system's key input panel (buttons) and output panel on a window.

Buttons can be used for the input panel, and labels (strings) and LEDs can be used for the output panel.

4

1 Features

1.5 About RAM Monitor Function

This debugger supports the real time RAM monitor function which allows you to reference the memory data without sacrificing real time performance during execution of the target program.

1.5.1 RAM Monitor Area

This debugger has 1 Kbytes of RAM monitor area which can be located in any contiguous address location or in 4 separate blocks comprised of 256 bytes each.

1.5.2 Sampling Period

Sampling cycle means the display update interval.

You can specify this function in any window which supports the RAM monitor. (The interval of 100 ms is set by default.)

The actual sampling cycle may take longer time than the specified cycle depending on the operating environment. (Sampling cycle depends on the following environments.) z

Communication interface z

Number of the RAM Monitor windows displayed z

Size of the RAM Monitor window displayed z

Number of ASM watch points within the RAM monitor area of the ASM Watch window z

Number of C watch points within the RAM monitor area of the C Watch window

5

1.5.3 Related Windows

The window where the function of the real time RAM monitor function can be used is shown below. z

RAM Monitor Window z

ASM Watch Window z

C Watch Window

6

1 Features

1.6 About Software Breaks Function

Software Break breaks the target program before execution of the command at the specified address. This break point is called software breakpoint.

The software breakpoint is set/reset in the Editor (Source) window or in the S/W Breakpoint

Setting window. You can also disable/enable a software breakpoint temporarily.

You can specify up to 64 software breakpoints. When specifying two or more software breakpoints, the breakpoint combination is based on the OR logic. (Arrival to any one of breakpoints breaks the target program.)

1.6.1 Setting of software breakpoint

The software breakpoint can be set by the following windows. z

Editor (Source) Window z

S/W Break Point Setting Window

You can double-click the mouse to set/reset the software breakpoint in the Editor (Source) window.

You can also switch to temporarily disable/enable the software breakpoint in the S/W Breakpoint

Setting window.

1.6.2 Area where software breakpoint can be set

The area which can be set for software breakpoint varies depending on the product.

For the areas available for software breakpoint, see the following:

The Internal RAM area and Internal ROM area can be designated for software breakpoint.

ATTENTION

During target program execution, a software break cannot be set as an internal ROM area.

7

1.7 About Hardware Breaks Function

The following designations are available as break events: z

Address designation

„

Instruction fetch

„

Memory access

„

Bit access z

External trigger designation z

Interruption

The number of events that can be specified are two events of all. For the address designation method, instruction fetch and memory access allow the range designation and logical condition designation, in addition to the normal one-address designation. Moreover, instruction fetch allows you to specify the function name.

Memory access allows you to specify the comparison data to read/write data related to the specified address in the same manner as when setting the H/W breakpoint. It also allows mask designation to the comparison data.

These break events can be combined as below: z

Trace when all of the valid events are established (AND condition) z

Trace when all of the valid events are established at the same time (simultaneous AND condition) z

Trace when one of the valid events is established (OR condition)

8

1 Features

1.8 About Address Interrupt Breaks Function

This function stops the target program immediately before executing an instruction at a specified address. This function is realized by using the MCU's address match interrupt.

The address interrupt break function can only be used when the address match interrupt is not used in the user application. The count of breakpoints depends on the connected MCU.

Note

The address interrupt break function can only be used when the Enable the Address Match

Interrupt Break Function check box on the Init dialog box MCU tab is selected.

1.8.1 Setting and Deleting a Break Points

The address interrupt beakpoint can be set by the following windows. z

Editor (Source) Window z

Address Interrupt Break Point Setting Window

You can double-click the mouse to set/reset the address interrupt breakpoint in the Editor (Source) window (same as software breakpoints).

You can also switch to temporarily disable/enable the address interrupt breakpoint in the Address

Interrupt Break Point Setting Window.

9

1.9 About Real-time Trace Function

The real-time trace function records the execution history of the target program.

The execution history is referred to in the tracing window.

The execution history can be referred to in the following mode. z

BUS mode

This mode allows you to inspect cycle-by-cycle bus information. The display content depends on the MCU and emulator system used. In addition to bus information, this mode allows disassemble, source line or data access information to be displayed in combination. z

Disassemble mode

This mode allows you to inspect the executed instructions. In addition to disassemble information, this mode allows source line or data access information to be displayed in combination. z

Data access mode

This mode allows you to inspect the data read/write cycles. In addition to data access information, this mode allows source line information to be displayed in combination. z

Source mode

This mode allows you to inspect the program execution path in the source program.

1.9.1 Trace Area

The 64K cycles execution history can be referred to with this debugger.

The trace area of the following 5 mode is being supported. z

Break

64K cycles before target program stops z

Before

64K cycles before trace point z

About

32K cycles either side of trace point z

After

64K cycles after trace point z

Full

Until 64K cycles are written in the trace memory

"Break" is set by default. To refer the execution history before stopping the target program, use

"Break" (designation of trace event is not required).

To refer the execution history at any position, or to continue execution of the target program, specify the trace event and change the trance range.

10

1 Features

1.9.2 Trace Condition Setting

The following designations are available as trace events: z

Address designation

„

Instruction fetch

„

Memory access

„

Bit access z

External trigger designation (eight events) z

Interruption

The number of events that can be specified are two events of all. These break events can be combined as below: z

Trace when all of the valid events are established (AND condition) z

Trace when all of the valid events are established at the same time (And(same time) comdition) z

Trace when one of the valid events is established (OR condition)

1.9.3 Trace Data Write Condition

Trace data write conditions can be specified.

You can specify the following write conditions: z

Write conditions unlimited (default) z

Cycles from the start event established to the end event established z

Only cycles where the start event is established z

Cycles from the start event established to the start event unestablished z

Other than cycles from the start event established to the end event established z

Other than cycles where the start event is established z

Other than cycles from the start event established to the start event unestablished

11