Events panel

This panel displays detailed information on the events that have been set on the Editor panel, Disassemble panel or Watch panel, as well as chooses to enable or disable event settings or deletes event settings (see "2.17 Event Management").

Note that this panel can be opened only when CS+ is connected with the debug tool.

Remark 1.

For details about event settings, see "2.17.7 Points to note regarding event setting."

Remark 2.

The events that have been set on the Function List panel or Variable List panel of the analysis tool are also managed on this panel.

Remark 3.

By double-clicking a line delimiting each area on the panel, it is possible to change the relevant area to the smallest displayable width without omitting the content in it.

Figure A.37

Events Panel [E1] [E20] [Simulator]

Figure A.38

Events Panel [EZ Emulator]

This section describes the following.

-	[How to open]

-	[Description of each area]

[Toolbar]

-	[[Edit] Menu (Event Panel-Only Items)]

-	[Context menu]

[How to open]

-	From the [View] menu, select [Event].

-	On the Editor panel or Disassemble panel, select [Timer Settings] and then [View Result of Timer] on the context menu.

-	On the Editor panel or Disassemble panel, move the caret to an event mark and then select [View Details in Event Panel] from the context menu.

[Description of each area]

(1)	[Name] area

This area lists the currently set event names in the form shown below.

Remark

By selecting the appropriate toolbar button, it is possible to limit the types of events displayed here (see [Toolbar]).

(a)

Check box

Clicking the check box displays or changes the set state of an event.

Note that when the set state of an event is changed, the Event mark also changes accordingly.

Enabled

When a specified condition becomes true, the event concerned with it occurs.

The event can be disabled by unchecking the check box.

Disabled

Even when a specified condition becomes true, the event concerned with it does not occur.

The event can be enabled by checking the check box.

Pending

A specified condition cannot be set in the program to be debugged.

The check box cannot be manipulated.

Remark 1.

The Run-Break timer event (not supported by the EZ Emulator) cannot be disabled or made pending.

Remark 2.

The enabled or disabled settings of an unconditional trace event and other trace events are controlled exclusively of each other. Therefore, although the unconditional trace event, one of the built-in events, is enabled by default, when either a trace start or a trace end event is set, it is automatically disabled at the same time, in which case, a trace event (consisting of a trace start and a trace end event that are combined into one) is enabled.
Conversely, when the set trace event is disabled, the unconditional trace event is automatically re-enabled.

Caution

[Simulator]
For the timer measurement event to be enabled, both timer start and end events should be specified.

(b)	Event mark

The event mark indicates the type of an event and shows its currently set state.

The displayed event marks and their meanings are as follows:

Table A.11

Event Marks

Type of event		Enabled	Disabled	Pending	Remark
Hardware Break					-
Software Break [E1] [E20] [EZ Emulator]					-
Combination break [E1] [E20] [EZ Emulator]					-
Unconditional Trace				None	-
Run-Break Timer			None	None	-
Trace					Displayed on only the Events panel
	Trace start				Displayed on only the Editor panel and Disassemble panel
	Trace end				Displayed on only the Editor panel and Disassemble panel
Timer Result					Displayed on only the Events panel
	Timer start				Displayed on only the Editor panel and Disassemble panel
	Timer end				Displayed on only the Editor panel and Disassemble panel
Point Trace					-
Printf event					-
Interrupt event [Simulator]					-
Multiple settings of above events		Note 1	Note 2	Note 3	Displayed on only the Editor panel and Disassemble panel

Note 1.

This applies when there is at least one enabled event among multiple events.

Note 2.

This applies when there is no enabled event but at least one disabled event among multiple events.

Note 3.

This applies when all of multiple events are made pending.

(c)	Event name

The type of an event and its ID number are displayed as an event name.

The ID number is automatically assigned beginning with 0001 for each event type. (Even when an event that was once set is deleted, the other events are not reassigned ID numbers.)

The displayed event types are as follows:

Table A.12

Event Types

Event Type

Description

Hardware Break

(BreakNote1)

