Table of Contents
Advertisement
1.4.3.5
CLOSE
A CLOSE primitive is used to close a connection. When a CLOSE primitive is
sent, the close timer (1 ms) is started. If a CLOSE primitive is not received
within 1 ms of sending CLOSE primitive, the BREAK primitive is sent. The
recipient must send a CLOSE primitive within 1 ms of receiving a CLOSE
primitive.
Drives support only the CLOSE (NORMAL) primitive as a CLOSE primitive,
while the CLOSE (CLEAR AFFILIATION), CLOSE (RESERVED 0), and
CLOSE (RESERVED 1) primitives are ignored.
1.4.3.6
EOAF (End of address frame)
EOAF specifies the end of an address frame.
1.4.3.7
ERROR
ERROR should be sent by an expander device when it is forwarding dwords from
a SAS physical link or SATA physical link to a SAS physical link and it receives
an invalid dword or an ERROR.
When a drive receives an ERROR primitive, the drive discards it. When a
received address frame contains the ERROR primitive, the whole address frame is
discarded even if CRC is correct.
When a drive receives an SSP frame containing the ERROR primitive, the drive
discards the whole SSP frame even if CRC is correct, and sends the NAK
primitive.
1.4.3.8
HARD_RESET
HARD_RESET is used to force a phy to generate a hard reset to its port. This
primitive is only valid after the phy reset sequence without an intervening
identification sequence and shall be ignored at other times.
Upon receipt of the HARD_RESET primitive, a drive clears all the commands it
is currently holding.
In a dual port drive, the HARD_RESET primitive received at one port (e.g., at
port A) affects the other port (e.g., at port B).
Meanwhile, as can be expected, a link reset sequence that occurs at one port (e.g.,
port A) does not affect the other port (e.g., port B).
C141-C009
1.4 Link layer
1-29
Advertisement
Table of Contents
