Events panel

This panel is used to display the detailed information about the events that are set on the Editor panel/Disassemble panel/Watch panel. On this panel, you can change the setting state of the event between valid/invalid and delete the event (see "2.17 Manage Events").

This panel appears only when connected to the debug tool.

Remark 1.

Also see "2.17.6 Notes for setting events" for details on events (e.g. limits on the number of enabled events).

Remark 2.

Events set via the Function List panel or Variable List panel of the analyze tool (Program Analyzer) are also managed on this panel.

Remark 3.

This panel can be zoomed in and out by in the tool bar, or by moving the mouse wheel forward or backward while holding down the [Ctrl] key.

Remark 4.

When the separator line of each area in this panel is double-clicked, the width of the area changes to the shortest possible size that can display the contents of the area.

Figure A.28

Events Panel

 

This section describes the following.

-

[How to open]

-

[Description of each area]

-

[Toolbar]

-

[[Edit] menu (Events panel-dedicated items)]

-

[Context menu]

[How to open]

-

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

-

[Simulator]

On the Editor panel/Disassemble panel, select [Timer Settings] >> [View Result of Timer] from the context menu.

[Description of each area]

(1)

[Name] area

A list of the event names that have currently been set is displayed in the form shown below.

Remark

It is possible to limit the event to be displayed by clicking the button on the toolbar (see "[Toolbar]").

(a)

Check box

The setting state of the event is displayed/changed.

Note that the Event mark is changed depending on the setting state of the event.

 

Valid state

Event occurs when the specified condition is met.

It is possible to set the event to an invalid state by removing the check.

 

Invalid state

Event does not occur when the specified condition is met.

It is possible to set the event to a valid state by removing the check.

 

Suspended state

The conditions that have been specified cannot be set with the program of the debugging target.

It is not possible to operate the check box.

Remark 1.

Both of the Timer Start event and Timer Stop event is must be set for the Timer Result event. Therefore, it is not possible to set a particular event to a valid state by only the setting of one of these (at the same time as both events are set, they are treated as grouped events as a Timer Result).

Remark 2.

It is not possible to set the Run-Break Timer event to an invalid/suspended state.

Remark 3.

The setting of the Unconditional Trace event and the Trace event to valid or invalid state is exclusively controlled. Therefore, the Unconditional Trace event, which is a built-in event, is valid state by default, but if either a trace start event/trace end event is set, it automatically becomes invalid state, and the Trace event, which is a event name that is collectively called with a trace start event and a trace end event, becomes valid state. Conversely, if the set Trace event is invalid state, the Unconditional Trace event automatically becomes valid state.

(b)

Event mark

The event mark shows the type of event, and in addition shows the current setting state.

The meanings of the marks displayed are as follows:

Table A.8

Event Mark

Event Type

Valid State

Invalid State

Suspended State

Note

Hardware Break

 

 

 

Including a hardware break point

Software Break

 

 

 

Including a software break point

Break at start of function

 

 

 

A break event that can be set via the analyze tool.

Access break to variable

 

 

 

Unconditional Trace

 

 

None

-

Run-Break Timer

 

None

None

-

Trace

 

 

 

Displayed on only the Events panel

 

Trace start

 

 

 

Displayed on only the Editor panel/Disassemble panel

Trace end

 

 

 

Timer Result

 

 

 

Displayed on only the Events panel

 

Timer start

 

 

 

Displayed on only the Editor panel/Disassemble panel

Timer end

 

 

 

Performance Measurement

 

 

 

Displayed on only the Events panel

 

Performance measurement start

 

 

 

Displayed on only the Editor panel/Disassemble panel

Performance measurement end

 

 

 

Point Trace

 

 

 

-

Printf (Action event)

 

 

 

-

Setting of two or more events

Note 1

Note 2

Note 3

Displayed on only the Editor panel/Disassemble panel

Note 1.

There is one or more event with valid state.

Note 2.

There is no event with valid state and at least one event with invalid state.

Note 3.

