Everything
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

E1(Serial)/E1(JTAG)
E20(Serial)/E20(JTAG)

Simulator

Software break

256Note1

0

Hardware break (execution-related: before execution)

8Note2

1024Note4

Break event (execution-related: after execution)

8Note2

0

Break event (access-related: Read, Write, Read/Write)

4Note2 Note5

1024

Combination break

8+4Note2 Note6 Note8

0

Trace (trace start, trace end)

8+4Note2 Note6 Note8 Note9

256

Point trace

4Note2 Note5

256

Timer result (timer start, timer end)

8+4Note2 Note6 Note9

2Note10

Action (Printf event)

256Note1

1024Note4

Action (Interrupt event)

0

256

Table 2.22

Allowable Number of Valid Events [RX26T Group]

Type of event

Debug tool

E1(Serial)/E1(JTAG)
E20(Serial)/E20(JTAG)

Simulator

Software break

256Note1

0

Hardware break (execution-related: before execution)

8Note2

1024Note4

Break event (execution-related: after execution)

8Note2

0

Break event (access-related: Read, Write, Read/Write)

4Note2

1024

Combination break

8+4Note2 Note6 Note8

0

Trace (trace start, trace end)

4+2Note3 Note7 Note8 Note9

256

Point trace

2Note3

256

Timer result (timer start, timer end)

4+2Note3 Note7 Note9

1Note10

Action (Printf event)

256Note1

1024Note4

Action (Interrupt event)

0

256

Table 2.23

Allowable Number of Valid Events [RX200 Series other than RX26T Group, RX140 Group]

Type of event

Debug tool

E1(Serial)
E20(Serial)

Simulator

Software break

256Note1

0

Hardware break (execution-related: before execution)

4Note3

1024Note4

Break event (execution-related: after execution)

4Note3

0

Break event (access-related: Read, Write, Read/Write)

2Note3

1024

Combination break

4+2Note3 Note7 Note8

0

Trace (trace start, trace end)

4+2Note3 Note7 Note8 Note9

256

Point trace

2Note3

256

Timer result (timer start, timer end)

4+2Note3 Note7 Note9

2Note10

Action (Printf event)

256Note1

1024Note4

Action (Interrupt event)

0

256

Table 2.24

Allowable Number of Valid Events [RX100 Series other than RX140 Group]

Type of event

Debug tool

E1(Serial)
E20(Serial)

Simulator

Software break

256Note1

0

Hardware break (execution-related: before execution)

4Note3

1024Note4

Break event (execution-related: after execution)

4Note3

0

Break event (access-related: Read, Write, Read/Write)

2Note3

1024

Combination break

4+2Note3 Note7 Note8

0

Trace (trace start, trace end)

4+2Note3 Note7 Note8 Note9

256

Point trace

2Note3

256

Timer result (timer start, timer end)

0

2Note10

Action (Printf event)

256Note1

1024Note4

Action (Interrupt event)

0

256

Note 1.

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

Note 2.

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

Note 3.

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

Note 4.

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

Note 5.

[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 6.

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

Note 7.

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

Note 8.

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)

-

[RX26T Group]
Combination break 7 events + reset event (R event)
Trace 3 events + reset event (R event)

Note 9.

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 10.

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

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

Table 2.25

Maximum Number of Enabled Channels

Event Type

Debug tool

E1(Serial)/E1(JTAG)/E20(Serial)/E20(JTAG)

Simulator

RX600, RX700 Series

RX200 Series, RX140 Group

Timer Result

(timer start/timer end)

1~2Note

1

1

Note

For measurements using two 32-bit counters, two channels are used, and for one 64-bit, one channel is used.