Allowable number of valid events

2.17.7.1 Allowable number of valid events

The number of events that can be set as valid (or Enabled) events at the same time are subject to the following limitations.

Therefore, if this limit is exceeded when you set one or more new valid events, some of the events that are already set need to be Disabled before you can set a new one.

Table 2.21

Allowable Number of Valid Events [RX600, RX700 Series]

Type of event	Debug tool
Type of event	E1(Serial)/E1(JTAG) E20(Serial)/E20(JTAG) EZ Emulator	Simulator
Software break	256Note9	0
Hardware break (execution-related: before execution)	8Note1	1024Note8
Break event (execution-related: after execution)	8Note1	0
Break event (access-related: Read, Write, Read/Write)	4Note1 Note3	1024
Combination break	8+4Note1 Note2 Note5	0
Trace (trace start, trace end)	8+4Note1 Note2 Note6	256
Point trace	4Note1 Note3	256
Timer result (timer start, timer end)	8+4Note1 Note2 Note6	1Note7
Action (Printf event)	256Note9	1024Note8
Action (Interrupt event)	0	256

Table 2.22

Allowable Number of Valid Events [RX200 Series]

Type of event	Debug tool
Type of event	E1(Serial) E20(Serial) EZ Emulator	Simulator
Software break	256Note9	0
Hardware break (execution-related: before execution)	4Note4	1024Note8
Break event (execution-related: after execution)	4Note4	0
Break event (access-related: Read, Write, Read/Write)	2Note4	1024
Combination break	4+2Note4	0
Trace (trace start, trace end)	4+2Note4 Note5 Note6	256
Point trace	4Note4	256
Timer result (timer start, timer end)	4+2Note4 Note6	1Note7
Action (Printf event)	256Note9	1024Note8
Action (Interrupt event)	0	256

Table 2.23

Allowable Number of Valid Events [RX100 Series]

Type of event	Debug tool
Type of event	E1(Serial) E20(Serial) EZ Emulator	Simulator
Software break	256Note9	0
Hardware break (execution-related: before execution)	4Note4	1024Note8
Break event (execution-related: after execution)	4Note4	0
Break event (access-related: Read, Write, Read/Write)	2Note4	1024
Combination break	4+2Note4	0
Trace (trace start, trace end)	4+2Note4 Note5 Note6	256
Point trace	4Note4	256
Timer result (timer start, timer end)	0	1Note7
Action (Printf event)	256Note9	1024Note8
Action (Interrupt event)	0	256

Note 1.

There are 8 execution-related events and 4 access-related events, which are shared by multiple functions.

Note 2.

For an event combination, up to 8 events can be set.

Note 3.

[E20(JTAG)]
The trace function and the real-time RAM monitor function (RRM function) in part are usable exclusively of each other. Therefore, while the RRM function is in use, the point trace cannot be used. Also, the access event is usable only when the RRM block has free space.

Note 4.

There are 4 execution-related events and 2 access-related events, which are shared by multiple functions.

Note 5.

If the combination condition for the combination break is Sequential, the maximum number of events that can be set differs with each microcontroller used, as shown below.

-	[RX600, RX700 Series] 7 events + reset event (R event)

-	[RX100, RX200 Series] 3 events + reset event (R event)

Note 6.

If the maximum number of execution-related events have already been used as trace start/trace end events or timer start/timer end events, [Go to Here] in the context menu of the Editor panel or Disassemble panel is not usable. Also, it is not possible to run the program to the address of a specified symbol after the CPU has been reset.

Note 7.

For each of timer start and end events, only a single execution-related event or access-related event can be specified.

Note 8.

Hardware breaks (execution-related: before execution) and actions (Printf events) are shared by multiple functions.

Note 9.

Software breaks and actions (Printf events) are shared by multiple functions.