This event is such that the debug tool successively checks break condition during program execution and, when the condition is met, causes the program to break.

-> See "2.10.2 Stop the program at the arbitrary position (breakpoint)"

-> See "2.10.4 Stop the program with the access to variables/I/O registers"

Software Break

(BreakNote1)

[E1] [E20] [EZ Emulator]

This event is such that instruction code at an address where a break is to occur is rewritten with a break instruction, so that when the instruction is executed, the program is made to break.

-> See "2.10.2 Stop the program at the arbitrary position (breakpoint)"

Combination break
[E1] [E20] [EZ Emulator]

When, while the debug tool successively is checking plural break conditions during program execution, the combination condition is met, this event causes the program to break.

->See 2.10.5 Set multiple break events in combination (Combination break) [E1] [E20] [EZ Emulator]

Unconditional Trace

Trace data is automatically collected at the same time the program starts running, and collection of trace data is halted simultaneously when the program stops.

Since this event is a built-in event Note2, it cannot be deleted. (This event is Enabled by default.)

-> See "2.13.2 Collecting an execution history up to a halt"

Run-Break Timer

A measurement of the program's execution time automatically begins at the same time the program starts running, and the measurement of execution time is halted simultaneously when the program stops. Since this event is a built-in event Note2, it cannot be deleted. (This event is Enabled by default.)

-> See "2.14.2 Measuring execution time from start to stop"

Trace

This event is such that when the condition set by a trace start and a trace end event is met, collection of trace data begins and then ends (displayed when either a trace start or a trace end event is set).

-> See "2.13.3 Collecting an execution history in a section"

Timer ResultNote3

This event is such that when the condition set by a timer start and a timer end event is met, a measurement of the program's execution time begins and then ends (displayed when either a trace start event or a trace end event is set).

-> See "2.14.3 Measuring execution time in a section"

Point Trace

This event is such that when a specified variable or I/O register is accessed by program execution, the accessed information is recorded in trace memory.

-> See "2.13.4 Collecting an execution history only when conditions are met"

Printf

This event is such that program execution is momentarily halted at any location and then a printf command is executed by a software process (i.e., an action event).

-> See "2.16.1 Insert printf"

Interrupt
[Simulator]

This event generates an interrupt at any place during program execution (action event).

-> See "2.16.2 Insert an interrupt event [Simulator]"

Note 1.

A breakpoint that is set by clicking the mouse once is displayed as "Break" (see "2.10.2.2 Set a breakpoint").

Note 2.

This is an event that is set by default in the debug tool.

Note 3.

[E1] [E20] [EZ Emulator]
Timer measurement sections are assigned channel numbers for each event type as their identification numbers (example: Timer Result 1).
The number of sections in which timer measurements are possible differs with each microcontroller used. Note the RX100 Series does not support timers.
- RX600 Series: Two sections
- RX200 Series: One section
[Simulator]
Only one section is available for timer measurement.

Remark

In addition to the above event types, following event types may be displayed if events (breakpoints or break events) have been set on the Function List panel or Variable List panel of the analysis tool.

-	For breakpoints for a function: "Break at start of function"

-	For break events for a variable: "Access break to variable"

(d)	Zoom in or out on a view

To zoom in and out of the Event panel view, change the zoom ratio by using the drop-down list on the toolbar of the Events panel while the focus is placed in the Event panel.

You can also change the zoom ratio by using the [Ctrl] key + mouse-wheel combination.

-	Using the [Ctrl] key + mouse-wheel forward will zoom into the view, making the contents larger and easier to see (max. 300%).

-	Using the [Ctrl] key + mouse-wheel backward will zoom out of the view, making the contents smaller (min. 50%).

If the panel is closed after the zoom ratio is changed, the changed zoom ratio is retained (next time, the panel will open at the changed zoom ratio).

(2)	[Detail] area

This area displays detailed information on each event.

The content of displayed information differs with event type.

The following shows how to read detailed information for each event type.

Table A.13

Detailed Information by Event Type

Type of event

