Related Manuals for Seagate M8U-Internal SpinPoint
Summary of Contents for Seagate M8U-Internal SpinPoint
- Page 1 M8U-Internal Product Manual 2.5” Hard Disk Drive May 12, 2015 Rev 3.4 PM-M8U-USB2.0-100698037 Rev. F...
- Page 2 © 2015 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. Spinpoint 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.
-
Page 3: Table Of Contents
TABLE OF CONTENTS CHAPTER 1 SCOPE ..........................1 ..........................1 EFINITION ........................1 ANUAL RGANIZATION USB ..............................2 ............................2 EFERENCE CHAPTER 2 DESCRIPTION ......................3 ..........................3 NTRODUCTION ..........................4 EATURES ......................5 TANDARDS AND EGULATIONS ......................5 ARDWARE EQUIREMENTS CHAPTER 3 SPECIFICATIONS ......................6 ........................6 PECIFICATION UMMARY .......................7 HYSICAL PECIFICATIONS ......................7 OGICAL... - Page 4 ..........................28 ERVO YSTEM ......................28 EAD AND RITE PERATIONS 5.4.1 The Read Channel......................28 5.4.2 The Write Channel ......................29 ........................29 IRMWARE EATURES 5.5.1 Read Caching .........................29 5.5.2 Write Caching .........................30 5.5.3 Defect Management ......................31 5.5.4 Automatic Defect Allocation ...................31 5.5.5 Multi-burst ECC Correction ...................31 CHAPTER 6 USB INTERFACE AND USB COMMANDS ............32 ..........................32...
- Page 5 6.3.6.1.2 Powered ..........................60 6.3.6.1.3 Default ..........................61 6.3.6.1.4 Address ...........................61 6.3.6.1.5 Configured ........................61 6.3.6.1.6 Suspended ........................61 6.3.6.1.7 Bus Enumeration ......................62 6.3.6.2 Generic USB Device Operation..................62 6.3.6.2.1 Dynamic Attachment and Removal .................62 6.3.6.2.2 Address Assignment ......................63 6.3.6.2.3 Configuration........................63 6.3.6.2.4 Data Transfer .........................63 6.3.6.2.5 Power Management ......................63 6.3.6.2.6...
- Page 6 6.4.4.3 V CSW ......................92 ALID AND EANINGFUL 6.4.4.4 D ........................93 EVICE RROR ANDLING 6.4.4.5 H ........................93 RROR ANDLING 6.4.4.6 E ..........................93 RROR LASSES 6.4.4.6.1 CBW N ......................93 ALID 6.4.4.6.2 ....................93 NTERNAL EVICE RROR 6.4.4.6.3 ..................93 EVICE ISAGREEMENTS 6.4.4.6.4 ......................93 OMMAND AILURE UFI C .........................94...
- Page 7 TABLE OF TABLES Table 3-1 : Specifications............................6 Table 3-2 : Physical Specifications ..........................7 Table 3-3 : Logical Configurations ..........................7 Table 3-4 : Performance Specifications ........................8 Table 3-5 : Power consumption ..........................9 Table 3-6 : Environmental Specifications ......................... 10 Table 3-7 : Reliability Specifications ........................
-
Page 8: Table Of Figures
TABLE OF FIGURES Figure 3-1 : Measurement Position ........................... 11 Figure 4-1 : Mechanical Dimension .......................... 13 Figure 4-2 : Mounting-Screw Clearance ........................15 Figure 4-3 : USB connector type..........................16 Figure 4-4 : USB interface ............................18 Figure 5-1 : Exploded Mechanical View ........................22 Figure 5-2 : Read/Write 88C9310 .......................... -
Page 9: Chapter 1 Scope
SCOPE CHAPTER 1 SCOPE seri es Welcome to the Spinpoint M8U-Internal of Samsung hard disk drive. This series of drives consists of the following models: ST320LM008, ST500LM016, ST750LM024, and T1000LM026. This chapter provides an overview of the contents of this manual, including the intended user, manual organization, terminology and conventions. -
Page 10: Usb
SCOPE A USB system has an asymmetric design, consisting of a host, a multitude of downstream USB ports, and multiple peripheral devices connected in a tiered-star topology. Additional USB hubs may be included in the tiers, allowing branching into a tree structure, subject to a limit of 5 levels of tiers. USB host may have multiple host controllers and each host controller may provide one or more USB ports. -
Page 11: Chapter 2 Description
DESCRIPTION CHAPTER 2 DESCRIPTION This chapter summarizes general functions and key features of the Spinpoint M8U hard disk drive, as well as the standards and regulations they meet. Introduction The Samsung Spinpoint M8U 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. -
Page 12: Key Features
DESCRIPTION Key Features Key features of the Spinpoint M8U hard disk drive includes: • Formatted capacities are 320, 500, 750 GB, 1TB • 9.5 ± 0.2 mm height form factor • 5400 RPM Class • 12 ms average seek time •... -
Page 13: Standards And Regulations
DESCRIPTION Standards and Regulations The Samsung Spinpoint M8U / 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. -
Page 14: Chapter 3 Specifications
SPECIFICATIONS CHAPTER 3 SPECIFICATIONS This chapter gives a detail description of the physical, electrical and environmental characteristics of the Spinpoint M8U hard disk drive. Specification Summary Table 3-1: Specifications DESCRIPTION ST320LM008 ST500LM016 ST750LM024 ST1000LM026 Number of R/W Maximum KBPI 179K Flexible data TPI Encoding method Noise Predictive PRML... -
Page 15: Physical Specifications
SPECIFICATIONS Physical Specifications Table 3-2: Physical Specifications ST320LM008 ST500LM016 ST750LM024 ST1000LM026 DESCRIPTION Physical dimensions Length (mm) Width (mm) 69.85 Height (mm) 1 Disk 99 / 2 Disk 107 Weight (g, max) Logical Configurations Table 3-3: Logical Configurations ST320LM008 ST500LM016 ST750LM024 ST1000LM026 DESCRIPTION Total Number of... -
Page 16: Performance Specifications
SPECIFICATIONS Performance Specifications Table 3-4: Performance Specifications ST320LM008 ST500LM016 ST750LM024 ST1000LM026 DESCRIPTION 5.6 ms Average Latency Data Transfer Rate (Max) buffer to/from media 145MB/s host to/from buffer 500 MB/s 5,400 RPM Class Rotational Speed Buffer size NOTES: ∗ Seek time is defined as the time from the receipt of a read, write or seek command until the actuator has repositioned and settled on the desired track with the drive operating at nominal DC input voltages and nominal operating temperature. -
Page 17: Power Consumption
SPECIFICATIONS Power consumption Table 3-5: Power consumption DESCRIPTION ST320LM008 ST500LM016 ST750LM024 ST1000LM026 Rated Voltage Current 0.85 Power Consumption Spin-Up (Max) 750.00 Idle Watt Seq W/R (File) Watt Random Seek Watt Stand by Watt Sleep Watt Power Requirements Tolerance For + 5V +/- 5 Ripple, 0-30MHz Supply Rise Time... -
Page 18: Environmental Specifications
SPECIFICATIONS Environmental Specifications Table 3-6: Environmental Specifications ST320LM008 ST500LM016 ST750LM024 ST1000LM026 DESCRIPTION (Drive temperature measured on position of figure 3-1 should be max 65C in range of 5C-55C, Ambient Temperature specified operation temperature.) 5 ∼ 55°C Operating -40 ∼ 70°C Non-operating Max. -
Page 19: Figure 3-1 : Measurement Position
SPECIFICATIONS Figure 3-1 : Measurement Position. Spinpoint M8U-Internal Product Manual REV 3.4... -
Page 20: Reliability Specifications
SPECIFICATIONS Table 3-6: Environmental Specifications (continued) ST320LM008 ST500LM016 ST750LM024 ST1000LM026 DESCRIPTION Linear Shock (1/2 sine pulse) 325G Operating Non-operating 2.0 ms 750G Rotational Shock 3K rad/sec Operating 2.0 ms 30K rad/sec Non-operating 2.0 ms Acoustic Noise (Typical Sound Power) Idle 2.4 Bels 2.6 Bels Seek... -
Page 21: Chapter 4 Installation
INSTALLATION CHAPTER 4 INSTALLATION This chapter describes how to unpack, mount, configure and connect a Spinpoint M8U hard disk drive. It also describes how to install the drive in systems. Space Requirements Figure 4-1 shows the external dimensions of the drive. Figure 4-1: Mechanical Dimension Spinpoint M8U-Internal Product Manual REV 3.4... -
Page 22: Unpacking Instructions
INSTALLATION Unpacking Instructions (1) Open the shipping container of the Spinpoint M8U hard disk drive. (2) Lift the packing assembly that contains the drive out of the shipping container. (3) Remove the drive from the packing assembly. When you are ready to install the drive, remove it from the ESD (Electro Static Discharge) protection bag. -
Page 23: Ventilation
INSTALLATION Figure 4-2: Mounting Dimensions 4.3.2 Ventilation The Spinpoint M8U hard disk drive is designed to operate without the need of a cooling fan provided the ambient air temperature does not exceed 55ºC. Any user-designed cabinet must provide adequate air circulation to prevent exceeding the maximum temperature. -
Page 24: Cable Connectors
INSTALLATION Cable Connectors 4.4.1 USB Connectivity The USB interface is connected with in a point to point configuration with the USB host port. There is no master or slave relationship within the devices. Spinpoint M8U does not require extra power. The USB connector types are Type A, Type B, Mini-A and Mini-B. -
Page 25: Table 4-1 Usb Connector Pin Definitions
INSTALLATION Table 4-1 lists the signals connection on the USB interface. Table 4-1 USB Connector Pin Definitions Name Cable color Definition White Data - Green Data + Black Ground Name Cable color Definition White Data - Green Data + Permits distinction of Micro-A and Micro-B plug none Type A : connected to ground... -
Page 26: Figure 4-4 Usb Interface
INSTALLATION Figures 4.6 and 4.7 illustrates USB connector locations on the Spinpoint M8U. Figure 4-4 USB Interface Spinpoint M8U-Internal Product Manual REV 3.4... -
Page 27: Drive Installation
INSTALLATION Drive Installation The Spinpoint M8U hard disk drive can be installed in an USB-compatible system: • To install the drive with a motherboard that contains USB port (type A), connect the drive to the USB port using a USB plugs (type A). •... -
Page 28: System Startup Procedure
Disk Manager utility program provided by Samsung and follow the instructions. The Disk Manager utility program is available from Samsung on a floppy diskette, or downloadable from the Samsung website at http://www.seagate.com If, after all these steps are successfully completed, your system will not boot up, then contact technical support. -
Page 29: Chapter 5 Disk Drive Operation
INSTALLATION CHAPTER 5 DISK DRIVE OPERATION This chapter describes the operation of the Spinpoint M8U hard disk drive functional subsystems. It is intended as a guide to the operation of the drive, rather than a detailed theory of operation. Head / Disk Assembly (HDA) The Spinpoint M8U hard disk drive consists of a mechanical sub-assembly and a printed circuit board assembly (PCBA), as shown in Figure 5-1. -
Page 30: Figure 5-1: Exploded Mechanical View
INSTALLATION Figure 5-1: Exploded Mechanical View Spinpoint M8U-Internal Product Manual REV 3.4... -
Page 31: Disk Stack Assembly
INSTALLATION 5.1.3 Disk Stack Assembly The disk stack assembly in the Spinpoint M8U hard disk drive consists of 1 or 2 disks and disk spacers secured on the hub of the spindle motor assembly by a disk clamp. The glass disks have a sputtered thin-film magnetic coating. -
Page 32: Drive Electronics
INSTALLATION 5.2 D r i v e Electronics The Spinpoint M8U hard disk drive attains its intelligence and performance through the specialized electronic components mounted on the PCBA. The components are mounted on one side of the PCBA. The Preamplifier IC is the only electrical component that is not on the PCBA. It is mounted on the flexible circuit inside the HDA. -
Page 33: The Buffer Control Block
INSTALLATION 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. -
Page 34: Power Management
INSTALLATION 5.2.2.5 Power Management Power management features are incorporated into each block of the Spinpoint M8U. This allows the designer to tailor the amount of power management to the specified design. Other power management features include: • Independent power management control for each block. •... -
Page 35: Analog Anti-Aliasing Low Pass Filter
INSTALLATION 5.2.3.4 Analog Anti-Aliasing Low Pass Filter The 7 order equal-ripple analog filter provide filtering of the analog signal from AGC before it’s being converted to digital signal with the ADC. Its main function is to avoid aliasing for the ADC circuit. -
Page 36: Servo System
INSTALLATION 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 M8U hard disk drive is an Embedded Sector Servo System. -
Page 37: The Write Channel
INSTALLATION The ENDEC of 88C9310 decodes the 30/32 with post-processor format to produce a serial bit stream. This NRZ (Non Return to Zero) serial data is converted to 12-bit bytes. The Sequencer module identifies the data as belonging to the target sector. After a full sector is read, the 88i9322 (Rev2.0) checks to see if the firmware needs to apply an ECC algorithm to the data. -
Page 38: Write Caching
INSTALLATION example, Read Caching could save most of the disk transaction time by eliminating the seek and rotational latency delays that prominently dominate the typical disk transaction. Read Caching operates by continuing to fill its cache memory with adjacent data after transferring data requested by the host. -
Page 39: Defect Management
INSTALLATION 5.5.3 Defect Management The Spinpoint M8U hard disk drive media is scanned for defects. After defect scanning, the defective sectors are saved in the defect list. A defect encountered in the manufacturing process is slipped to the next physical sector location. All logical sector numbers are pushed down to maintain a sequential order of data. -
Page 40: Usb Interface And Usb Commands
INSTALLATION CHAPTER 6 USB INTERFACE AND USB COMMANDS Introduction A Samsung disk drive with an Embedded USB Interface fully supports and enhances PC mass storage requirements. The Samsung USB interface conforms to the USB 2.0 standards in Cabling, in Physical Signals, and in Logical Programming schemes. -
Page 41: Mechanical Interface
INSTALLATION 6.2.1 Mechanical Interface This chapter provides the mechanical and electrical specifications for the cables, connectors, and cable assemblies used to interconnect USB devices. The specification includes the dimensions, materials, electrical, and reliability requirements. This chapter documents minimum requirements for the external USB interconnect. -
Page 42: Usb Connector Termination Data
INSTALLATION the host system. Series “B” receptacle mates with a Series “B” plug (male). Electrically, Series “B” receptacles function as inputs to hubs or devices. Series “B” plug mates with a Series “B” receptacle. The Series “B” plug is always oriented towards the USB hub or device. -
Page 43: Series "A" And Series "B" Receptacles
INSTALLATION 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 “A” Receptacle Interface Spinpoint M8U-Internal Product Manual REV 3.4... -
Page 44: Series "A" And Series "B" Plugs
INSTALLATION Figure 6-4: USB Series “B” Receptacle Interface 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 Spinpoint M8U-Internal Product Manual REV 3.4... -
Page 45: Cable
INSTALLATION Figure 6-6: USB Series “B” Plug Interface 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, V , GND, and an overall shield. High-/full speed cable must be marked to indicate suitability for USB usage. -
Page 46: High-/Full-Speed Captive Cable Assemblies
INSTALLATION Figure 6-7: USB Standard Detachable Cable Assembly 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. -
Page 47: Low-Speed Captive Cable Assemblies
INSTALLATION 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... -
Page 48: Electrical Interface
INSTALLATION 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. -
Page 49: Signaling
INSTALLATION 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. -
Page 50: High-Speed (480Mb/S) Driver Characteristics
INSTALLATION 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Ω... -
Page 51: High-Speed (480Mb/S) Signaling Rise And Fall Times
INSTALLATION 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Ω... -
Page 52: High-Speed (480Mb/S) Signaling Levels
INSTALLATION 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. Table 6-2: High-speed Signaling Levels Ω... -
Page 53: Power Distribution
INSTALLATION 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. -
Page 54: Self-Powered Hubs
INSTALLATION Power switching on any non-removable function may be implemented either by removing its power or by shutting off the clock. Switching on the non-removable function is not required if the aggregate power drawn by it and the Hub Controller is less than one unit load. However, as long as the hub port associated with the function is in the Power-off state, the function must be logically reset and the device must appear to be not connected. -
Page 55: Protocol Layer
INSTALLATION Figure 6-13: Compound Self-powered Hub 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. -
Page 56: Common Usb Packet Fields
INSTALLATION 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. -
Page 57: Address Fields
INSTALLATION The host and all functions must perform a complete decoding of all received PID fields. Any PID received with a failed check field or which decodes to a non-defined value is assumed to be corrupted and it, as well as the remainder of the packet, is ignored by the packet receiver. -
Page 58: Endpoint Fields
INSTALLATION The function address (ADDR) field specifies the function, via its address, that is either the source or destination of a data packet, depending on the value of the token PID. As shown in Figure 6-15, a total of 128 addresses are specified as ADDR<6:0>. The ADDR field is specified for IN, SETUP, and OUT tokens and the PING and SPLIT special token. -
Page 59: Packet Format
INSTALLATION the data bit and then the remainder is shifted left one bit and the low-order bit set to zero. If the result of that XOR is one, then the remainder is XORed with the generator polynomial. When the last bit of the checked field is sent, the CRC in the generator is inverted and sent to the checker MSb first. -
Page 60: Data Packet
INSTALLATION 6.3.3.2 Data Packet A data packet consists of a PID, a data field containing zero or more bytes of data, and a CRC as shown in Figure 6-19. There are four types of data packets, identified by differing PIDs: DATA0, DATA1, DATA2 and MDATA. -
Page 61: Start-Of-Frame Packets
INSTALLATION 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. -
Page 62: Transfer/Endpoint Types
INSTALLATION • Message Pipes have a defined USB format. They are host controlled, which are initiated by a request sent from the host. Data is then transferred in the desired direction, dictated by the request. Therefore message pipes allow data to flow in both directions but will only support control transfers. 6.3.5 Transfer/Endpoint Types The Universal Serial Bus specification defines four transfer/endpoint types, •... -
Page 63: Control Transaction
INSTALLATION 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. The packet length of control transfers in low speed devices must be 8 bytes, high speed devices allow a packet size of 8, 16, 32 or 64 bytes and full speed devices must have a packet size of 64 bytes. -
Page 64: Figure 6-24: Data Stage
INSTALLATION is working, but temporary has no data to send. OUT: When the host needs to send the device a control data packet, it issues an OUT token followed by a data packet containing the control data as the payload. If any part of the OUT token or data packet is corrupt then the function ignores the packet. -
Page 65: Bulk Transaction
INSTALLATION OUT (Figure 6-25): If the host sent OUT token(s) during the data stage to transmit data, the function will acknowledge the successful recept of data by sending a zero length packet in response to an IN token. However if an error occurred, it should issue a STALL or if it is still busy processing data, it should issue a NAK asking the host to retry the status phase later. -
Page 66: Figure 6-28: Bulk Transaction Diagram
INSTALLATION Figure 6-28: Bulk Transaction Diagram The Figure 6-27 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. -
Page 67: Usb Device Generic Framework
INSTALLATION 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. -
Page 68: Attatched
INSTALLATION Table 6-4: Visible Device States 6.3.6.1.1 Attatched 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. -
Page 69: Default
INSTALLATION that configuration is the maximum the device will draw from V in either mode. The device must observe this maximum, regardless of its mode. If a configuration supports only one power mode and the power source of the device changes, the device will lose its current configuration and address and return to the Powered state. -
Page 70: Bus Enumeration
INSTALLATION remote wakeup signaling must be disabled. 6.3.6.1.7 Bus Enumeration Before application can communicate with a device, the host need to learn about what transfer types and endpoint the device support. The host also must assign an address to the device (Figure 6-29) Figure 6-30: Enumeration When a USB device is attached to or removed from the USB, the host uses a process known as bus enumeration to identify and manage the device state changes necessary. -
Page 71: Address Assignment
INSTALLATION the effect of resetting the device. A reset USB device has the following characteristics: Responds to the default USB address Is not configured Is not initially suspended When a device is removed from a hub port, the hub disables the port where the device was attached and notifies the host of the removal. -
Page 72: Request Processing
INSTALLATION device, Host Software shall not select that configuration. USB devices shall limit the power they consume from V to one unit load or less until configured. Suspended devices, whether configured or not, shall limit their bus power consumption. Depending on the power capabilities of the port to which the device is attached, a USB device may be able to draw up to five unit loads from V after configuration. -
Page 73: Figure 6-31: Windex Format When Specifying An Endpoint
INSTALLATION ■ bmRequestType This bitmapped field identifies the characteristics of the specific request. In particular, this field identifies the direction of data transfer in the second phase of the control transfer. The state of the Direction bit is ignored if the wLength field is zero, signifying there is no Data stage. The USB Specification defines a series of standard requests that all devices must support. -
Page 74: Standard Usb Device Request Overview
INSTALLATION bmRequestType field. If this field is zero, there is no data transfer phase. On an input request, a device must never return more data than is indicated by the wLength value; it may return less. On an output request, wLength will always indicate the exact amount of data to be sent by the host. -
Page 75: Clear Feature (Request Code 1)
INSTALLATION Table 6-7: Standard Request Codes Table 6-8: Descriptor Types 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. Table 6-9: Standard Feature Sectors 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. -
Page 76: Get Configuration (Request Code 8)
INSTALLATION recipient is an interface, and only endpoint feature selector values may be used when the recipient is an endpoint. Refer to Table 6-9 for a definition of which feature selector values are defined for which recipients. A ClearFeature () request that references a feature that cannot be cleared, that does not exist, or that references an interface or endpoint that does not exist, will cause the device to respond with a Request Error. -
Page 77: Get Interface (Request Code 10)
INSTALLATION a configuration if the device were operating at the other speed. A request for a configuration descriptor returns the configuration descriptor, all interface descriptors, and endpoint descriptors for all of the interfaces in a single request. The first interface descriptor follows the configuration descriptor. The endpoint descriptors for the first interface follow the first interface descriptor. -
Page 78: Figure 6-33 Information Returned By A Getstatus() Request To A Device
INSTALLATION Figure 6-33 Information Returned by a GetStatus() Request to a Device The Self Powered field indicates whether the device is currently self-powered. If D0 is reset to zero, the device is bus-powered. If D0 is set to one, the device is self-powered. The Self Powered field may not be changed by the SetFeature() or ClearFeature() requests. -
Page 79: Set Address (Request Code 5)
INSTALLATION 6.3.6.3.7 Set Address (Request Code 5) This request sets the device address for all future device accesses. The wValue field specifies the device address to use for all subsequent accesses. As noted elsewhere, requests actually may result in up to three stages. In the first stage, the Setup packet is sent to the device. -
Page 80: Set Feature (Request Code 3)
INSTALLATION 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. For example, a device can implement several configuration descriptors. -
Page 81: Set Interface (Request Code 11)
INSTALLATION Table 6-10: Test Mode Selectors If wLength is non-zero, then the behavior of the device is not specified. If an endpoint or interface is specified that does not exist, then the device responds with a Request Error. Default state: A device must be able to accept a SetFeature(TEST_MODE, TEST_SELECTOR) request when in the Default State. -
Page 82: Standard Usb Descriptor
INSTALLATION When an endpoint supports isochronous transfers, the endpoint may also require per-frame transfers to vary in size according to a specific pattern. The host and the endpoint must agree on which frame the repeating pattern begins. The number of the frame in which the pattern began is returned to the host. If a high-speed device supports the Synch Frame request, it must internally synchronize itself to the zeroth microframe and have a time notion of classic frame. -
Page 83: Device Descriptor
INSTALLATION 6.3.6.4.2 Device Descriptor A device descriptor describes general information about a USB device. It includes information that applies globally to the device and all of the device’s configurations. A USB device has only one device descriptor. A high-speed capable device that has different device information for full-speed and high-speed must also have a device_qualifier descriptor. -
Page 84: Device Qualifier Descriptor
INSTALLATION 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. -
Page 85: Configuration Descriptor
INSTALLATION The vendor, product, device, manufacturer, product, and serialnumber fields of the standard device descriptor are not included in this descriptor since that information is constant for a device for all supported speeds. The version number for this descriptor must be at least 2.0 (0200H). The host accesses this descriptor using the GetDescriptor() request. -
Page 86: Other_Speed_Configuration_ Descriptor
INSTALLATION 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. -
Page 87: Interface Descriptor
INSTALLATION 6.3.6.4.6 Interface Descriptor The interface descriptor describes a specific interface within a configuration. A configuration provides one or more interfaces, each with zero or more endpoint descriptors describing a unique set of endpoints within the configuration. When a configuration supports more than one interface, the endpoint descriptors for a particular interface follow the interface descriptor in the data returned by the GetConfiguration() request. -
Page 88: Endpoint Descriptor
INSTALLATION 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. - Page 89 INSTALLATION 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..4=01B) or whether it is a data endpoint that also serves as an implicit feedback endpoint for one or more data endpoints (bits 5..4=10B).
-
Page 90: String Descriptor
INSTALLATION maximum packet size for the endpoint can be any allowed value (as defined in Chapter 5). If bits 12..11 of wMaxPacketSize are not zero (0), the allowed values for wMaxPacketSize bits 10..0 are limited as shown in Table 6-17. 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;... -
Page 91: Bulk-Only Transport
INSTALLATION 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. -
Page 92: Host/Device Packet Transfer Order
INSTALLATION 6.4.1.3 Host/Device Packet Transfer Order The host shall send the CBW before the associated Data-Out, and the device shall send Data-In after the associated CBW and before the associated CSW. The host may request Data-In or CSW before sending the associated CBW. -
Page 93: Table 6-20: Bulk Only Transport Device Descriptor
INSTALLATION Table 6-20: Bulk Only Transport Device Descriptor The iSerialNumber field shall be set to the index of the string descriptor that contains the serial number. The serial number shall contain at least 12 valid digits, represented as a UNICODE string. The last 12 digits of the serial number shall be unique to each USB idVendor and idProduct pair. -
Page 94: Configuration Descriptor (Table 6-22)
INSTALLATION 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. -
Page 95: Endpoint Descriptor
INSTALLATION 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. (Table 6-24) Table 6-24: Bulk-In Endpoint Descriptor ■... -
Page 96: Figure 6-36: Command/Data/Status Flow
INSTALLATION Figure 6-36: Command/Data/Status Flow Figure 6-37: Status Transport Flow Spinpoint M8U-Internal Product Manual REV 3.4... -
Page 97: Command Block Wrapper (Cbw)
INSTALLATION 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. -
Page 98: Command Status Wrapper (Csw)
INSTALLATION CBWCB: The command block to be executed by the device. The device shall interpret the first bCBWCBLength bytes in this field as a command block as defined by the command set identified by bInterfaceSubClass. If the command set supported by the device uses command blocks of fewer than 16 (10h) bytes in length, the significant bytes shall be transferred first, beginning with the byte at offset 15 (Fh). -
Page 99: Data Transfer Conditions
INSTALLATION 6.4.3.3 Data Transfer Conditions This section describes how the host and device remain synchronized. The host indicates the expected transfer in the CBW using the Direction bit and the dCBWDataTransferLength field. The device then determines the actual direction and data transfer length. The device responds as defined in 6 - Host/Device Data Transfers by transferring data, STALLing endpoints when specified, and returning the appropriate CSW. -
Page 100: Valid And Meaningful Cbw
INSTALLATION 6.4.4.2 Valid and Meaningful CBW The host communicates its intent to the device through the CBW. The device performs two verifications on every CBW received. First, the device verifies that what was received is a valid CBW. Next, the device determines if the data within the CBW is meaningful. -
Page 101: Device Error Handling
INSTALLATION 6.4.4.4 Device Error Handling The device may not be able to fully satisfy the host's request. At the point when the device discovers that it cannot fully satisfy the request, there may be a Data-In or Data-Out transfer in progress on the bus, and the host may have other pending requests. -
Page 102: Ufi Command Set
INSTALLATION 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. -
Page 103: Ufi Command Set Overview
INSTALLATION 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. -
Page 104: Inquiry Command (12H)
INSTALLATION 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. -
Page 105: Read (10) Command (28H)
INSTALLATION 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. -
Page 106: Read Format Capacity Command (23H)
INSTALLATION 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. -
Page 107: Capacity List
INSTALLATION 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. -
Page 108: Write (10) Command (2Ah)
INSTALLATION 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. -
Page 109: Chapter 7 Maintenance
INSTALLATION CHAPTER 7 MAINTENANCE General Information The Samsung Spinpoint M8U 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 adj ustments, greatly reducing the amount of downtime required for unscheduled repairs. -
Page 110: Figure 7-1 : Hdd Handling Guide-Please Handle Hdd By Side Surfaces
INSTALLATION - - Please handle HDD by side surfaces! Fig. 7-1: - - Do not Touch Cover and PCB! Fig. 7-2: - - Do Not Stack! Fig. 7-3: Spinpoint M8U-Internal Product Manual REV 3.4... -
Page 111: Service And Repair
Service and Repair To determine the warranty for a specific drive, use a web browser to access the following web page http://www.seagate.com/support/warranty-and-returns From this page, click on the “Verify Your Warranty” link. You will be asked to provide the drive serial number, model number (or part number) and country of purchase.