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

IDT 80KSBR200
Advanced Datasheet*
Notes
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
AckID
rsvd CRF prio
tt
fType
Target ID
Source ID
transaction
rdsize/wrsize
srcTID
Hop Count
config_offset
config_offset
wdptr rsrv
Payload
Payload
CRC
Figure 7 sRIO Maintenance Request Packet (Type 8)
◆ _{AckID = Transaction ID for link acknowledgements}
◆ _{CRF = Critical Request Flow, not used in SerB}
◆ _{prio = Packet priority}
◆ _{tt = Transaction type, 00 = 8 bits, 01 = 16 bits}
◆ _{fType = 1000, for a type 8 maintenance packet}
◆ _{Target ID = the destination ID of the SerB, is 16 bits if tt = 01}
◆ _{Source ID = the ID of the sending device, is 16 bits if tt = 01}
◆ _{transaction = specifies whether request is read, write and/or response, see sect 4.1.10 of sRIO Input/Output}
Logical spec
◆ _{rdsize/wrsize = see sect 4.1.2 of sRIO Input/Output Logical spec}
◆ _{srcTID = the Transaction ID for sRIO end to end retransmissions}
◆ _{Hop Count = Not important to an end point.}
◆ _{config_offset = the configuration register address}
◆ _{wdptr = part of rdsize/wrsize}
◆ _{Payload = 32 bits of data destined to be written to the designated register}
◆ _{CRC = 16 bits of CRC}
The sRIO maintenance request packet will receive a response packet as shown in Figure 8. The response will be
returned to the sender of the request and include a "status" of the request. The status is identified in section 4.1.10 of the
sRIO input/Output Logical spec. The SerB shall observe that 0000b indicates "done" and 0111b indicates "error".
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
AckID
rsvd CRF prio
tt
fType
Target ID
Source ID
transaction
rdsize/wrsize
srcTID
Hop Count
config_offset
config_offset
wdptr rsrv
Payload
Payload
CRC
Figure 8 sRIO Maintenance Response Packet (Type 8)
Other than the status field of the packet, the fields serve the same function as the request packet or are unused. Upon
a read request, the Payload is the data content of the selected configuration register. When initiating a Maintenance
Response Packet, the hop count will be set to 0xFF.
The fields of the response packet are as follows:
◆ _{AckID = Transaction ID for link acknowledgements}
◆ _{CRF = The incoming CRF is returned in the response}
◆ _{prio = Increased to one higher than the request}
◆ _{tt = Same as the request}
◆ _{fType = Same as the request (8)}
◆ _{Target ID = The Source ID of the request (a simple swap)}
◆ _{Source ID = The Target ID of the request (a simple swap)}
◆ _{transaction = specifies whether request is read, write and/or response, see sect 4.1.10 of sRIO Input/Output}
Logical spec
◆ _{status = 0000b means done, 0111b means error}
23 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.