Displayed content Note1

Hardware Break

(Generation condition: Execution-related)

Display form 1

Display example

Before Execution main.c#39 0x100

Before Execution - 0x300

Display form 2

Display example

Before Execution funcA + 0x10 0x100

Before Execution - 0x300

Hardware Break

(Generation condition: Access-related)

Display form 1

Display example

Read main.c#variable1 0x100 - 0x101 == 0x5

Write sub.c#variable2 0x200 - 0x200 == 0x7

Read/Write sub2.c#variable3 0x300 - 0x303 == 0x8

Display form 2

Display example

Read main.c#func1#variable1 0x100 - 0x101 == 0x10

Display form 3

Display example

Write variable1 0x100 - 0x101 == 0x10

Software Break

[E1] [E20] [EZ Emulator]

Display form1

Display example

Before Execution main.c#40 0x102

Before Execution sub.c#101 0x204

Display form 2

Display example

Before Execution funcA + 0x12 0x102

Combination break

(Generation condition: Execution-related, Access-related)

[E1] [E20] [EZ Emulator]

Display form

Display example

-	After execution main.c#100 0x300

-	After execution funcA + 0x10 0x100

-	Write sub.c#variable2 0x200 - 0x200 == 0x7

-	Read/Write sub2.c#variable3 0x300 - 0x303 == 0x8

Unconditional Trace

Display form

Display example

Run-Break Timer

Display form

Total: <Total execution time>

Display example

Total: 1000ms

Total: OVERFLOW

Display form 2

Total:<Total execution time> Execution Cycle Count:<Total number of cycles executed> Execution Instruction Count:<total number of instructions executed> [Simulator]

Display example

Total: 3300ns Execution Cycle Count: 330 Execution Instruction Count: 200

Trace

(Generation condition: Execution-related, Access-related)

[E1] [E20] [EZ Emulator]

Display form

Start: <Combination condition for trace start> End: <Combination condition for trace end> Start/End: <Total number of trace start/trace end event>Note2

Display example

Start: OR End: OR Start/End: 6

-	Start After Execution main.c#100 0x300

-	Start After Execution funcA + 0x100 0x300

-	Start Write variable1 0x100-0x101 == 0x10

-	End After Execution main.c#200 0x100

-	End After Execution funcA + 0x10 0x100

-	End Read main.c#variable1 0x100-0x101 == 0x5

Trace

(Generation condition: Execution-related, Access-related)

[Simulator]

Display form

Start: OR End: OR Start/End: <Total number of trace start/ trace end events>Note2

Display example

Start: OR End: OR Start/End: 6

-	Start Before Execution main.c#100 0x300

-	Start Before Execution funcA + 0x100 0x300

-	Start Write variable1 0x100-0x101== 0x10

-	End Before Execution main.c#200 0x100

-	End Before Execution funcA + 0x10 0x100

-	End Read main.c#variable1 0x100-0x101 == 0x5

Timer Result

(Generation condition: Execution-related, Access-related)

[E1] [E20] [EZ Emulator]

Display form

Total:<Total execution time > Start/End: <Total number of timer starts/ timer ends>Note 2

-	<Total execution time> <Pass count>

-	<Start/end> <Detailed information on timer start/timer end>

Display example

Total: 10ms Start/End: 6

-	Total: 10ms Pass Count: 5

-	Start After Execution main.c#100 0x300

-	Start After Execution funcA + 0x30 0x100

-	Start Write variable1 0x100-0x101== 0x10

-	End After Execution main.c#100 0x300

-	End After Execution funcA + 0x50 0x100

-	End Read main.c#variable1 0x100-0x101 == 0x5

Timer Result

(Generation condition: Execution-related, Access-related)

[Simulator]

Display form

Total:<Total execution time > Start/End: <Total number of timer starts/ timer ends>Note 2

-	<Total execution time> <Pass count>

-	<Start/end> <Detailed information on timer start/timer end>

Display example

Total: 10ms Start/End: 2

-	Total: 10ms Pass Count: 5