All the set events are suspended state.

(c)

Event name

The event type and ID number are displayed as the event name.

A number from 0001 is automatically provided as the ID number for each event (no renumbering of the ID number is done even in the event that an event that has been set once is deleted).

Event types that are displayed are as follows:

Table A.9

Event Type

Event Type

Description

Hardware Break

(BreakNote 1)

Breaks the program when the condition is met while the debug tool monitors the break condition all the time during program execution.

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

-> See "2.9.4 Stop the program at the arbitrary position (break event)"

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

Software Break

(BreakNote 1)

Breaks the program when the instruction, which an address code to break is rewritten for the break instruction, is executed.

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

Break at start of function

This event type is a Hardware Break (execution type) that is set in the Function panel of the analyze tool (Program Analyzer).

Access break to variable

This event type is a Hardware Break (access type) that is set in the Variable panel of the analyze tool (Program Analyzer).

Unconditional Trace

Automatically collects the trace data with start of a program execution, and stops collecting the trace data with stop of the program execution.

This event cannot be deleted because of the built-in eventNote 2 (this event is set to a Valid state by default).

-> See "2.12.2 Collect execution history until stop of the execution"

Run-Break Timer

Automatically measures the execution time of a program with start of the program execution, and stops the measurement with stop of the program execution. This event cannot be deleted because of the built-in eventNote 2 (this event is set to a Valid state by default).

-> See "2.13.1 Measure execution time until stop of the execution"

Trace

Starts/stops collecting the trace data when the condition specified with a trace start event and a trace end event is met (this event is displayed when either a trace start event or a trace end event is set).

-> See "2.12.3 Collect execution history in a section"

Timer Result n

 

Starts/stops measuring the execution time of a program when the condition specified with a timer start event and a timer end event is met (this event is displayed when either a timer start event or a timer end event is set).

"n" indicates the channel number in which a Timer Result event is set.

-> See "2.13.2 Measure execution time in a section"

Performance Measurement n

Starts/stops performance measurement when the condition specified with a performance measurement start event and a performance measurement end event is met (this event is displayed when either a performance measurement start event or a performance measurement end event is set).

"n" indicates the channel number in which a Performance Measurement event is set.

-> See "2.14.1 Measure the performance in a section"

Point Trace

Records the information as the trace data only when accessing the specified variable or I/O register during execution of a program.

-> See "2.12.4 Collect execution history only when the condition is met"

Printf

 

Executes printf command in software processing after temporary stopping a program in execution at an arbitrary position (action event).

-> See "2.16.1 Inset printf"

Note 1.

A breakpoint that is set by a one click operation of the mouse is displayed "Break" (see "2.9.3.1 Set a breakpoint").

Note 2.

This is set in the debug tool by default.

(2)

[Detail Information] area

Detailed information about each event is displayed.

The contents of the information that is displayed differ depending on the event type as follows:

Table A.10

Detailed Information with Event Type

Event Type

Displayed ContentNote 1

Hardware Break

(Condition: execution)

Format1

<PE> <Condition to occur> <File name#Line number> <Address>

Example

CPU1 Before Execution main.c#39 0x100

CPU1 After Execution sub.c#100 0x200

CPU1 Before Execution - 0x300

CPU1 Execution main.c#39 0x300 [Simulator]

Format2

<PE> <Condition to occur> <Symbol + Offset> <Address>

Example

CPU1 Before Execution funcA + 0x10 0x100

CPU1 After Execution funcB + 0x20 0x200

CPU1 Before Execution - 0x300

Hardware Break

(Condition: access)

Format1

<PE> <Condition to occur> <File name#Variable name> <Address(range)> <Comparison condition> <Comparison value>

Example

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

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

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

Format2

<PE> <Condition to occur> <File name#Function name#Variable name> <Address(range)> <Comparison condition> <Comparison value>

Example

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

Format3

<PE> <Condition to occur> <Variable name> <Address(range)> <Comparison condition> <Comparison value>

Example

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

Software Break

Format1

