
www.ti.com
SRIO Functional Description
2.3.4.1RX Operation
As message packets are received by the RapidIO ports, the data must be written into memory while maintaining accurate state information that is needed for future processing. For instance, if a message spans multiple packets, information must be saved that allows
Figure 14. CPPI RX Scheme for RapidIO
Mailbox from
Header
input
Mailbox
|
|
|
|
|
|
Q15 | Q2 | Q1 | Q0 |
| |
|
|
|
|
|
|
Queue
Packet
Manager
nA
n+1 B
n+2 B
n+3 C
n+4 D
n+5 B
n+6 | E |
| Message |
Packet |
|
Buffer
Queues:
Descriptor
All
Dedicated |
|
|
Message |
|
|
| L2 |
|
A | Data | fer |
C | n |
|
| n+3 |
|
D | n+4 |
|
|
| |
E | n+6 |
|
null | 256B | fer |
| L2 |
|
| Data | fer |
| n+1 |
|
| n+2 |
|
| n+5 |
|
Descriptor
B
Descriptor
null | 4KB | fer |
Messages addressed to any of the 64 mailbox locations can be received on any of the RapidIO ports simultaneously. Packets are handled sequentially in order of receipt. The function of the mailbox mapper block is to direct the inbound messages to the appropriate queue and finally to the correct core. The queue mapping is programmable and must be configured after device reset. RapidIO originally supported only 4 mailboxes with 4 letters/mailbox. Letters allow concurrent message traffic between sender and receiver. However, for messages that consist of only single packets, the unused
Figure 15. Message Request Packet
n*64+64
PHY | TRA | LOG | TRA | LOG | PHY |
10 | 2 | 4 | 16 | n*64+16 | 16 |
acklD | rsv | prio | tt | ftype | destID sourcelD | msglen | ssize | letter | mbox | msgseg/xmbox | ... | CRC | |||||
5 | 3 | 2 | 2 | 4 | 8 | 8 | 4 | 4 | 2 | 2 | 4 | 64 | 64 | 64 | 64 | 16 | |
ftype | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SPRU976 | Serial RapidIO (SRIO) | 41 |