-	Start Write variable1 0x100-0x101== 0x10

-	End Before Execution main.c#100 0x300

Point Trace

(Generation condition: Access-related)

Display form 1

Display example

Read variable1 0x100

Display form 2

Display example

Write sub.c#variable2 0x200

Format3

Display example

Read/Write sub.c#func1#variabl3 0x300

Printf event

(Action event)

Display form

Display example

Before Execution main.c#39 0x100 aaa, bbb, ccc

After Execution sub.c#100 0x200 Result of aaa : aaa

Interrupt event

(Action event)

[Simulator]

Display form

<Generation condition> <File name # line number> <Address> interrupt vector: <Interrupt vector> Priority level: <Interrupt priority>

Display example

Before execution main.c#39 0x100 Interrupt vector: 1c Priority level: 7

Note 1.

Following are the details on the display format.

<Generation condition>	One of the following conditions is displayed: [E1] [E20] Execution-related: Before Execution, After Execution Access-related: Read, Write, Read/Write [Simulator] Execution-related: Before Execution, Access-related: Read, Write, Read/Write
<File name # Line number>	A source file name and a line number in the source file are displayed. The display form is the same as for the scope specification expression of a watch-expression. If there are multiple load module files that are downloaded, <Load module name$File name#Line number> is displayed. For events set on the Disassemble panel, however, a <Line number> is displayed in the form <Symbol + Offset>, if the following applies: - Line information exists and a specified event set position is not at the beginning of line information. - No line information exists, but symbol information exists. Also, a line number is displayed with "-," if the following applies: - No line information exists, and no symbol information exists.
<Variable name>	A variable name in a source file is displayed. The display form is the same as for the scope specification expression of a watch-expression.
<Comparison condition>	A comparison condition (==) is displayed. This is not displayed if no comparison value is specified.
<Comparison value>	A comparison value is displayed. This is not displayed if no comparison value is specified.
<Address>	The beginning and the end address of a specified variable in a memory area are displayed (always in hexadecimal).
<Combination condition>	One of the following conditions is displayed: OR, AND, Sequential
<Detailed information on combination break>	Detailed information on combination break event is displayed.
<Total execution time>	The total execution time measured by a timer is displayed. The time is expressed in one of ns/s,/ms/s/min units. (However, if expressed in "min," a "s" digit is displayed at the same time.) If the timer has overflowed (see "2.14.4 Range of measurable time") or the value is invalid, "OVERFLOW" is displayed.
<Combination condition for trace start>	One of the following conditions is displayed: OR, AND, Sequential
<Combination condition for trace end>	An OR condition is displayed.
<Total number of trace start/trace end event>	The total number of trace start and trace end events is displayed.
<Start/end>	Displays whether the content of the detailed information is about start event or end event.
<Detailed information on trace start/trace end>	Detailed information on trace start and trace end events is displayed.
<Pass count>	The pass count of a timer is displayed. If the timer has overflowed (see "2.14.4 Range of measurable time") or the value is invalid, "OVERFLOW" is displayed.
<Total number of cycles executed>	Displays the total number of cycles executed between Run-Break as the result of measurements made.
<Total number of instructions executed>	Displays the total number of instructions executed between Run-Break as the result of measurements made.
<Print event setting>	The <Output character string>: <Variable expression> specified in the Action Events dialog box is displayed.
<Interrupt vector>	Displays the interrupt vector specified in the Action Events dialog box or Detailed Settings of Interrupt Events dialog box [Simulator].
<Interrupt priority>	Displays the priority level specified in the Action Events dialog box or Detailed Settings of Interrupt Events dialog box [Simulator].

Note 2.

When this line is clicked, detailed information on the lines below that is displayed.

(3)	[Comment] area

This area permits the user to enter freely a comment on any event that is set.

To enter a comment, select the event for which you want to enter a comment and click in this area or select [Edit Comment] on the context menu, and then enter any text directly from the keyboard. (Pressing the [Esc] key cancels the editing mode.)

