80KSBR200 Datasheet, PDF (20/172 Pages) Integrated Device Technology – sRIO SERIAL BUFFER FLOW-CONTROL DEVICE

IDT 80KSBR200
Notes
Advanced Datasheet*
◆ _{Any packet that is generated by the SerB that is unrelated to a particular queue (such as a link error) will use}
the device ID of the SerB as the source ID.
3.4.4 sRIO Request Packet Types (Ftype 0 - 11)
Within the sRIO specification, 16 packet types may be formed. Packet types "Type 0" through "Type 11" are Request
packet types. Packet types, "Type 12" through "Type 15" are Response packet types. Many of the packet types are
reserved.
The SerB has limited sRIO functionality, but should be able to imitate any type of command. The SerB initiates
commands through the Case Scenario. Case Scenarios have the ability to initiate any type of command by simply entering
the correct Ftype and the rest of the sRIO header as desired. The required data may be appended as needed.
The SerB fully supports only selected sRIO commands. The user needs to be aware of the limited SerB functionality,
but may be able to pass commands outside the SerB limits if the usage and expectation of the commands fits within the
limits of SerB capabilities.
Following are the sRIO commands SerB is capable of supporting:
◆ _{SWRITE (type 6)}
◆ _{CAR/CSR (type 8)}
◆ _{DOORBELLS (type 10)}
◆ _{MESSAGES (type 11) (no defined message)}
Following are the sRIO commands supported in next phase of SerB:
◆ _{NREAD (type 2)}
◆ _{NWRITE (type 5)}
◆ _{NWRITE_R (type 5)}
The packet types are described in the RapidIO Interconnect Specification, Part 1: Input/Output Logical Specification in
chapter 4. The following is a list of the packet types and the level of support the lite protocols shall offer.
Type 0 Packet Format (Implementation Defined)
Type 0 packets shall not be used on the SerB.
Type 1 Packet Format (Reserved)
Type 1 packets are not defined in the sRIO spec and shall not be used in the SerB. If received, they are simply passed
unaltered at the logical level.
Type 2 Packet Format (Request Class)
Type 2 packets are described in section 4.1.5 of the sRIO spec. Type 2 is used for NREAD and ATOMIC in standard
sRIO. The SerB does not support neither NREAD nor ATOMIC packet format.
Type 3-4 Packet Format (Reserved)
Type 3 and Type 4 packets are not defined in the sRIO spec and shall not be used in the SerB. If received, on the sRIO
port with an SerB destination ID, an error message shall be sent. When a case scenario is loaded with type 3 or 4, the type
shall be passed along with any data. No further interpretation should be needed.
Type 5 Packet Format (Write Class)
Type 5 packets are described in section 4.1.7 of the sRIO spec. Type 5 is used for NWRITE, NWRITE_R, and ATOMIC
in standard sRIO. As with Type 2 packets, the priority must be identified so it can be passed.
Type 6 Packet Format (Streaming-Write Class)
Type 6 packets are described in section 4.1.8 of the sRIO spec. Type 6 has only one function (SWRITE), which is
limited in scope with no response needed. Therefore, the entire SWRITE packet must be passed unaltered, except for the
addition of a priority designation.
The PPSc generates SWRITE packets, so the primary packet the SerB will see in PPS applications is SWRITE. The
SerB must accept SWRITE packets as they are received, because the PPS has no backpressure mechanism and a delay
in packet acceptance will mean packet loss.
20 of 172
March 19, 2007
„2005 Integrated Device Technology, Inc. All rights reserved. Advanced Datasheet for informational purposes only. Product specifications subject to change without notice.NOT AN OFFER FOR SALE The information presented herein is subject to a
Non-Disclosure Agreement (NDA) and is for planning purposes only. Nothing contained in this presentation, whether verbal or written, is intended as, or shall have the effect of, a sale or an offer for sale that creates a contractual power of acceptance.