Development Tools

2.19.7.1 Restrictions on the numbers of valid events and channels

The number of events that can be set to Valid state at the same time are subject to the following limitations.

Consequently, if enabling a new event would exceed the limit, you must first set some other event to Invalid state.

Table 2.28

Maximum Number of Enabled Events

Event Type	Debug Tool
	Full-spec emulator/E1/E20			SimulatorNote 1
	RH850G3M, RH850G3K, RH850G3MH, RH850G3KH	RH850G4MH	GTM	SimulatorNote 1
Hardware Break (after execution)	8Note 2 + 8Note 3	8Note 2 + 8Note 3	2Note 8	64
Hardware Break (before execution)	12+4Note 4, Note 5	12+4Note 4, Note 5, Note 6	-
Software Break	2000	2000	-
Trace (trace start/trace end) Timer Result (timer start/timer end) Performance Measurement (performance measurement start/performance measurement end)	8Note 2 + 8Note 3	8Note 2 + 8Note 3	-
Point Trace	8Note 3	8Note 3	2Note 8
Action (Printf)	100Note 7	100Note 7	-

"x + y": "Execution type: x" + "Access type: y"

Remark 1.

When a multi-core microcontroller is selected, the number of events are specified as follows.

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

Events can be set per core up to the upper limit on the number of events.

Software breaks can be set until the total number specified for all cores reaches the upper limit.

-	[Simulator]

Events can be set until the total number specified for all cores reaches the upper limit.

Remark 2.

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

The following restrictions apply to the number of access-type events for hardware breaks (after execution), access-type events for hardware breaks (before execution), tracing, timer measurement, performance measurement, and point tracing.

-	When a range of addresses is specified or the unit of access is specified as 8 bytes, two events are available.

-	When an unconditional trace event is enabled and data-access trace information is acquired, one access-related event is no longer available for use as other types of event since it is occupied in the acquisition of data.

Note 1.

Hardware breaks (after execution), software breaks, and performance measurement cannot be set.

Note 2.

These are execution-related events for hardware breaks (after execution), and can also be used as execution-related events for tracing, timer measurement, and performance measurement.

Note 3.

These are access-related events for hardware breaks (after execution), and can also be used as access-related events for tracing, timer measurement, performance measurement, and point tracing.

Note 4.

Four of the execution-related events for hardware breaks (before execution) can also be used as access-related events for hardware breaks (before execution).

Note 5.

A post-execution break only occurs in the following cases.

-	When the data condition is specified after selecting [Break Settings] >> [Set Read Break to] / [Set R/W Break to] from the context menu

-	When a write access of the read-modify-write instruction is detected, after selecting [Break Settings] >> [Set Write Break to] / [Set R/W Break to] from the context menu

Note 6.

Data cannot be specified.

Note 7.

Combination with Software Break events.

Note 8.

These are access-related events for hardware breaks (after execution), and can also be used as point tracing.

The following restrictions apply to the number of timer and performance measurement channels that can be set at the same time.

Table 2.29

Maximum Number of Enabled Channels

Event Type	Debug Tool
	Full-spec emulator/E1/E20			Simulator
	RH850G3M, RH850G3K, RH850G3MH, RH850G3KH	until RH850G4MH2.0	after RH850G4MH2.1	Simulator
Timer Result (timer start/timer end)	3 (for each core)	3 (for each core)	7 (common for all cores)	8 (common for all cores)
Performance Measurement (performance measurement start/performance measurement end)	4 (for each core)	4 (for each core)	8 (common for all cores)	-