6. Event Management > Event Notification
CPS-1848 User Manual
148
June 2, 2014
Formal Status
This document is confidential and is subject to an NDA.
Integrated Device Technology
6.3.9
Port-Write Formats, Programming Model, and Generation
Port-write commands are signaled by the S-RIO port when an error is detected and captured either as defined in the
RapidIO Specification (Rev. 2.1), Part 8, or as detected and captured using the IDT implementation-specific definition for errors
that are not defined in Part 8 (such as lane-level errors). Two types of port-write packets can be generated by the CPS-1848:
• Standard port-write (see
) – This packet has a 16-byte payload. Its format is defined in RapidIO Specification
(Rev. 2.1), Part 8.
) – This packet has an 8-byte payload. Its format is IDT specific.
6.3.9.1
Port-Write Programming Model
The registers listed in
control the physical and transport layer fields of Standard and IDT port-writes. These fields
determine where port-writes are sent and their priority in the system. These fields must be configured before port-writes can be
successfully received.
The type of port-write format that has been received can be determined based on the length of the
port-write payload. For endpoints that do not capture the length of a received port-write payload, IDT
recommends that devices generating Standard port-writes set at least one of the most significant two
bits of the RapidIO standard
, as these bits are never set in an IDT port-write.
Table 54: Port-Write Programming Model Registers and Fields
Register
Field Name
Discussion
DESTID_MSB, DESTID
destID for the endpoint(s) that will receive the port-writes.
Note that port-writes can be multicast.
LARGE
0 = 8-bit destIDs are used
1 = 16-bit destIDs are used
SRCID_MSB, SRCID
This value is reserved in the port-write. If the port-write
receiver can capture the sourceID field of the port-write,
this field can transfer static information in the port write.
Otherwise, leave as 0.
PRIO
RapidIO physical layer priority for all port-writes.
Recommend that this be set to 0b11 (Priority 3)
CRF
Critical Request Flow indicator for all port-writes.
Recommend that this be set to 1.
Note: A port-write packet does not support per-port route table.