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] |
|
|
|
|
|
|
|
Software break
|
|
|
|
Hardware break (execution-related: before execution)
|
|
|
|
Break event (execution-related: after execution)
|
|
|
|
Break event (access-related: Read, Write, Read/Write)
|
|
|
|
Combination break
|
|
|
|
Trace (trace start, trace end)
|
|
|
|
Point trace
|
|
|
|
Timer result (timer start, timer end)
|
|
|
|
Action (Printf event)
|
|
|
|
Action (Interrupt event)
|
|
|
Table 2.22 | Allowable Number of Valid Events [RX200 Series, RX140 Group] |
|
|
|
|
|
|
|
Software break
|
|
|
|
Hardware break (execution-related: before execution)
|
|
|
|
Break event (execution-related: after execution)
|
|
|
|
Break event (access-related: Read, Write, Read/Write)
|
|
|
|
Combination break
|
|
|
|
Trace (trace start, trace end)
|
|
|
|
Point trace
|
|
|
|
Timer result (timer start, timer end)
|
|
|
|
Action (Printf event)
|
|
|
|
Action (Interrupt event)
|
|
|
Table 2.23 | Allowable Number of Valid Events [RX100 Series other than RX140 Group] |
|
|
|
|
|
|
|
Software break
|
|
|
|
Hardware break (execution-related: before execution)
|
|
|
|
Break event (execution-related: after execution)
|
|
|
|
Break event (access-related: Read, Write, Read/Write)
|
|
|
|
Combination break
|
|
|
|
Trace (trace start, trace end)
|
|
|
|
Point trace
|
|
|
|
Timer result (timer start, timer end)
|
|
|
|
Action (Printf event)
|
|
|
|
Action (Interrupt event)
|
|
|
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. |
Note 10. | For an event combination, up to 4 events can be set. |
The following restrictions apply to the number of timer and performance measurement channels that can be set at the same time.
Table 2.24 | Maximum Number of Enabled Channels |
|
|
|
|
|
|
|
|
|
|
Timer Result
(timer start/timer end)
|
|
|
|
Note | For measurements using two 32-bit counters, two channels are used, and for one 64-bit, one channel is used. |