When you've finished editing a comment, press the [Enter] key or move the focus to other than the edit area to complete your editing.

Note that a comment can be entered for up to 256 characters each, and the comment is saved as the one set by the current user.

[Toolbar]

		Deletes a selected event or an event condition. However, the built-in events (unconditional trace and Run-Break timer events) cannot be deleted.
		Displays hardware break-related events (default).
[E1] [E20] [EZ Emulator]		Displays software break-related events (default).
		Displays trace-related events (default).
		Displays timer-related events (default).
		Displays action events (Printf event or interrupt event) (default).
		Displays built-in events (unconditional trace and Run-Break timer events) (default).
		Opens the Editor panel, with the caret on it moved to the source line corresponding to the address where a selected eventNote is set.
		Opens the Disassemble panel (Disassemble1), with the caret on it moved to the disassembled result corresponding to the address where a selected eventNote is set.
		Opens the Memory panel (Memory1), with the caret on it moved to the memory value corresponding to the address where a selected eventNote is set.

Note	This does not include trace events, timer measurement events, and built-in events (unconditional trace and Run-Break timer events).

[[Edit] Menu (Event Panel-Only Items)]

The [Edit] menu used exclusively for the Events panel is as follows. (All other items are disabled.)

Delete		Deletes a selected event. However, the built-in events (unconditional trace and Run-Break timer events) cannot be deleted.
Select All		Selects all of the events displayed on this panel.
Find...		Opens the Find and Replace dialog box, with its [Find in Files] tab selected.
Replace...		Opens the Find and Replace dialog box, with its [Replace in Files] tab selected.

[Context menu]

Enable Event		Enables a selected event. However, this is ignored if the selected event is already enabled.
Disable Event		Disables a selected event. However, this is ignored if the selected event is already disabled.
Delete		Deletes a selected event or an event condition. However, the built-in events (unconditional trace and Run-Break timer events) cannot be deleted.
Select All		Selects all of the currently displayed events.
View Select		Shows the following cascaded menu to limit the event types to be displayed. By default, all items are selected.
	Hardware Break	Displays hardware break-related events.
	Software Break	Displays software break-related events.
	Timer Event	Displays timer-related events.
	Trace Event	Displays trace-related events.
	Action Event	Displays action events (Printf event).
	Built-in Event	Displays built-in events (unconditional trace and Run-Break timer events).
Timer Settings		Shows the following cascaded menu to make timer-related settings. However, this is enabled only when a timer-related event is selected.
	Init Timer	Initializes the timer to be used in a selected event (not including the Run-Break timer event).
	Nanosecond	Displays the result of a selected event measured by a timer in nanosecond (ns) units.
	Microsecond	Displays the result of a selected event measured by a timer in microsecond (s) units.
	Millisecond	Displays the result of a selected event measured by a timer in millisecond (ms) units.
	Second	Displays the result of a selected event measured by a timer in second (s) units.
	Minute	Displays the result of a selected event measured by a timer in minute (min) units.
Jump to Memory		Opens the Memory panel (Memory1), with the caret on it moved to the memory value corresponding to the address where a selected eventNote1 is set.
Jump to Disassemble		Opens the Disassemble panel (Disassemble1), with the caret on it moved to the disassembled result corresponding to the address where a selected eventNote1 is set.
Jump to Source		Opens the Editor panel, with the caret on it moved to the source line corresponding to the address where a selected eventNote1is set.
Edit Condition ...		Opens the detailed settings dialog box corresponding to a selected eventNote2. If a Trace event or combination break is selected, the Combination Condition dialog box [E1][E20] [EZ Emulator] is opened. If a Printf event is selected, the Action Events dialog box is opened.
Edit Comment		Places a comment on a selected event into editing mode. If a comment for the event already exists, the whole of its character string is selected.

Note 1.

This does not include trace events, timer measurement events, and built-in events (unconditional trace and Run-Break timer events).

Note 2.

This includes the following events:

-	Hardware break/execution-related events, access-related events, and timer measurement events [E1] [E20]