<Condition to occur> <File name#Line number> <Address>

Example

Before Execution main.c#40 0x102

Before Execution sub.c#101 0x204

Format2

<Condition to occur> <Symbol + Offset> <Address>

Example

Before Execution funcA + 0x12 0x102

Unconditional Trace

 

Format

-

Example

-

Run-Break Timer

Format

Total: <Total execution time>

Example

Total: 1000ms

Total: OVERFLOW

Trace

(Condition: execution)

 

Format

Total of Start/End: <Total number of trace start/trace end events> Note 2

<PE> <Start/End> <Detailed information of trace start/trace end event>

Example

Total of Start/End: 4

-

CPU1 Start After Execution main.c#100 0x300

-

CPU1 Start After Execution funcA + 0x100 0x300

-

CPU1 End After Execution main.c#200 0x100

-

CPU1 End After Execution funcA + 0x10 0x100

Timer Result n

(Condition: execution)

 

Format

Total:<Total execution time > Total of Start/End: <Total number of timer start event/timer end event>Note 2

-

<Total execution time> <Pass Count> <Average> <Max> <Min>

-

<PE> <Start/End> <Detailed information of timer start event/timer end event>

Example

Total: 10ms Total of Start/End: 4

-

Total: 10ms Pass Count: 5 Average: 2ms Max: 4ms Min: 1ms

-

CPU1 Start After Execution main.c#100 0x300

-

CPU1 Start After Execution funcA + 0x30 0x100

-

CPU1 End After Execution main.c#100 0x300

-

CPU1 End After Execution funcA + 0x50 0x100

Performance Measurement n

(Condition: execution)

Format

<Performance measurement mode> <Performance measurement result> <Total number of performance measurement start event/performance measurement end event>

-

<PE> <Start/End> <Detailed information of performance measurement start event/performance measurement end event>

Example

ALL instruction count Count:10 Total of Start/End: 2

-

CPU1 Start After Execution main.c#100 0x300

-

CPU1 End After Execution main.c#100 0x300

Performance Measurement n

(Condition: access)

Format1

<Performance measurement mode> <Performance measurement result> <Total number of performance measurement start event/performance measurement end event>

-

<PE> <Start/End> <Condition to occur> <File name#Function name#Variable name> <Address(variable range)> <Comparison condition symbol> <Comparison value>

Example

ALL instruction count Count:10 Total of Start/End: 2

-

CPU1 Start Read main.c#variable1 0x100 – 0x101 == 0x5

-

CPU1 End Write sub.c#variable2 0x200 – 0x200 == 0x7

Format2

<Performance measurement mode> <Performance measurement result> <Total number of performance measurement start event/performance measurement end event>

-

<PE> <Start/End> <Condition to occur> <File name#Function name#Variable name> <Address(variable range)> <Comparison condition symbol> <Comparison value>

Example

ALL instruction count Count:10 Total of Start/End: 2

-

CPU1 Start Read main.c#func1#variable1 0x100 – 0x101 == 0x10

-

CPU1 End Write main.c#func1#variable1 0x100 – 0x101 == 0x10

Format3

<Performance measurement mode> <Performance measurement result> <Total number of performance measurement start event/performance measurement end event>

-

<PE> <Start/End> <Condition to occur> <Variable name> <Address(variable range)> <Comparison condition symbol> <Comparison value>

Example

ALL instruction count Count:10 Total of Start/End: 2

-

CPU1 Start Read variable1 0x100 – 0x101 == 0x10

-

CPU1 End Write variable1 0x100 – 0x101 == 0x10

Point Trace

(Condition: access)

Format1

<PE> <Condition to occur> <Variable name> <Variable address>

Example

CPU1 Read variable1 0x100

Format2

<PE> <Condition to occur> <File name#Variable name> <Variable address>

Example

CPU1 Write sub.c#variable2 0x200

Format3

<PE> <Condition to occur> <File name#Function name#Variable name> <Variable address>

Example

CPU1 Read/Write sub.c#func1#variable3 0x300

