Nexus Aurora Router (NAR)
Field
9–7
6
FE3
5–2
SF3
1
0
ACC
65.4.2.2
Message type filter register (NAR_TFR)
The MSP can be configured to accept or exclude messages of up to four types, as encoded
in the message TCODE field. The TCODEs which are to be filtered are programmed in the
message type filter register (NAR_TFR) as shown in the following figure. This register
should only be set in the BD NAR because partitioning is not supported in the PD NAR.
Register index: 3
31
30
R
TFI
FE0
W
Reset
0
0
15
14
R
0
FE2
W
Reset
0
0
The NAR_TFR is described in the following table.
Field
31
TFI
30
FE0
29–24
TF0
23
1880/2058
Table 1052. NAR_SFR field descriptions(Continued)
Reserved
Enable Filter 3.
0 Filter 3 disabled. SF3 ignored
1 Filter 3 enabled and contained in SF3
Source Filter 3. The message source trace ID is compared with this field. See
Section 65.5.6, Output arbitration
Reserved
OR source and type filters.
0 Match if source AND type filters match
1 Match if source OR type filters match
29
28
27
26
TF0
0
0
0
0
13
12
11
10
TF2
0
0
0
0
Figure 1115. Message type filter register (NAR_TFR)
Table 1053. NAR_TFR field descriptions
Type Filter Invert.
0 Match if message TCODE equals any of the enabled filters
1 Match if message TCODE equals none of the enabled filters
Enable Filter 0.
0 Filter 0 disabled. TF0 ignored
1 Filter 0 enabled and contained in TF0
Type Filter 0. The message TCODE is compared with this field. See
Output arbitration
for an example.
Reserved
DocID027809 Rev 4
Description
for an example.
25
24
23
22
0
FE1
0
0
0
0
9
8
7
6
0
FE3
0
0
0
0
Description
21
20
19
18
TF1
0
0
0
0
5
4
3
2
TF3
0
0
0
0
Section 65.5.6,
RM0400
17
16
0
0
1
0
0
0
Need help?
Do you have a question about the SPC572L series and is the answer not in the manual?
Questions and answers