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

IDT 80KSBR200
Notes
Advanced Datasheet*
3.0 Protocol
The SerB is a packet-handling device. The SerB may be configured to require all packets to be acknowledged, and
hold all packets available for retransmission until acknowledgement is received. Incoming corrupted packets are dropped
and issues a retransmission request. The negotiation for acknowledgement, retransmission and dropping packets is
handled at the local interface level, without intervention of higher-level authorities. The SerB does not forward any packet
until it is fully received, verified, and acknowledged (if configured to verify).
3.1 SerB Packet Characteristics
3.1.1 Maximum Packet Size
The sRIO specification requires a maximum packet size of 256 bytes plus overhead. The SerB fully complies to this
specification.
3.1.2 Interface Packet Buffer Size
The sRIO specification has defined buffer sizes for the transmit and receive buffers. Included in the buffer specification
is the requirement to transmit higher priority packets first. Upon transmission failure, and retransmission, the retransmis-
sion may be held up and a higher priority packet interjected if one arrives.
3.1.3 Multicast Packets
The SerB has no special multicast capabilities. To perform a multicast, the case scenario should be set up to perform
an SWRITE function. The destination ID for the case scenario should be set to a multicast address elsewhere in the
system. The SerB shall perform a multicast by sending the SWRITE to the user designated multicast address, along with
the data.
Waterlevel multicast in the PPS application is done the same way. When the waterlevel event is triggered, the SerB
issues an SWRITE multicast packet to the PPS multicast address. The SWRITE command is generated by the case
scenario.
3.2 sRIO Specification
The SerB serial interface is a standard 1x/4x serial port with sRIO capabilities. In the PPS application, the sRIO port act
primarily as an sRIO end-point, but will work as a bus master to perform multicast operations.
All the RIO TWG documents can be found on the RapidIO Members website:
http://www.rapidio.org/apps/org/workgroup/twg/documents.php
The following documents are the final version 1.2 specifications, which can be found under the Members Library
section, version 1.3 of the specifications will replace these section files when they are approved by the Steering
Committee:
RapidIO_Spec.pdf
gsmlspec.pdf
serial.book.pdf
inter-op.pdf
errspec.pdf
errata1.pdf
fcspec.pdf
system_bringup_spec.pdf
Part I through part IV of the spec., version 1.2
Part V of the spec., version 1.2
Part VI of the spec., version 1.2
Part VII of the spec., version 1.2
Part VIII of the spec., version 1.2
Errata 1 to version 1.2 of the spec.
Part IX of the spec., version 1.0
Annex I of the spec.
The version 1.3 files are currently:
IO_logical.pdf
msg_logical.pdf
cmn_trnspt.pdf
parallel_phy.pdf
Part 1: Input/Output Logical Specification
Part 2: Message Passing Logical Specification
Part 3: Common Transport Specification
Part 4: Physical Layer 8/16 LP-LVDS Specification
15 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.