2. RapidIO Ports > Packet Trace and Filtering
CPS-1848 User Manual
54
June 2, 2014
Formal Status
This document is confidential and is subject to an NDA.
Integrated Device Technology
Figure 9: Trace Function within a Port
From an application perspective, the support for comparison over the first 160 bits of the packet is to ensure that the trace
function can cover the largest RapidIO header (including those using extended addressing) plus at least the first 32 bits of the
payload. This implementation is flexible across the first 160 bits of the packet and ensures that the following parameters
(among others) can be used as trace criteria:
• The header’s ftype field (4 bits)
• The header’s destID field (8 or 16 bits)
• The header’s mbox field (up to 8 bits)
• The first 32 bits of the packet payload (32 bits)
2.9.1.2
Trace Port Features
Each S-RIO port supports a trace port functionality. The user can define which output port is enabled for the Trace function. For
a specific device, all packets that match the Trace criteria from all trace-enabled inputs are routed to the same configured,
trace-enabled output port.
Note that the device supports configurations where the trace port and the output port referenced by a received packet are
defined to be the same port. In the case where there is a trace match and the packet’s destID references the output port
configured as the trace port, the packet will be forwarded only once regardless of the packet type.
If an S-RIO port detects an error in a received packet, the packet will not be forwarded to the trace port;
however, it can still be reported as a trace match.
0
159
First 160 bits of packet
0
159
Programmable Comparison 0
Mask 0
Mask 1
Programmable Comparison 1
Mask 2
Mask 3
Programmable Comparison 2
Programmable Comparison 3
Trigger
0
159
0
159
0
159
0
159
0
159
0
159
0
159
RapidIO
packet