Printf

(Action event)

Format

<Condition to occur> <File name#Line number> <Address> <Setting of Printf event>

Example

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

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

Note 1.

Following are the details on the display format.

<PE>

If the microcontroller is multi-core, the core name is shown. If the microcontroller is single-core, nothing is shown.

<Condition to occur>

Displays one of the following conditions.

[Full-spec emulator][E1][E20]

Execution: Before Execution or After Execution

Access: Read, Write, Read/Write

[Simulator]

Execution: Execution

Access: Read, Write, Read/Write

<File name#Line number>

Shows the line number of the source. Display format is the same as the watch type scope specification expression. When multiple load module files are downloaded, <Load module file name$File name#Line number> is displayed.

For those events set in the Disassemble panel, display <Line number> in the format <Symbol + offset> in the condition below.

-

Line information exists and the specified position that the event is set not the top of the line information

-

Line information does not exist and symbol information exists.

Show <Line number> in "-" in the following condition.

-

Line information and symbol information does not exist.

<Variable name>

Shows the variable name in the source file. Display format is the same as the watch type scope specification expression.

<Comparison condition>

Condition to compare (==) is shown. If the comparison value is not specified, comparison condition is not shown.

<Comparison value>

Comparison value is shown. If the comparison value is not specified, comparison condition is not shown.

<Address>

Address in the memory area is shown (only in hex number).

<Start/End>

Shows whether the contents of the detailed information is start event or the stop event.

<Pass Count>

Shows the measurement result of the pass count of the timer.

If a timer overflow occurs (see "2.13.3 Measurable time"), or if the illegal value was acquired, "OVERFLOW" is displayed.

If measurements have not been performed yet, "Not measured" is displayed.

<Total>

Shows the measurement result of the timer total execution time.

The unit is either of ns/μs,/ms/s/min/clock (if, however, the unit is in "min", a value in "s" unit also appears).

If a timer overflow occurs (see "2.13.3 Measurable time"), or if the illegal value was acquired, "OVERFLOW" is displayed.

If measurements have not been performed yet, "Not measured" is displayed.

<Average>

Shows the measurement result of average execution of the timer.

The unit is either of ns/μs,/ms/s/min/clock (if, however, the unit is in "min", a value in "s" unit also appears).

If a timer overflow occurs (see "2.13.3 Measurable time"), or if the illegal value was acquired, "OVERFLOW" is displayed.

If measurements have not been performed yet, "Not measured" is displayed.

<Max>

Shows the measurement result of the maximum execution time of the timer.

The unit is either of ns/μs,/ms/s/min/clock (if, however, the unit is in "min", a value in "s" unit also appears).

If a timer overflow occurs (see "2.13.3 Measurable time"), or if the illegal value was acquired, "OVERFLOW" is displayed.

If measurements have not been performed yet, "Not measured" is displayed.

<Min>

Shows the measurement result of the minimum execution time of the timer.

The unit is either of ns/μs,/ms/s/min/clock (if, however, the unit is in "min", a value in "s" unit also appears).

If a timer overflow occurs (see "2.13.3 Measurable time"), or if the illegal value was acquired, "OVERFLOW" is displayed.

If measurements have not been performed yet, "Not measured" is displayed.

<Set print event>

Shows the variable expression and the character strings specified in the Action Events dialog box.

<Performance measurement mode>

Shows the mode of performance measurement.

The mode set in the Detailed Settings of Performance Measurement dialog box [Full-spec emulator][E1][E20] is displayed.

<Performance measurement result>

Shows the result of performance measurement.

If "Clock cycle", "Non-interrupt cycle", or "Interrupt disable cycle of DI/EI" is set as the performance measurement mode in the Detailed Settings of Performance Measurement dialog box [Full-spec emulator][E1][E20], the number of cycles is displayed, otherwise the number of counts is displayed.

Note 2.

Click this line to display the detailed information of the lower lines.

(3)

[Comment] area

The user can write comments for each event that has been set.

