M9TU Product Manual USB 3.0 - 2.5” Hard Disk Drive September 05, 2013 Rev 1.0 PMM9T-USB3.
© 2013 Seagate Technology LLC. All rights reserved. Seagate and Seagate Technology are registered trademarks of Seagate Technology LLC in the United States and/or other countries. Momentus is either a trademark or registered trademark of Seagate Technology LLC or one of its affiliated companies in the United States and/or other countries. All other trademarks or registered trademarks are the property of their respective owners.
TABLE OF CONTENTS CHAPTER 1 1.1 1.2 1.3 1.4 USER DEFINITION .............................................................................................................................. MANUAL ORGANIZATION .................................................................................................................. USB .................................................................................................................................................... REFERENCE ..........................
5.5 FIRMWARE FEATURES ..................................................................................................................... 5.5.1 Read Caching ................................................................................................................. 5.5.2 Write Caching ................................................................................................................. 5.5.3 Defect Management .................................................................................
6.3.6.3 6.3.6.3.1 6.3.6.3.2 6.3.6.3.3 6.3.6.3.4 6.3.6.3.5 6.3.6.3.6 6.3.6.3.7 6.3.6.3.8 6.3.6.3.9 6.3.6.3.10 6.3.6.3.11 6.3.6.3.12 6.3.6.4 6.3.6.4.1 6.3.6.4.2 6.3.6.4.3 6.3.6.4.4 6.3.6.4.5 6.3.6.4.6 6.3.6.4.7 6.3.6.4.8 Standard USB Device Requests ..................................................................................................... 54 Standard USB Device Request Overview ..............................................................................................
TABLE OF TABLES Table 3-1 : Specifications......................................................................................................................................... 5 Table 3-2 : Physical Specifications .......................................................................................................................... 5 Table 3-3 : Logical Configurations ...........................................................................................................................
TABLE OF FIGURES Figure 3-1 : Measurement Position ........................................................................................................................... 9 Figure 4-1 : Mechanical Dimension .......................................................................................................................... 10 Figure 4-2 : Mounting-Screw Clearance ...................................................................................................................
SCOPE CHAPTER 1 SCOPE Welcome to the Spinpoint™ M9TU USB 3.0 series of Samsung™ hard disk drive. This series of drives consists of the following models: ST2000LM005 and ST1500LM008. This chapter provides an overview of the contents of this manual, including the intended user, manual organization, terminology and conventions. In addition, it provides a list of references that might be helpful to the reader. 1.1 User Definition The Spinpoint M9TU-USB 3.
SCOPE 1.4 Reference For additional information about the USB interface, refer to: • USB 0.7: Released in November 1994 • USB 0.8: Released in December 1994 • USB 0.9: Released in April 1995 • USB 0.99: Released in August 1995 • USB 1.0 Release candidate: Released in November 1995 • USB 1.0 (1.5Mbit/s, Low-Speed and 12Mbit/s, Full-Speed): Released in January 1996 • USB 1.1: Released in September 1998 • USB 2.0 (480Mbit/s, Hi-Speed): Released in April 2000 • USB 3.
DESCRIPTION CHAPTER 2 DESCRIPTION This chapter summarizes general functions and key features of the Spinpoint M9TU-USB 3.0 hard disk drive, as well as the standards and regulations they meet. 2.1 Introduction The Samsung Spinpoint M9TU-USB 3.0 2.5 inch hard disk drive is high capacity, high performance random access storage device, which uses non-removable 2.5-inch disks as storage media. Each disk incorporates thin film metallic media technology for enhanced performance and reliability.
DESCRIPTION 2.3 Standards and Regulations The Samsung Spinpoint M9TU / Seagate® Momentus® hard disk drive depends upon its host equipment to provide power and appropriate environmental conditions to achieve optimum performance and compliance with applicable industry and governmental regulations. Special attention has been given in the areas of safety, power distribution, shielding, audible noise control, and temperature regulation. The Spinpoint M9TU-USB 3.
SPECIFICATIONS CHAPTER 3 SPECIFICATIONS This chapter gives a detail description of the physical, electrical and environmental characteristics of the Spinpoint M9TU-USB 3.0 hard disk drive. 3.1 Specification Summary Table 3-1: Specifications DESCRIPTION ST1500LM008 ST2000LM005 6 Number of R/W heads 6 Maximum BPI 2731K Flexible data TPI 480K Encoding method LDPC (low density parity check) encoding Interface USB interface (Supports USB 3.
SPECIFICATIONS 3.4 Performance Specifications Table 3-4: Performance Specifications DESCRIPTION ST1500LM008 ST2000LM005 Average Seek Time 12msec Average Latency 5.
SPECIFICATIONS 3.5 Power consumption Table 3-5: Power consumption DESCRIPTION ST1500LM008 ST2000LM005 Rated Voltage V +5 Current A 0.85 Power Consumption Spin-Up (Max) mA 750.00 Idle Watt 1.8 Seq W/R (File) Watt 3.2 Random Seek Watt 3.0 Stand by Watt 1.4 Sleep Watt 1.4 Power Requirements Tolerance For + 5V % +/- 5 Ripple, 0-30MHz mVp-p 100 Supply Rise Time msec 7-100 Supply Fall Time Sec Spinpoint M9TU-USB 3.0 Product Manual REV 1.
SPECIFICATIONS 3.6 Environmental Specifications Table 3-6: Environmental Specifications DESCRIPTION ST1500LM008 ST2000LM005 Ambient Temperature (Drive temperature measured on position of figure 3-1 should be max 65C in range of 0°C -60°C, specified operation temperature.) Operating 0 ∼ 60°C Non-operating -40 ∼ 70°C Max.
SPECIFICATIONS Figure 3-1 : Measurement Position. 3.7 Reliability Specifications Table 3-7: Reliability Specifications DESCRIPTION ST1500LM008 ST2000LM005 Recoverable Read Error Non-Recoverable Read Error <10 in 1011 bits <1 sector in 1014 bits MTBF (POH) 550,000 hours MTTR (Typical) 5 minutes Load/Unload Cycles 600,000 Ambient Spinpoint M9TU-USB 3.0 Product Manual REV 1.
INSTALLATION CHAPTER 4 INSTALLATION This chapter describes how to unpack, mount, configure and connect a Spinpoint M9TU-USB 3.0 hard disk drive. It also describes how to install the drive in systems. 4.1 Space Requirements Figure 4-1 shows the external dimensions of the drive. Figure 4-1: Mechanical Dimension 4.2 Unpacking Instructions (1) Open the shipping container of the Spinpoint M9TU-USB 3.0 hard disk drive. (2) Lift the packing assembly that contains the drive out of the shipping container.
INSTALLATION 4.3.1 Orientation Figure 4-2 shows the physical dimensions and mounting holes located on each side of the drive. The mounting holes on Spinpoint M9TU-USB 3.0 hard disk drive allow the drive to be mounted in any direction. 4.3.2 Ventilation The Spinpoint M9TU-USB 3.0 hard disk drive is designed to operate without the need of a cooling fan provided the ambient air temperature does not exceed 60ºC.
INSTALLATION 4.4 Cable Connectors 4.4.1 USB Connectivity The USB interface is connected within a point to point configuration with the USB host port. There is no master or slave relationship within the devices. Spinpoint M9TU-USB 3.0 does not require extra power. USB3.0 Micro B type applied to Spinpoint M9TU-USB 3.0. Figure 4.3 illustrates USB3.0 Micro B type connector. Figure 4-3 USB connector type Table 4-1 lists the signals connection on the USB interface.
INSTALLATION 4.6 System Startup Procedure Once the Spinpoint M9TU-USB 3.0 hard disk drive and along with the adapter board (if required) have been installed in your system, the drive can now be partitioned and formatted for operation. To set up the drive correctly, follow these instructions: 1. Power on the system. 2. Typically the system will detect a configuration change automatically. If so, then jump to step 5. 3.
INSTALLATION CHAPTER 5 DISK DRIVE OPERATION This chapter describes the operation of the Spinpoint M9TU-USB 3.0 hard disk drive functional subsystems. It is intended as a guide to the operation of the drive, rather than a detailed theory of operation. 5.1 Head / Disk Assembly (HDA) The Spinpoint M9TU-USB 3.0 hard disk drive consists of a mechanical sub-assembly and a printed circuit board assembly (PCBA), as shown in Figure 5-1. This section describes the mechanism of the drive.
INSTALLATION Figure 5-1: Exploded Mechanical View 5.1.5 Voice Coil Motor and Actuator Latch Assemblies The rotary voice coil motor consists of upper and lower permanent magnets and magnetic yokes fixed to the base casting and a rotary bonded coil on the head stack assembly. Each magnet consists of two alternating poles and is attached to the magnet yoke.
DISK DRIVE OPERATION 5.1.7 Load/Unload Mechanism Portable computer is exposed to heavy handling environment comparing with desk top computer. Load/Unload mechanism provides to protect data loss caused by head hitting to disk due to the abnormal shock and vibration in the transportation and handling. When power is shut down, head will move to parking position on the ramp. 5.2 D r i v e Electronics The Spinpoint M9TU-USB 3.
DISK DRIVE OPERATION 5.2.2.2 The Buffer Control Block The Buffer Control block manages the flow of data into and out of the buffer. Significant automation allows buffer activity to take place automatically during read/write operations between the host and the disk. This automation works together with automation within the Host Interface Control and Disk Control blocks to provide more bandwidth for the local microprocessor to perform non-data flow functions.
DISK DRIVE OPERATION 5.2.3 Read/Write IC The Read/Write IC, shown in Figure 5-2 provides read/write-processing functions for the drive. The Read/Write IC receives the Read GATE and Write GATE signals, write data, and servo AGC and gates from the Interface Controller. The Read/Write IC sends decoded read data and the read reference clock. It receives write data from the Interface Controller.
DISK DRIVE OPERATION Figure 5-2: Read/Write 88C10010 Spinpoint M9TU-USB 3.0 Product Manual REV 1.
DISK DRIVE OPERATION 5.3 S e r v o System The Servo System controls the position of the read/write heads and holds them on track during read/write operations. The Servo System also compensates for MR write/read offsets and thermal offsets between heads on different surfaces and for vibration and shock applied to the drive. The Spinpoint M9TU-USB 3.0 hard disk drive is an Embedded Sector Servo System. Positioning information is radically located in evenly spaced servo sectors on each track.
DISK DRIVE OPERATION 5.4.2 The Write Channel The signal path for the Write Channel follows the reverse order of that for the Read Channel. The host transmits data via the AT bus to the 88i1022 Interface Controller. The Buffer Controller section of the 88i1022 stores the data in the cache. Because the data is transmitted to the drive at a rate that exceeds the rate at which the drive can write data to the disk, data is stored temporarily in the cache.
DISK DRIVE OPERATION • INITIALIZE DEVICE PARAMETER (91h) • SLEEP (99h, E6h) • STANDBY IMMEDIATELY (94h, E0h) • READ BUFFER (E4h) • WRITE BUFFER (E8h) • WRITE SAME (E9h) 5.5.2 Write Caching Write caching improves both single and multi-sector write performance by reducing delays introduced by rotational latency.
USB INTERFACE AND USB COMMANDS CHAPTER 6 6.1 USB INTERFACE AND USB COMMANDS Introduction A Seagate disk drive with an Embedded USB Interface fully supports and enhances PC mass storage requirements. The Seagate USB interface conforms to the USB 2.0 and 3.0 standards in Cabling, in Physical Signals, and in Logical Programming schemes. The Seagate Embedded USB controller joins the industry premiere VLSI circuitry with ingenious programming skill that does not compromise performance or reliability.
USB INTERFACE AND USB COMMANDS 6.2.1.2 Connector To minimize end user termination problems, USB uses a “keyed connector” protocol. The physical difference in the Series “A” and “B” connectors insures proper end user connectivity. The “A” connector is the principle means of connecting USB devices directly to a host or to the downstream port of a hub. All USB devices must have the standard Series “A” connector specified in this chapter.
USB INTERFACE AND USB COMMANDS 6.2.1.2.2 Series “A” and Series “B” Receptacles Electrical and mechanical interface configuration data for Series "A" and Series "B" receptacles are shown in Figure 6-3 and Figure 6-4. Figure 6-3: USB Series “Standard - A” Receptacle Interface Figure 6-4: USB Series “Standard - B” Receptacle Interface Spinpoint M9TU-USB 3.0 Product Manual REV 1.
USB INTERFACE AND USB COMMANDS 6.2.1.2.3 Series “A” and Series “B” Plugs Electrical and mechanical interface configuration data for Series "A" and Series "B" plugs are shown in Figure 6-5 and Figure 6-6. Figure 6-5: USB Series “B” Plug Interface Figure 6-6: USB Series “B” Plug Interface Spinpoint M9TU-USB 3.0 Product Manual REV 1.
USB INTERFACE AND USB COMMANDS 6.2.1.3 Cable USB cable consists of four conductors, two power conductors, and two signal conductors. High-/full-speed cable consists of a signaling twisted pair, VBUS, GND, and an overall shield. High-/full speed cable must be marked to indicate suitability for USB usage. High-/full-speed cable may be used with either low-speed, fullspeed, or high-speed devices. When high-/full-speed cable is used with low-speed devices, the cable must meet all low-speed requirements.
USB INTERFACE AND USB COMMANDS Appendix (USB 3.0 Cable) USB 3.0 Standard –A to USB 3.0 Standard –B Cable Assembly USB 3.0 Standard –A to USB 3.0 Micro –B Cable Assembly Spinpoint M9TU-USB 3.0 Product Manual REV 1.
USB INTERFACE AND USB COMMANDS USB 3.0 Micro –A to USB 3.0 Micro –B Cable Assembly USB 3.0 Standard –A to USB 3.0 Standard –A Cable Assembly USB 3.0 Micro –A to USB 3.0 Standard – B Cable Assembly Spinpoint M9TU-USB 3.0 Product Manual REV 1.
USB INTERFACE AND USB COMMANDS 6.2.1.4.2 High-/full-speed Captive Cable Assemblies Assemblies are considered captive if they are provided with a vendor-specific connect means (hardwired or custom detachable) to the peripheral. High-/full-speed hardwired cable assemblies may be used with either high-speed, full-speed, or low-speed devices. When using a high-/full-speed hardwired cable on a lowspeed device, the cable must meet all low-speed requirements.
USB INTERFACE AND USB COMMANDS 6.2.1.4.3 Low-speed Captive Cable Assemblies Assemblies are considered captive if they are provided with a vendor-specific connect means (hardwired or custom detachable) to the peripheral. Low-speed cables may only be used on low-speed devices. Figure 6-9 illustrates a low-speed hardwired cable assembly. Figure 6-9: USB Low-speed Hardwired Cable Assembly 6.2.1.4.4 Prohibited Cable Assemblies USB is optimized for ease of use.
USB INTERFACE AND USB COMMANDS Cable assembly that violates USB topology rules A cable assembly with both ends terminated in either Series “A” plugs or Series “B” receptacles. This allows two downstream ports to be directly connected. Note: This prohibition does not prevent using a USB device to provide a bridge between two USB buses. Standard detachable cables for low-speed devices Low-speed devices are prohibited from using standard detachable cables.
USB INTERFACE AND USB COMMANDS 6.2.2.2 Signaling The signaling specification for the USB is described in the following subsections. Overview of High-speed Signaling A high-speed USB connection is made through a shielded, twisted pair cable that conforms to all current USB cable specifications. Figure 6-11 depicts an example implementation which largely utilizes USB 1.1 transceiver elements and adds the new elements required for high-speed operation. High-speed operation supports signaling at 480 Mb/s.
USB INTERFACE AND USB COMMANDS The magnitude of the current source and the value of the termination resistors are controlled to specified tolerances, and together they determine the actual voltage drive levels. The DC resistance from D+ or D- to the device ground is required to be 45Ω ±10% when measured without a load, and the differential output voltage measured across the lines (in either the J or K state) must be ±400 mV ±10% when D+ and D- are terminated with precision 45Ω resistors to ground.
USB INTERFACE AND USB COMMANDS When a transceiver operating in high-speed mode transmits, the transmit current is directed into either the D+ or D- data line. A J is asserted by directing the current to the D+ line, a K by directing it to the D- line. When each of the data lines is terminated with a 45Ω resistor to the device ground, the effective load resistance on each side is 22.5Ω. Therefore, the line into which the drive current is being directed rises to 17.78 ma * 22.5Ω or 400 mV (nominal).
USB INTERFACE AND USB COMMANDS 6.2.2.6 High-speed (480Mb/s) Signaling Levels The high-speed signaling voltage specifications in Table 6-2 must be met when measuring at the connector closest to the transceiver, using precision 45Ω load resistors to the device ground as reference loads. All voltage measurements are taken with respect to the local device ground.
USB INTERFACE AND USB COMMANDS 6.2.3 Power Distribution This section describes the USB power distribution. Our Storage Device is Bus-powered hubs. 6.2.3.1 Overview The power source and sink requirements of different device classes can be simplified with the introduction of the concept of a unit load. A unit load is defined to be 100 mA. The number of unit loads a device can draw is an absolute maximum, not an average over time.
USB INTERFACE AND USB COMMANDS Figure 6-12 shows the partitioning of power based upon the maximum current draw (from upstream) of five unit loads: one unit load for the Hub Controller and the non-removable function and one unit load for each of the external downstream facing ports. If more than four external ports are required, then the hub will need to be selfpowered.
USB INTERFACE AND USB COMMANDS 6.3 Protocol Layer This chapter presents a bottom-up view of the USB protocol, starting with field and packet definitions. This is followed by a description of packet transaction formats for different transaction types. Link layer flow control and transaction level fault recovery are then covered. The chapter finishes with a discussion of retry synchronization, babble, loss of bus activity recovery, and high-speed PING protocol. 6.3.
USB INTERFACE AND USB COMMANDS 6.3.2 Common USB Packet Fields Field formats for the token, data, and handshake packets are described in the following section. Packet bit definitions are displayed in unencoded data format. The effects of NRZI coding and bit stuffing have been removed for the sake of clarity. All packets have distinct Start- and End-of-Packet delimiters. Sync All packets must start with a sync field.
USB INTERFACE AND USB COMMANDS Table 6-3: PID Types PIDs are divided into four coding groups: token, data, handshake, and special, with the first two transmitted PID bits (PID<0:1>) indicating which group. This accounts for the distribution of PID codes. 6.3.2.3 Address Fields Function endpoints are addressed using two fields: the function address field and the endpoint field. A function needs to fully decode both address and endpoint fields.
USB INTERFACE AND USB COMMANDS 6.3.2.4 Endpoint Fields An additional four-bit endpoint (ENDP) field, shown in Figure 6-16, permits more flexible addressing of functions in which more than one endpoint is required. Except for endpoint address zero, endpoint numbers are function-specific. The endpoint field is defined for IN, SETUP, and OUT tokens and the PING special token. All functions must support a control pipe at endpoint number zero (the Default Control Pipe).
USB INTERFACE AND USB COMMANDS 6.3.3 Packet Format This section shows packet formats for token, data, and handshake packets. Fields within a packet are displayed in these figures in the order in which bits are shifted out onto the bus. 6.3.3.1 Token Packet Figure 6-18 shows the field formats for a token packet. A token consists of a PID, specifying either IN, OUT, or SETUP packet type and ADDR and ENDP fields. The PING special token packet also has the same fields as a token packet.
USB INTERFACE AND USB COMMANDS The STALL handshake is used by a device in one of two distinct occasions. The first case, known as “functional stall,” is when the Halt feature associated with the endpoint is set. A special case of the functional stall is the “commanded stall.” Commanded stall occurs when the host explicitly sets the endpoint’s Halt feature.
USB INTERFACE AND USB COMMANDS 6.3.
USB INTERFACE AND USB COMMANDS 6.3.5.1 Control Transaction Control transfers are typically used for command and status operations. They are essential to set up a USB device with all enumeration functions being performed using control transfers. They are typically bursty, random packets which are initiated by the host and use best effort delivery.
USB INTERFACE AND USB COMMANDS Figure 6-24: Data Stage Status Stage reports the status of the overall request and this once again varies due to direction of transfer. Status reporting is always performed by the function. • IN (Figure 6-25): If the host sent IN token(s) during the data stage to receive data, then the host must acknowledge the successful receipt of this data. This is done by the host sending an OUT token followed by a zero length data packet.
USB INTERFACE AND USB COMMANDS 6.3.5.2 Bulk Transaction Bulk transfers can be used for large bursty data. Such examples could include a print-job sent to a printer or an image generated from a scanner. Bulk transfers provide error correction in the form of a CRC16 field on the data payload and error detection/re-transmission mechanisms ensuring data is transmitted and received without error. Bulk transfers will use spare un-allocated bandwidth on the bus after all other transactions have been allocated.
USB INTERFACE AND USB COMMANDS Figure 6-28: Bulk Transaction Diagram The Figure 6-28 above diagram shows the format of a bulk IN and OUT transaction. • IN: When the host is ready to receive bulk data it issues an IN Token. If the function receives the IN token with an error, it ignores the packet.
USB INTERFACE AND USB COMMANDS 6.3.6 USB Device Generic Framework This chapter describes the common attributes and operations of the protocol layer of a USB device. 6.3.6.1 USB Device State A USB device has several possible states. Some of these states are visible to the USB and the host, while others are internal to the USB device. This section describes those states. This section describes USB device states that are externally visible (see Figure 6-29). Table 6-4 summarizes the visible device states.
USB INTERFACE AND USB COMMANDS Table 6-4: Visible Device States 6.3.6.1.1 Attached A USB device may be attached or detached from the USB. The state of a USB device when it is detached from the USB is not defined by this specification. This specification only addresses required operations and attributes once the device is attached. 6.3.6.1.2 Powered USB devices may obtain power from an external source and/or from the USB through the hub to which they are attached.
USB INTERFACE AND USB COMMANDS 100 mA, then if the device switches to being bus-powered, it must return to the Address state. Self-powered hubs that use VBUS to power the Hub Controller are allowed to remain in the Configured state if local power is lost. A hub port must be powered in order to detect port status changes, including attach and detach.
USB INTERFACE AND USB COMMANDS Figure 6-30: Enumeration 1. The hub to which the USB device is now attached informs the host of the event via a reply on its status change pipe. At this point, the USB device is in the Powered state and the port to which it is attached is disabled. 2. The host determines the exact nature of the change by querying the hub. 3.
USB INTERFACE AND USB COMMANDS 6.3.6.2.3 Configuration A USB device must be configured before its function(s) may be used. The host is responsible for configuring a USB device. The host typically requests configuration information from the USB device to determine the device’s capabilities. As part of the configuration process, the host sets the device configuration and, where necessary, selects the appropriate alternate settings for the interfaces.
USB INTERFACE AND USB COMMANDS made using control transfers. The request and the request’s parameters are sent to the device in the Setup packet. The host is responsible for establishing the values passed in the fields listed in Table 6-5. Every Setup packet has eight bytes. Table 6-5: Format of Setup Data ■ bmRequestType This bitmapped field identifies the characteristics of the specific request.
USB INTERFACE AND USB COMMANDS The Direction bit is set to zero to indicate the OUT endpoint with the specified Endpoint Number and to one to indicate the IN endpoint. In the case of a control pipe, the request should have the Direction bit set to zero but the device may accept either value of the Direction bit. Figure 6-32 shows the format of wIndex when it is used to specify an interface.
USB INTERFACE AND USB COMMANDS Table 6-7: Standard Request Codes Table 6-8: Descriptor Types Table 6-9 : Standard Feature Selectors Feature selectors are used when enabling or setting features, such as remote wakeup, specific to a device, interface, or endpoint. The values for the feature selectors are given in Table 6-9. If an unsupported or invalid request is made to a USB device, the device responds by returning STALL in the Data or Status stage of the request.
USB INTERFACE AND USB COMMANDS 6.3.6.3.3 Get Configuration (Request Code 8) This request returns the current device configuration value. If the returned value is zero, the device is not configured. If wValue, wIndex, or wLength are not as specified above, then the device behavior is not specified. Default state: Device behavior when this request is received while the device is in the Default state is not specified. Address state: The value zero must be returned.
USB INTERFACE AND USB COMMANDS Some USB devices have configurations with interfaces that have mutually exclusive settings. This request allows the host to determine the currently selected alternate setting. If wValue or wLength are not as specified above, then the device behavior is not specified. If the interface specified does not exist, then the device responds with a Request Error. Default state: Device behavior when this request is received while the device is in the Default state is not specified.
USB INTERFACE AND USB COMMANDS A GetStatus() request to an endpoint returns the information shown in Figure 6-35. Figure 6-35: Information Returned by a GetStatus() Request to an Endpoint The Halt feature is required to be implemented for all interrupt and bulk endpoint types. If the endpoint is currently halted, then the Halt feature is set to one. Otherwise, the Halt feature is reset to zero. The Halt feature may optionally be set with the SetFeature(ENDPOINT_HALT) request.
USB INTERFACE AND USB COMMANDS The lower byte of the wValue field specifies the desired configuration. This configuration value must be zero or match a configuration value from a configuration descriptor. If the configuration value is zero, the device is placed in its Address state. The upper byte of the wValue field is reserved. If wIndex, wLength, or the upper byte of wValue is non-zero, then the behavior of this request is not specified.
USB INTERFACE AND USB COMMANDS 6.3.6.3.9 Set Descriptor (Request Code 7) This request is optional and may be used to update existing descriptors or new descriptors may be added. The wValue field specifies the descriptor type in the high byte (refer to Table 6-8) and the descriptor index in the low byte. The descriptor index is used to select a specific descriptor (only for configuration and string descriptors) when several descriptors of the same type are implemented in a device.
USB INTERFACE AND USB COMMANDS Table 6-10: Test Mode Selectors 6.3.6.3.11 Set Interface (Request Code 11) This request allows the host to select an alternate setting for the specified interface. Some USB devices have configurations with interfaces that have mutually exclusive settings. This request allows the host to select the desired alternate setting. If a device only supports a default setting for the specified interface, then a STALL may be returned in the Status stage of the request.
USB INTERFACE AND USB COMMANDS 6.3.6.4 Standard USB Descriptor The standard descriptors defined in this specification may only be modified or extended by revision of the Universal Serial Bus Specification. Note: An extension to the USB 1.0 standard endpoint descriptor has been published in Device Class Specification for Audio Devices Revision 1.0. This is the only extension defined outside USB Specification that is allowed.
USB INTERFACE AND USB COMMANDS Table 6-11: Standard Device Descriptor Spinpoint M9TU-USB 3.0 Product Manual REV 1.
USB INTERFACE AND USB COMMANDS 6.3.6.4.3 Device Qualifier Descriptor The device_qualifier descriptor describes information about a high-speed capable device that would change if the device were operating at the other speed. For example, if the device is currently operating at full-speed, the device_qualifier returns information about how it would operate at high-speed and vice-versa. Table 6-12 shows the fields of the device_qualifier descriptor.
USB INTERFACE AND USB COMMANDS Table 6-13: Standard Configuration Descriptor Spinpoint M9TU-USB 3.0 Product Manual REV 1.
USB INTERFACE AND USB COMMANDS 6.3.6.4.5 Other_Speed_Configuration_ Descriptor The other_speed_configuration descriptor shown in Table 6-14 describes a configuration of a highspeed capable device if it were operating at its other possible speed. The structure of the other_speed_configuration is identical to a configuration descriptor. Table 6-14: Other Speed Configuration Descriptor The host accesses this descriptor using the GetDescriptor() request.
USB INTERFACE AND USB COMMANDS Table 6-15: Standard Interface Descriptor Spinpoint M9TU-USB 3.0 Product Manual REV 1.
USB INTERFACE AND USB COMMANDS 6.3.6.4.7 Endpoint Descriptor Each endpoint used for an interface has its own descriptor. This descriptor contains the information required by the host to determine the bandwidth requirements of each endpoint. An endpoint descriptor is always returned as part of the configuration information returned by a GetDescriptor(Configuration) request. An endpoint descriptor cannot be directly accessed with a GetDescriptor() or SetDescriptor() request.
USB INTERFACE AND USB COMMANDS The bmAttributes field provides information about the endpoint’s Transfer Type (bits 1..0) and Synchronization Type (bits 3..2). In addition, the Usage Type bit (bits 5..4) indicate whether this is an endpoint used for normal data transfers (bits 5..4=00B), whether it is used to convey explicit feedback information for one or more data endpoints (bits 5..
USB INTERFACE AND USB COMMANDS Table 6-17: Allowed wMaxPacketSize Values for Different Numbers of Transaction per Microframe For high-speed bulk and control OUT endpoints, the bInterval field is only used for compliance purposes; the host controller is not required to change its behavior based on the value in this field. 6.3.6.4.8 String Descriptor String descriptors are optional.
USB INTERFACE AND USB COMMANDS 6.4 Bulk-Only Transport N2 Product transfer data by USB Mass Storage Class Bulk Only Transport Specification. 6.4.1 Functional Characteristics 6.4.1.1 Bulk-Only Mass Storage Reset (Class-Specific request) This request is used to reset the mass storage device and its associated interface. This class-specific request shall ready the device for the next CBW from the host. The host shall send this request via the default pipe to the device.
USB INTERFACE AND USB COMMANDS 6.4.2 Standard Descriptors The device shall support the following standard USB descriptors: • Device. Each USB device has one device descriptor (per USB Specification). • Configuration. Each USB device has one default configuration descriptor, which supports at least one interface. • Interface. The device shall support at least one interface, known herein as the Bulk-Only Data Interface. Some devices may support additional interfaces, to provide other capabilities.
USB INTERFACE AND USB COMMANDS 6.4.2.2 Configuration Descriptor (Table 6-22) Table 6-22: Bulk Only Transport Configuration Descriptor 6.4.2.3 Interface Descriptor The device shall support at least one interface, known herein as the Bulk-Only Data Interface. The Bulk-Only Data Interface uses three endpoints. Composite mass storage devices may support additional interfaces, to provide other features such as audio or video capabilities. This specification does not define such interfaces.
USB INTERFACE AND USB COMMANDS 6.4.2.4 Endpoint Descriptor The device shall support at least three endpoints: Control, Bulk-In and Bulk-Out. Each USB device defines a Control endpoint (Endpoint 0). This is the default endpoint and does not require a descriptor. ■ Bulk-In Endpoint The Bulk-In endpoint is used for transferring data and status from the device to the host.
USB INTERFACE AND USB COMMANDS 6.4.3 Protocol (Command/Data/Status) Figure 6-36 - Command/Data/Status Flow shows the flow for Command Transport, Data-In, Data-Out and Status Transport. The following sections define Command and Status Transport. Figure 6-37 - Status Transport Flow shows a detailed diagram of Status Transport. The following sections outline the various conditions for host/device communication, possible errors, and recovery procedures.
USB INTERFACE AND USB COMMANDS 6.4.3.1 Command Block Wrapper (CBW) The CBW (Table 6-26) shall start on a packet boundary and shall end as a short packet with exactly 31 (1Fh) bytes transferred. Fields appear aligned to byte offsets equal to a multiple of their byte size. All subsequent data and the CSW shall start at a new packet boundary. All CBW transfers shall be ordered with the LSB (byte 0) first (little endian). Refer to the USB Specification Terms and Abbreviations for clarification.
USB INTERFACE AND USB COMMANDS 6.4.3.2 Command Status Wrapper (CSW) The CSW (Table 6-27) shall start on a packet boundary and shall end as a short packet with exactly 13 (0Dh) bytes transferred. Fields appear aligned to byte offsets equal to a multiple of their byte size. All CSW transfers shall be ordered with the LSB (byte 0) first (little endian). Refer to the USB Specification Terms and Abbreviations for clarification.
USB INTERFACE AND USB COMMANDS 6.4.3.3.2 Data Transport All data transport shall begin on a packet boundary. The host shall attempt to transfer the exact number of bytes to or from the device as specified by the dCBWDataTransferLength and the Direction bit. The device shall respond as specified in 6 - Host/Device Data Transfers.
USB INTERFACE AND USB COMMANDS 6.4.4.3 Valid and Meaningful CSW The device generally communicates the results of its attempt to satisfy the host’s request through the CSW. The host performs two verifications on every CSW received. First, the host verifies that what was received is a valid CSW Next, the host determines if the data within the CSW is meaningful.
USB INTERFACE AND USB COMMANDS 6.5 UFI Command Set N2 Product doesn’t Support full of UFI Command. Support Command will explain in this chapter. 6.5.1 Overview A UFI Device is a removable-media mass storage subsystem, which connects to a Host computer via its Universal Serial Bus (USB) port. The Host and UFI Device communicate by exchanging Command Blocks, data, and status information as defined by this specification. 6.5.1.
USB INTERFACE AND USB COMMANDS 6.5.1.2 UFI Command Set Overview UFI commands (Table 6-29) are packets or command data blocks issued by the host to the UFI device. Each command block is 12-bytes in length. The format of each command block is based on SFF-8070i and SCSI-2. Some command blocks require extra parameters or CPU data. These are sent to the UFI device on the host bulk out endpoint, as defined by the transport specification. Some command blocks request data be sent from the UFI device to the host.
USB INTERFACE AND USB COMMANDS 6.5.2 INQUIRY Command (12h) The INQUIRY command (Table 6-30) requests that information regarding parameters of the UFI device itself be sent to the host. It is used by a driver on the host to ask the configuration of the UFI device, typically after power-on or hardware reset. Table 6-30: INQUIRY Command The EVPD (Enable Vital Product Data) is set to zero. The Logical Unit Number field specifies the logical unit (0~7) for which Inquiry data should be returned.
USB INTERFACE AND USB COMMANDS RMB: Removable Media Bit: this shall be set to one to indicate removable media. ISO/ECMA: These fields shall be zero for the UFI device. ANSI Version: must contain a zero to comply with this version of the Specification. Response Data Format: a value of 01h shall be used for UFI device The Additional Length field shall specify the length in bytes of the parameters.
USB INTERFACE AND USB COMMANDS RelAdr: This bit should be set to zero. Logical Block Address should be set to zero. PMI: This bit should be set to zero. If the UFI device recognizes the formatted medium, the UFI device returns a READ CAPACITY Data (Table 6-34) to the host on the Bulk In endpoint. The UFI device sets the sense key to NO SENSE if the command block passed. Table 6-34: READ CAPACITY Data The Last Logical Block Address field holds the last valid LBA for use with media access commands.
USB INTERFACE AND USB COMMANDS 6.5.5.1 Capacity List Upon receipt of this command block, the UFI device returns a Capacity List (Table 6-36) to the host on the Bulk In endpoint. - No media in FDU: Capacity List Header + Maximum Capacity Header - Media in FDU: Capacity List Header + Current Capacity Header + Formattable Capacity Descriptors Table 6-36: Capacity List The Capacity List Header (Table 6-37) gives the length of the descriptor data to follow.
USB INTERFACE AND USB COMMANDS Table 6-39: Descriptor Code Definition Table 6-40: Formattable Capacity Descriptor The Number of Blocks field indicates the maximum (or fixed) number of addressable blocks for the given capacity descriptor. The Block Length specifies the length in bytes of each logical block for the given capacity descriptor. 6.5.6 WRITE (10) Command (2Ah) The WRITE (10) command (Table 6-41) requests that the UFI device write the data transferred by the host to the medium.
MAINTENANCE CHAPTER 7 7.1 MAINTENANCE General Information Seagate's Spinpoint M9TU-USB 3.0 hard disk drive achieves high reliability through their mechanical design and extensive use of microelectronics. Their design allows fast, easy sub-assembly r e p l a c e m e n t w i t h o u t adjustments, greatly reducing the amount of downtime required for unscheduled repairs. 7.
MAINTENANCE Fig. 7-1: HDD handling guide -Please handle HDD by side surfaces! Fig. 7-2: HDD handling guide -Do not Touch Cover and PCB! Fig. 7-3: HDD handling guide -Do Not Stack! Spinpoint M9TU-USB 3.0 Product Manual REV 1.
MAINTENANCE Fig. 7-4: HDD handling guide - Prevent Shocks! 7.3 Service and Repair To determine the warranty for a specific drive, use a web browser to access the following web page http://samsunghdd.seagate.com/, then click on the Warranty Tab and follow the steps outlined. You will be asked to provide the drive serial number, model number (or part number) and country of purchase. The system will display the warranty information for your drive. Spinpoint M9TU-USB 3.0 Product Manual REV 1.
