Specifications

SATA-IO Confidential 86
2.18.15.1. Expected Behavior
When a port multiplier receives a FIS from the host system directed to a device port that is beyond the range of
supported port numbers, it shall not respond with either R_OK or R_ERR. Instead, it shall send a SYNC primitive to
the host system, terminating the FIS transfer.
This test does not apply to a port multiplier that supports the full range of allowable device port numbers, 0-14.
There is no standard way for host software to know that the HBA has received SYNC from the PM. I expect the usual
result will be a command timeout in host software. (Verify this on real hardware.)
Measurement Requirements
For setup consistency, issue Soft Reset to Port F of the port multiplier before starting the test sequence.
Install a SATA analyzer on the link between HBA and port multiplier. Install a drive on the highest numbered device
port and initialize the interface. Verify that the drive can execute an IDENTIFY DEVICE command correctly.
Issue an IDENTIFY DEVICE command to a port address greater than the highest numbered port on the PM. Observe
whether the command completes successfully. Capture a trace of the interface activity when the command is issued.
Pass/Fail Criteria
• Verify that the command did not complete successfully. Verify by examining the interface trace from the
analyzer that the PM responded to the command FIS with one or more SYNC primitives.
2.18.16. PM-16 : Test For PM-aware Host
See section 13.13.3.1 of Serial ATA Revision 2.6.
Port Multiplier aware software checks the host’s SStatus register to determine if a device is
connected to the port. If a device is connected to the port, the host then issues a software reset
to the control port. If the Port Multiplier signature is returned, then a Port Multiplier is attached to
the port. Then the host proceeds with enumeration of devices on Port Multiplier ports as detailed
in section 13.13.4.2.
2.18.16.1. Expected Behavior
Following system power on, a PM-aware host will issue Soft Reset to the control port address, Fh, and wait for the
specific signature FIS of a port multiplier. This is in contrast to a non-PM-aware host, which is not
aware of PM port address Fh and which waits for a signature FIS from a direct attached device.
After determining that a port multiplier is attached, the PM-aware host should enumerate the PM ports and discover
any attached devices. The exact sequence of events on the host port after the PM signature FIS is implementation
specific and is not detailed here.
Measurement Requirements.
With a SATA analyzer connected between the designated HBA port and the PM host port, program the analyzer to
capture all FIS transfers. Start the analyzer.
Power up the host system and the port multiplier. If the port multiplier is powered by a separate power supply, then
power up the port multiplier before turning on the host system being tested.
After the host OS is fully loaded and initialized, stop the analyzer.
Pass/Fail Criteria
• In order for the host to be designated PM-aware, the trace must show a soft reset addresses to the control
port of the port multiplier.
• A soft reset consists of two consecutive Register Host -> Device FISes sent by the host. The first must have
the C bit = 0 and Control register bit 2 = 1. The second must have the C bit = 0 and Control register bit 2 = 0.
In both FIS’s the PM Port field must = Fh.