To input comments, click on this area, or select [Edit Comment] form the context menu after selecting the event in which you want to input comments, and then input directly the desired text from the keyboard (the edit mode is cancelled by pressing down the [Esc] key).

After editing the comments, complete the editing by pressing the [Enter] key or moving the focus to outside the edit region. Up to a maximum of 256 characters can be inputted for the comments, and this is saved as the settings of the user during use.

[Toolbar]

 

Deletes the selected event and event condition.

Note that it is not possible to delete the built-in events (Unconditional Trace event and Run-Break Timer event).

 

Displays events related to Hardware Break (default).

 

[Full-spec emulator]
[E1][E20]

Displays events related to Software Break (default).

 

Displays events related to the trace (default).

 

Displays events related to the timer (default).

 

Displays events related to performance measurement (default).

 

Displays events related to the action event (Printf event) (default).

 

Displays events related to the built-in event (Unconditional Trace event/Run-Break Timer event) (default).

 

Opens the Editor panel and jumps to the source line corresponding to the address where the selected eventNote is being set.

 

Opens the Disassemble panel and jumps to the disassemble results corresponding to the address where the selected eventNote is being set.

 

Opens the Memory panel and jumps to the memory corresponding to the address where the selected eventNote is being set.

Note

Events other than Trace events, Timer Result events and built-in events (Unconditional Trace events/Run-Break Timer events) can be objects of this button.

[[Edit] menu (Events panel-dedicated items)]

The following items are exclusive for [Edit] menu in the Events panel (all other items are disabled).

Delete

Deletes the selected event and event condition.

Note that it is not possible to delete the built-in events (Unconditional Trace event and Run-Break Timer event).

Select All

Selects all the events displayed on the panel.

Find...

Opens the Find and Replace dialog box with selecting [Find in Files] tab.

Replace...

Opens the Find and Replace dialog box with selecting [Replace in Files] tab.

[Context menu]

Enable Event

Enables the selected event (valid state).

Note that this item is disabled if the selected event is a valid state.

Disable Event

Disables the selected event (invalid state).

Note that this item is disabled if the selected event is an invalid state.

Delete

Deletes the selected event.

Note that it is not possible to delete the built-in events (Unconditional Trace event and Run-Break Timer event).

Select All

Selects all the events of this panel.

View Select

The following cascade menus are displayed to limit the event type to be displayed.

All of the items have been selected by default.

 

Hardware Break

Displays events related to Hardware Break.

Software Break

Displays events related to Software Break.

Timer Event

Displays events related to the timer.

Performance Measurement Event

Displays events related to performance measurement.

Trace Event

Displays events related to the trace.

Action Event

Displays events related to action events (Printf events).

Built-in Event

Displays events related to built-in events (Unconditional Trace event or Run-Break Timer event).

Timer Settings

The following cascade menus are displayed to do the settings related to the timer.

Note that this item is enabled only when a timer-related event has been selected.

 

Init Timer

Initializes the timer used by the selected event (except for Run-Break Timer).

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.

Clock

Displays the result of a selected event measured by a timer in clock units.

Init Performance Measurement

Initializes performance measurement used by the selected event.

Jump to Memory

Opens the Memory panel (Memory1) and jumps to the memory corresponding to the address where the selected eventNote is being set.

Jump to Disassemble

Opens the Disassemble panel (Disassemble1) and jumps to the disassemble results corresponding to the address where the selected eventNote is being set.

Jump to Source

Opens the Editor panel and jumps to the source line corresponding to the address where the selected eventNote is being set.

Edit Condition...

Opens one of the following dialog box to edit the selected event

-

For an action event (Printf event)
Action Events dialog box

Edit Comment

Sets to the edit mode to input comments for the selected event.

When comments are already present, all of that character string is set to a select state.

Note

Events other than Trace events, Timer Result events and built-in events (Unconditional Trace events/Run-Break Timer events) can be objects of this item.

 


Differences Information
Previous Topic
Next Topic
Table of Contents