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

IDT 80KSBR200
Notes
Advanced Datasheet*
4.4 Idles
When the S-Port is not sending packet data, 8B/10B Idles shall be transmitted, along with any link maintenance
packets needed per the protocol spec. Idles received, will be ignored and not result in data being stored within the SerB.
4.5 Case Scenarios
The "Case Scenario" is method used to generate the sRIO packet headers when data is transmitted out of the SerB.
The case scenario is established to route every sRIO data packet that is originated by the SerB. A single queue may have
data intended for several different destinations as defined by the case scenario.
The case scenario may be programmed to be any sRIO command type followed by data, allowing fairly sophisticated
command generation with little overhead. While the SerB may program any command into the case scenario, it is not guar-
anteed that the SerB is capable of fully executing more than the designated command types. The user may be able to use
this feature to extend the SerB capabilities.
The "Case Scenario Register" must be programmed before use. Every data packet that leaves the SerB must contain
an sRIO packet header. The following are the rules describing "Case Scenario".
◆ _{Case Scenario is programmed into the configuration registers.}
◆ _{Every data packet originated by the SerB must use a case scenario}
– sRIO Response packets do not use case scenarios
– sRIO Doorbells, messages, and other packets do not use case scenarios
◆ _{The queue is programmed to always select a case scenario for all data that leaves that queue.}
◆ _{The destination ID is used to route the packet to the queue.}
4.5.1 sRIO Destination IDs for queuing incoming data
The SerB itself has a device destination ID, and any incoming sRIO packets that do not contain data (e.g. configuration
register updates), should use this device destination ID. The device destination ID is further described in the configuration
registers section. It is searchable on the sRIO bus and is programmed during the sRIO "bring up".
The queue may be programmed with a destination ID in the configuration register (separate and distinct from the
device destination ID). This destination ID is not searchable and not programmed in accordance with the sRIO "bring up"
specification. Instead, the register must be programmed using the same methods as most of the other configuration regis-
ters. Any data coming over the sRIO port, carrying a destination ID that matches the destination ID for the queue will be
loaded into that queue.
The destination ID is an eight bit designation within the sRIO packet header. The destination IDs programmed in the
configuration registers are also eight bits. The programmed destination ID will be used as the source ID during sRIO trans-
mission. Figure 9 below shows the location of the destination/target ID and the source ID in a typical sRIO packet.
Figure 9 Typical sRIO Packet showing location of Source and Destination IDs
Destination IDs are the means of communication within an sRIO environment. It is required that every sRIO packet
have a destination ID and a source ID.
27 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.