Datasheet

4–4
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
spd tLabel rt tCode priority
destinationID destinationOffsetHigh
destinationOffsetLow
dataLength extended_tCode
block data
Reserved
Figure 4–5. Block-Transmit Format (Write Request)
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
spd tLabel rt tCode priority
destinationID destinationOffsetHigh
destinationOffsetLow
dataLength extended_tCode
Reserved
Figure 4–6. Block-Transmit Format (Read Request)
4.1.2.2 Block Read-Response and Write-Response Packets
The format for a block read-response packet is shown in Figure 4–7. The first quadlet contains the packet
control information. The first 16 bits of the second quadlet is the destination identifier, which is the address
of the destination or requesting node. The second quadlet also contains the response code of this
transaction. The third quadlet is reserved. The first 16 bits of the fourth quadlet contains the dataLength field.
This is the number of bytes of data in the packet. The remaining 16 bits represent the extended_tCode field.
The block data, if any, follows the extended_tCode. The format for a block write-response is shown in
Figure 4–8.
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
spd tLabel rt tCode priority
destinationID rCode
RESERVED
dataLength extended_tCode
block data
Reserved
Reserved
Figure 4–7. Block-Transmit Format (Read Response)