Standard Microsystems is a registered trademark of Standard Microsystems Corporation, and SMSC is a trademark of Standard Microsystems
Corporation. Product names and company names are the trademarks of their respective holders. Circuit diagrams utilizing S MSC products are incl uded
as a means of illustrating typical applications; consequently complete information sufficient for construction purposes is not necessarily given. Although
the information has been checked and is believed to be accurate, no responsibility is assumed for inaccuracies. SMSC reserves the right to make
changes to specifications and product descriptions at any time without notice. Contact your local SMSC sales office to obtain the latest speci fications
before placing your product order. The provision of this information does not convey to the purchaser of the semiconductor devices described any
licenses under the patent rights of SMSC or others. All sales are expressly conditional on your agreement to the terms and conditions of the most
recently dated version of SMSC's standard Terms of Sale Agreement dated before the date of your order (the "Terms of Sale Agreem ent" ). T he product
may contain design defects or errors known as anomalies which may cause the product's functions to deviate from published specifications. Anom aly
sheets are available upon request. SMSC products are not designed, intended, authorized or warranted for use in any life support or other application
where product failure could cause or contribute to personal injury or severe property damage. Any and all such uses without prior written approval of an
Officer of SMSC and further testing and/or modification will be fully at the risk of the customer. Copies of this document or other SMSC literature, as well
as the Terms of Sale Agreement, may be obtained by visiting SMSC’s website at http://www.smsc.com.
SMSC DISCLAIMS AND EXCLUDES ANY AND ALL WARRANTIES, INCLUDING WITHOUT LIMITATION ANY AND ALL IMPLIED WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND AGAINST INFRINGEMENT, AND ANY AND ALL WARRANTIES
ARISING FROM ANY COURSE OF DEALING OR USAGE OF TRADE.
IN NO EVENT SHALL SMSC BE LIABLE FOR ANY DIRECT, INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES,
OR FOR LOST DATA, PROFITS, SAVINGS OR REVENUES OF ANY KIND; REGARDLESS OF THE FORM OF ACTION, WHETHER BASED ON
CONTRACT, TORT, NEGLIGENCE OF SMSC OR OTHERS, STRICT LIABILITY, BREACH OF WARRANTY, OR OTHERWISE; WHETHER OR NOT
ANY REMEDY IS HELD TO HAVE FAILED OF ITS ESSENTIAL PURPOSE; AND WHETHER OR NOT SMSC HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
Table 18 – SRAM Data Port Register..........................................................................................................................26
Table 25 – SIE Configuration Register........................................................................................................................29
Table 26 - USB Bus Status Register...........................................................................................................................30
Table 27 – USB Bus Status Mask Register.................................................................................................................30
Table 28 – SIE Status Register...................................................................................................................................31
Table 29 – SIE Status Mask Register..........................................................................................................................31
Table 30 – USB Configuration Number Register.........................................................................................................32
Table 31 – Endpoint 0 Receive Control Register........................................................................................................ 32
Table 32 – Endpoint 0 Transmit Control Register....................................................................................................... 32
Table 33 – Endpoint 1 Receive Control Register........................................................................................................ 32
Table 34 – Endpoint 1 Transmit Control Register....................................................................................................... 33
Table 35 – Endpoint 2 Control Register...................................................................................................................... 33
Table 50 – USB Error Register.................................................................................................................................... 37
Table 51 – MSB ATA Data Register............................................................................................................................ 38
Table 52 – LSB ATA Data Register............................................................................................................................. 38
Table 53 – ATA Transfer Count Register 0................................................................................................................. 38
Table 54 – ATA Transfer Count Register 1................................................................................................................. 38
Table 55 – ATA Transfer Count Register 2................................................................................................................. 38
Table 56 – ATA Transfer Count Register 3................................................................................................................. 39
Table 57 –ATA Control Register..................................................................................................................................39
Table 59 – IDE Timing Register..................................................................................................................................40
Table 60 –ATA Slew Rate Control A Register............................................................................................................. 42
Table 61 –ATA Slew Rate Control B Register............................................................................................................. 42
Table 62 – IDE Transaction Timing............................................................................................................................. 45
Table 63 – ULTRA ATA/66 Control Signal Assignments.............................................................................................46
The USB97C201 is a USB2.0 Mass Storage Class Peripheral Controller intended for use with standard ATA hard
drives and standard ATAPI-5 devices.
The device consists of a USB 2.0 PHY and SIE, buffers, Fast 8051 microprocessor with expanded scratchpad and
768 of program SRAM, and an ATA-66 compatible interface.
Provisions for external Flash Memory up to 64K bytes for program storage is provided.
Internal 768 Bytes of program SRAM are also provided.. This internal SRAM is used for program storage to
implement program upgrade via USB download to “boot block” Flash program memory, if desired.
Eight GPIO pins are provided for controlling external power control elements and sensing specialized drive functions.
Provisions are made to allow dynamic attach and re-attach to the USB bus to allow hot swap of drives to be
implemented.
IDE_DRQISThis pin is the active high DMA request from
DISK DRIVE INTERFACE
the ATA/ATAPI interface.
IDE IO Read
Strobe
IDE Register
Address 1
IDE Register
Address 0
IDE Register
Address 2
IDE DataIDE_D15IO20This pin is the bi-directional data bus bit 15
IDE IO Write
Strobe
IDE DMA
Acknowledge
IDE Interrupt
Request
IDE DataIDE_D13IO20This pin is the bi-directional data bus bit 13
IDE_nIORO20This pin is the active low read signal for the
interface.
IDE_SA1O20This pin is the register select address bit 1
signal for the ATA/ATAPI interface.
IDE_SA0O20This pin is the register select address bit 0
signal for the ATA/ATAPI interface.
IDE_SA2O20This pin is the register select address bit 2
signal for the ATA/ATAPI interface.
signal for the ATA/ATAPI interface.
IDE_nIOWO20This pin is active low write signal for the
ATA/ATAPI interface.
IDE_nDACKO20This pin is the active low DMA acknowledge
signal for the ATA/ATAPI interface.
IDE_IRQISThis pin is the active high interrupt request
signal for the ATA/ATAPI interface.
signal for the ATA/ATAPI interface.
IDE DataIDE_D14IO20This pin is the bi-directional data bus bit 14
signal for the ATA/ATAPI interface.
.
IDE Chip
Select 0
IDE Chip
Select 1 0
IDE DataIDE_D[0:12]IO20These pins are bits 0-12 of the ATA/ATAPI bi-
IO ReadyIORDYIThis pin is the active high IORDY signal from
IDE_nCS0O20This pin is the active low chip select 0 signal
for the ATA/ATAPI interface.
IDE_nCS1O20This pin is the active low select 1 signal for the
ATA/ATAPI interface.
directional data bus.
the IDE drive.
SMSC DS – USB97C201Page 10Rev. 03/25/2002
PRELIMINARY
USB Bus
Data
USB
Transceiver
Filter
USB
Transceiver
Bias
Termination
Resistor
Full Speed
USB Data
Memory Data
Bus
Memory
Address Bus
Memory Write
Strobe
Memory Read
Strobe
IO Read
Strobe
IO Write
Strobe
USB INTERFACE
USBUSB+
LOOPFLTRThis pin provides the ability to supplement the
RBIASA 9.09 Kohm precision resistor is attached
RTERMA precision 1.5Kohm precision resistor is
FSFS+
MD[7:0]IO12These signals are used to transfer data
MA[15:0]O12These signals address memory locations
nMWRO12Program Memory Write; active low
nMRDO12Program Memory Read; active low
nIORO12XDATA space Read; active low
nIOWO12XDATA space Write; active low
IO-UThese pins connect to the USB bus data
signals.
internal filtering of the transceiver with an
external network, if required.
from ground to this pin to set the transceiver’s
internal bias currents.
attached to this pin from a 3.3V supply.
IO-UThese pins connect to the USB- and USB+
pins through 31.6 ohm series resistors.
MEMORY/IO INTERFACE
between the internal CPU and the external
program memory.
within the external memory.
SMSC DS – USB97C201Page 11Rev. 03/25/2002
PRELIMINARY
MISC
Crystal
Input/External
Clock Input
Crystal
Output
Clock Output CLKOUTO8This pin produces a 30Mhz clock signal
General
Purpose I/O
RESET input nRESETISThis active low signal is used by the system to
Test inputnTest[0:2}IPThese signals are used for testing the chip.
XTAL1/
CLKIN
XTAL2OCLKx12Mhz Crystal
GPIO[0:7]IO20These general purpose pins may be used
POWER, GROUNDS, and NO CONNECTS
VDD+2.5V Core power
VDDIO+3.3V I/O power
VDDP+2.5 Analog power
VSSPAnalog Ground Reference
VDDA+3.3V Analog power
VSSAAnalog Ground Reference
GNDGround Reference
NCNo Connect. These pins should not be
ICLKx12Mhz Crystal or external clock input.
This pin can be connected to one terminal of
the crystal or can be connected to an external
12Mhz clock when a crystal is not used.
This is the other terminal of the crystal, or left
open when an external clock source is used to
drive XTAL1/CLKIN. It may not be used to
drive any external circuitry other than the
crystal circuit.
independent of the processor clock divider. It
is held inactive and low whenever the internal
processor clock is stopped or is being
obtained from the ring oscillator.
either as inputs, edge sensitive interrupt
inputs, or outputs. In addition, GPIO0 has the
capability of auto-toggling at a 1Hz rate when
used as an output.
reset the chip. The active low pulse should be
at least 100ns wide.
User should normally leave them
unconnected. For board testing, all pads
except these test inputs are included in an
XNOR chain, such that by tying nTEST2 low,
nIOR will reflect the toggling of a signal on
each pin. Circuit board continuity of the pin
solder connections after assembly can be
checked in this manner
connected externally.
SMSC DS – USB97C201Page 12Rev. 03/25/2002
PRELIMINARY
5.1 BUFFER TYPE DESCRIPTIONS
Table 1 - USB97C201 Buffer Type Descriptions
BUFFERDESCRIPTION
IInput
ISInput with Schmitt trigger
IO8Input/Output with 8 mA drive
O8Output with 8mA drive
O12Output with 12mA drive
IO20Input/output with 20mA drive
OD12Open drain….12mA sink
O20Output with 20mA drive
ICLKxXTAL clock input
OCLKxXTAL clock output
I/O-UDefined in USB specification
SMSC DS – USB97C201Page 13Rev. 03/25/2002
PRELIMINARY
6.0 FUNCTIONAL BLOCK DESCRIPTIONS
6.1 MCU
The 64K memory map is as follows from the 8051's viewpoint:
6.1.1 MCU MEMORY MAP: CODE SPACE
The 8051 has a single flat 64K Code space. External memory requires 80ns access times from Address to Data and
less than 80ns output enable access times, assuming the use of the nMEMR signal as OE on the memory.
Table 2 - MCU Code Memory Map
8051 ADDRESSCODE SPACEACCESS
0x0700-0xFFFFFixed MemoryExternal Program
Memory
0x0400-0x06FF768 Bytes of Fixed 16k FLASH Page
OR
768 Bytes of Internal SRAM for program execution
(see bit 7 of the UTIL_CFG register for more
information)
0x0000-0x03FFFixed MemoryExternal Program
8051 MCU External Code Address
Space
0xFFFF
K
4
6
External Program
Memory
OR
Internal Program
SRAM
Memory
0x0700
0x0400
0x0000
FIGURE 1 - MCU TO EXTERNAL CODE SPACE MAP
SMSC DS – USB97C201Page 14Rev. 03/25/2002
Intern al 76 8 Byte
SRAM or External
Memory
PRELIMINARY
6.1.2 MCU MEMORY MAP: XDATA SPACE
Table 3 - MCU XData Memory Map
8051 ADDRESSDATA SPACEACCESS
0x3F30-0xFFFF
0x3F00-0x3F2F
0x33F7-0X3EFF
033F6External ATA Interface I/OExternal
0x31F8-0x33F5External Memory or I/O DevicesExternal
0x31F0-0x31F7External ATA Interface I/OExternal
0x30F4-0x31EFExternal Memory or I/O DevicesExternal
0X30F0-0X30F3Internal Test Registers (reserved access)DO NOT ACCESS
0X0700-0X30EFExternal Memory or I/O DevicesExternal
Internal Test Registers (reserved access)
External Memory or I/O Devices
External
(IOR or IOW
active)
DO NOT ACCESS
External
(IOR or IOW
active)
(IOR or IOW
active)
(IOR or IOW
active)
(IOR or IOW
active)
(IOR or IOW
active)
(IOR or IOW
active)
(IOR or IOW
active)(see Note 1)
Note 1: This XDATA space is accessed using MOVX instructions. A region of 8051 Special Function Registers
(SFR) is also accessible at 0x0100 to 0x01FF addresses using the MOV instructions. In addition to the
normal 8051 SFRs, there are also numerous Runtime Registers in this SFR space. These Runtime
Registers are external to the 8051, but internal to the USB97C201.
SMSC DS – USB97C201Page 15Rev. 03/25/2002
PRELIMINARY
6.1.3 MCU BLOCK REGISTER SUMMARY
Table 4 - MCU Block Register Summary
(These registers are external to the 8051 design core)
ATA CONFIGURATION REGISTERS
DBMSB_ATAR/WMSB ATA Data Register38
DCLSB_ATAR/WLSB ATA Data Register38
DDATA_CTLR/WATA Control Register39
DEATA_DMAR/WATA Ultra DMA Timing Register40
DFIDE_TIMR/WIDE Timing Register40
E1ATA_CNT0R/WATA Transfer Count Register 038
E2ATA_CNT1R/WATA Transfer Count Register 138
E3ATA_CNT2R/WATA Transfer Count Register 238
E4ATA_CNT3R/WATA Transfer Count Register 339
E5ATA_SRCAR/WATA Slew Rate Control A Register42
E6ATA_SRCBR/WATA Slew Rate Control B Register42
SMSC DS – USB97C201Page 17Rev. 03/25/2002
PRELIMINARY
Table 5 - 8051 Core SFR Register Summary
These registers are part of the 8051 design core itself.
Bit WRS of the SPC_FNC register controls the operation of MOVX writes the program or XDATA bus of the
8051. Setting it to 0 ( the reset state), will direct writes to the XDATA bus, either to internal or external
destinations, while setting it to 1 will allow writes to the program memory bus to occur, either internally( if the
768 SRAM is the target) or externally.
Bits MD2:0 of the CKCON SFR register (8Eh) control the cycle timing for external accesses using the nIOR and
nIOW signals. This allows slow peripheral devices to be attached. The values and corresponding strobe widths
are shown below:
Note: the strobe width will vary with the actual clock divider used for the processor. For example if, 16 Mhz is used,
an MD[2:0] value of 111 will result in a 28 clock strobe or 1866ns.
SMSC DS – USB97C201Page 18Rev. 03/25/2002
NIOR/NIOW STROBE (AT
30MHZ)
PRELIMINARY
6.1.4 MCU REGISTER DESCRIPTIONS
6.1.4.1 MCU Runtime Registers
Table 6 - Interrupt 0 Source Register
ISR_0
(0x80 - RESET=0x0C)INTERRUPT 0 SOURCE REGISTER
BITNAMER/WDESCRIPTION
7USB_STATR1= USB Bus System Event has occurred. Check USB_STAT
6SETUPR/W1= A SETUP packet was received on Endpoint 0. The EP0RX
5ReservedRThis bit always reads a “0”.
4ATA_IRQR/WExternal interrupt input from the ATA-66 Interface.
3RAMRD_BR/W1 = The current transfer from the SRAM B Buffer has been
2RAMRD_AR/W1 = The current transfer from the SRAM A Buffer has been
1RAMWR_BR/W1 = The current transfer to the SRAM B Buffer has been
0RAMWR_AR/W1 = The current transfer to the SRAM A Buffer has been
register for the specific event(s). This must be cleared by
clearing the USB_STAT register.
bit of ISR_1 will not be set. If another SETUP packet is
received on Endpoint 0 while this bit is high, the bit will go low
and then immediately high again, to signal the duplicate
SETUP. If all other bits in this register are clear and the INT0
of the 8051is configured for edge triggering, then another
interrupt will be generated within the 8051. The firmware must
clear this bit by writing a "1" to it to allow the Enpoint 0 buffer
to receive subsequent data packets during the SETUP
transaction. Receipt of these packets will set EP0RX in ISR_1.
1 = An ATA interrupt has occurred.
completed. See Sections 6.7 and 6.9 for more detail. This bit
is also cleare d by writing a “1” to the RAMRD_TOGGLE bit of
the EP2_CTL register.
completed. See Sections 6.7 and 6.9 for more detail. . This bit
is also cleare d by writing a “0” to the RAMRD_TOGGLE bit of
the EP2_CTL register.
completed. This bit may be cleared by the internal hardware
state machine while operating in “Auto Transfer” mode. See
Sections 6.7 and 6.9 for more detail.
completed. This bit may be cleared by the internal hardware
state machine while operating in “Auto Transfer” mode. See
Sections 6.7 and 6.9 for more detail.
The bits in this register (except bit 7) are set to their POR values by writing a ‘1’ to the corresponding bit. If not
masked by the corresponding bit in the IMR0 mask register, a “1” on any of these bits will generate a “1” on the 8051
core’s external INT0 input.
1 = Mask Interrupt
3RAMRD_BR/WSRAM Buffer B Output Interrupt Mask
0 = Enable Interrupt
1 = Mask Interrupt
2RAMRD_AR/WSRAM Buffer A Output Interrupt Mask
0 = Enable Interrupt
1 = Mask Interrupt
1RAMWR_BR/WSRAM Buffer B Input Interrupt Mask
0 = Enable Interrupt
1 = Mask Interrupt
0RAMWR_AR/WSRAM Buffer A Input Interrupt Mask
0 = Enable Interrupt
1 = Mask Interrupt
Note1: The mask bits do not prevent the status in the ISR_0 register from being set, only from generating an
interrupt.
Table 8 - Interrupt 1 Source Register
ISR_1
(0x90- RESET=0x00)INTERRUPT 1 SOURCE REGISTER
BITNAMER/WDESCRIPTION
7ZLP_EP0R/W1= A ZLP has been received on EP0RX.
6ReservedRThis bit always reads a “0”.
5ATA_PIORThis bit reflects that state of the PIO_COMPLETE bit (bit 6) of
the ATA_CTL register. It cannot be written directly.
4EP1RXR/W1 = A Packet was successfully received on Endpoint 1 and
stored in the Buffer SRAM. OUT tokens will be NAK’d until this
bit is cleared.
3EP1TXR/W1 = A Packet was successfully transmitted on Endpoint 1 from
the Buffer SRAM. IN tokens will be NAK’d until this bit is
cleared.
2EP0RXR/W1 = A non-SETUP, non ZLP Packet (see ISR_0 SETUP bit)
was successfully received on Endpoint 0 and stored in the
Buffer SRAM. OUT tokens will be NAK’d until this bit is
cleared.
1EP0TXR/W1 = A Packet was successfully transmitted on Endpoint 0 from
the Buffer SRAM. IN tokens will be NAK’d until this bit is
cleared.
0SUSPENDR/WSuspend – If 3ms of IDLE state are detected by the hardware,
then this bit will be set.
Note 1: The bits (except for bit 5)in this register are cleared by writing a ‘1’ to the corresponding bit. If not masked by
the corresponding bit in the IMR1 mask register, a “1” on any of these bits will generate a “1” on the 8051 core’s
external INT1 input.
SMSC DS – USB97C201Page 20Rev. 03/25/2002
PRELIMINARY
Table 9 - Interrupt 1 Mask
IMR_1
(0x94- RESET=0xFF)INTERRUPT 1 MASK REGISTER
BITNAMER/WDESCRIPTION
7ZLP_EP0R/W Zero Length Packet Interrupt Mask
0 = Enable Interrupt
1 = Mask Interrupt
6ReserevedR/WReserved. This bit should never be written to a “0”.
5ATA_PIOR/WATA PIO Complete Interrupt Mask
0 = Enable Interrupt
1 = Mask Interrupt
4EP1RXR/WEndpoint 1 Received Packet Interrupt Mask
Note 1: The mask bits do not prevent the status in the ISR_1 register from being set, only from generating an
interrupt.
Table 10 - Device Revision Register
DEV_REV
(0x95- RESET=0xXX)DEVICE REVISION REGISTER
BITR/WDESCRIPTION
[7:0]XXhRThis register defines additional revision information
used internally by SMSC. The value is silicon revision
dependent.
Table 11 - Device Identification Register
DEV_ID
(0x96- RESET=0x12)DEVICE IDENTIFICATION REGISTER
BITR/WDESCRIPTION
[7:0]12hRThis register defines additional revision information
used internally by SMSC
SMSC DS – USB97C201Page 21Rev. 03/25/2002
PRELIMINARY
6.1.4.2 Utility Registers
BITNAMER/WDESCRIPTION
7GPIO7R/WGPIO7 Direction
6GPIO6R/WGPIO6 Direction
5GPIO5R/WGPIO5 Direction
4GPIO4/nWER/WGPIO4 Direction
3GPIO3/T1R/WGPIO3 Direction
2GPIO2/T0R/WGPIO2 Direction
1GPIO1/TXDR/WGPIO1 Direction
0GPIO0/RXDR/WGPIO0 Direction
Table 12 - GPIO Direction Register
GPIO_DIR
(0x97- RESET=0x00)
GPIO DIRECTION
REGISTER
0 = In
1 = Out
0 = In
1 = Out
0 = In
1 = Out
0 = In
1 = Out
0 = In
1 = Out
0 = In
1 = Out
0 = In
1 = Out
0 = In
1 = Out
SMSC DS – USB97C201Page 22Rev. 03/25/2002
PRELIMINARY
GPIO Direction Bit
GPIO out data
GPIO[7:5]
GPIO in data
Edge Detector
GPIO2 data out
8051 "T0 timer P3.4"
8051 "T1 timer P3.5"
RXD "Uart P3.0"
Mux Enable
GPIO1 data out
TXD "Uart P3 .1 "
Mux Enable
0
1
S
Mux Enable
0
1
S
Mux Enable
Enable
GPIO0 data out
0
"0"
1
S
0
1
S
GPIO2 data in
TBD
GPIO3 data out
GPIO3 data in
TBD
1 Hz
gate
GPIO0 DIR
GPIO0 data in
Edge Detector
GPIO1 DIR
GPIO1 data in
GPIO2 DIR
Edge Detector
GPIO3 DIR
Edge Detector
GPIO2
GPIO3
GPIO0
GPIO1
GPIO4 data out
IDE_nIOW
Mux Enable
0
1
S
Edge Detector
GPIO4 DIR
GPIO4/
nWE
GPIO4 data in
FIGURE 2 - GPIO MUXING BLOCK DIAGRAM
SMSC DS – USB97C201Page 23Rev. 03/25/2002
PRELIMINARY
Table 13 - GPIO Output Register
GPIO_OUT
(0x9A- RESET=0x00)
BITNAMER/WDESCRIPTION
7GPIO7R/WGPIO7 Output Buffer Data
6GPIO6R/WGPIO6 Output Buffer Data
5GPIO5R/WGPIO5 Output Buffer Data
4GPIO4/nWER/WGPIO4 Output Buffer Data
3GPIO3/T1R/WGPIO3 Output Buffer Data
2GPIO2/T0R/WGPIO2 Output Buffer Data
1GPIO1/TXDR/WGPIO1 Output Buffer Data
0GPIO0/RXDR/WGPIO0 Output Buffer Data
Table 14 - GPIO Input Register
GPIO_IN
(0x9B- RESET=0x00)GPIO INPUT REGISTER
BITNAMER/WDESCRIPTION
7GPIO7RGPIO7 Input Buffer Data
6GPIO6RGPIO6 Input Buffer Data
5GPIO5RGPIO5 Input Buffer Data
4GPIO4/nWERGPIO4 Input Buffer Data
3GPIO3/T1RGPIO3 Input Buffer Data
2GPIO2/T0RGPIO2 Input Buffer Data
1GPIO1/TXDRGPIO1 Input Buffer Data
0GPIO0/RXDRGPIO0 Input Buffer Data
GPIO DATA OUTPUT
REGISTER
Table 15 – GPIO Interrupt Status Register (INT4)
GPIO_IRQ
(0XC0- RESET=0x00)GPIO INTERRUPT STATUS REGISTER
BITNAMER/WDESCRIPTION
7GPIO7_IRQR/W1 = A level change has occurred on GPIO7.
6GPIO6_IRQR/W1 = A level change has occurred on GPIO6.
5GPIO5_IRQR/W1 = A level change has occurred on GPIO5.
4GPIO4_IRQR/W1 = A level change has occurred on GPIO4.
3GPIO3_IRQR/W1 = A level change has occurred on GPIO3.
2GPIO2_IRQR/W1 = A level change has occurred on GPIO2.
1GPIO1_IRQR/W1 = A level change has occurred on GPIO1.
0GPIO0_IRQR/W1 = A level change has occurred on GPIO0.
Note 1: Writing a “1” (one) to a bit clears the bit and enables the detection of the next level transition. If not masked
by the corresponding bit in the GPIO_MSK register, “1” in any bit in this register will force a “1” on the 8051
core’s external INT4 interrupt input.
SMSC DS – USB97C201Page 24Rev. 03/25/2002
PRELIMINARY
Table 16 – GPIO Interrupt Mask Register
GPIO_MSK
(0x9C- RESET=0xFF)GPIO INTERRUPT MASK REGISTER
BITNAMER/WDESCRIPTION
7GPIO7_MSKR/W1 = Prevents a high in the corresponding bit
in the GPIO_IRQ register from generating an
interrupt on the INT4 input to the 8051.
6GPIO6_MSKR/W1 = Prevents a high in the corresponding bit
in the GPIO_IRQ register from generating an
interrupt on the INT4 input to the 8051..
5GPIO5_MSKR/W1 = Prevents a high in the corresponding bit
in the GPIO_IRQ register from generating an
interrupt on the INT4 input to the 8051...
4GPIO4_MSKR/W1 = Prevents a high in the corresponding bit
in the GPIO_IRQ register from generating an
interrupt on the INT4 input to the 8051...
3GPIO3_MSKR/W1 = Prevents a high in the corresponding bit
in the GPIO_IRQ register from generating an
interrupt on the INT4 input to the 8051...
2GPIO2_MSKR/W1 = Prevents a high in the corresponding bit
in the GPIO_IRQ register from generating an
interrupt on the INT4 input to the 8051...
1GPIO1_MSKR/W1 = Prevents a high in the corresponding bit
in the GPIO_IRQ register from generating an
interrupt on the INT4 input to the 8051...
0GPIO0_MSKR/W1 = Prevents a high in the corresponding bit
in the GPIO_IRQ register from generating an
interrupt on the INT4 input to the 8051...
SMSC DS – USB97C201Page 25Rev. 03/25/2002
PRELIMINARY
Table 17 - Utility Configuration Register
UTIL_CONFIG
(9D RESET=0x00)UTILITY CONFIGURATION REGISTER
BITNAMER/WDESCRIPTION
7SRAMSWR/W1 = The 768 byte SRAM is located at 0x0400-
0x06FF in the Code Space, instead of
external Memory.
0 = The 768 byte SRAM is located at 0x04000x06FF in the XDATA space.
6ReservedR/WReserved. This bit should never be written to
a “1”.
5GPIO0_TOGR/W1 = GPIO0 Output Auto Toggle enabled.
0 = Disabled, normal operation occurs.
4GPIO4/ nWER/WGPIO4/SOF Output Select Mux
0 = GPIO4
1 = The IDE_nIOW signal is output.
3GPIO3/T1R/WP3.5 Timer 1 input trigger source
0 = GPIO3
1 = TBD
2GPIO2/T0R/WP3.4 Timer 0 input trigger source
0 = GPIO2
1 = TBD
1GPIO1/TXDR/WGPIO1/TXD Output Select Mux
0 = GPIO1
1 = P3.1
0GPIO0/RXDR/WP3.0 RXD/GPIO0 Input Select Mux
0 = RXD<=GPIO0
1 = RXD<='0'
Note 1: GPIO0, when used as an output, will automatically toggle with 1second period and 50% duty cycle if
GPIO0_TOG is high.
Table 18 – SRAM Data Port Register
SRAM_DATA
(0x9F- RESET=0x00)
BITNAMER/WDESCRIPTION
[7:0]SRAM_DATA
[7:0]
Table 19 – SRAM Address Register 1
SRAM_ADD1
(A1 RESET=0x00)
BITNAMER/WDESCRIPTION
[7:0]SRAM_ADD
[7:0]
R/WData to be read or written
R/WThis register contains lower bits
SRAM DATA PORT
REGISTER
from/to the buffer SRAM. The
address of the data is
determined by the
SRAM_ADD1/2 registers. Data
to be written will be done so
upon write of this register.
While reads of the register
always reflects the data at the
memory location.
SRAM ADDRESS REGISTER 1
of the address in the buffer
RAM that the SRAM_DATA
register reads or writes.
2CLKVALIDRReflects the state of the PHY CLKVALID signal. When 1,
indicates that the internal clocks are stable and can be
used instead of the ring oscillator.
1:0]ReservedRAlways reads “0”.
SRAM ADDRESS REGISTER 2
of the address in the buffer
RAM that the SRAM_DATA
register reads or writes.
Note 1: The 8051 may program itself to run off of an internal Ring Oscillator having a frequency range between 8 and
24MHz. This is not a precise clock, but is meant to provide the 8051 with a clock source, without running the
30MHz crystal oscillator or the PLL
Note 2: Switching between fast and slow clocks is recommended to sav e pow er.
Note 3: Clock switching can be done on the fly as long as both clocks are running. When switching, it takes a total of
six clocks (3 clocks of the original clock plus 3 clocks of the switching clock) to guarantee the switching.
Note 4: Time TBD is required from ROSC_EN=1 to MCUCLK_SRC=0.
SMSC DS – USB97C201Page 27Rev. 03/25/2002
PRELIMINARY
Table 22 - Wakeup Source 1 Register (INT2)
WU_SRC_1
(0XA0 – RESET=0x00)WAKEUP SOURCE 1
BITNAMER/WDESCRIPTION
[7:3]ReservedR/WReserved
2USB_ResetR/WThis bit is set when the SIE detects simultaneous logic lows on D+
and D- (Single-Ended 0) for 32 to 64 full speed bit times, or 4 to 8
low speed bit times (or 2.5<t<5.5us). The USB_Reset signal may be
as long as 10ms. SETUP tokens can be NAK'd for up to 10ms after
the Reset signal is released.
1ResumeR/WThis bit is set on detection of Global Resume state (when there is a
transition from the "J" state while in Global Suspend).
0EXT_INTRThis bit will be set if the ATA_IRQ bit of the ISR_0 register is set OR
if the 8051 INT4 signal (GPIO Interrupts) is high.
Note 1: The bits 1 and 2 in this register are cleared by writing a ‘1’ to the corresponding bit.
Note 2: Unmasked W akeup Source bits restart the 8051 when its clock is stopped. This restarts the Ring Oscillator
and crystal oscillator for the MCU to resume from <500µA operation.
Note 3: To initiate USB Remote Wakeup, the SIE_Resume bit should be used in the SIE_CONF register.
Table 23 - Wakeup Mask 1 Register
WU_MSK_1 (Note 1)
(0XA6 - RESET=0xFF)WAKEUP MASK 1
BITNAMER/WDESCRIPTION
[7:3]ReservedR This bit always reads “1”.
2USB_ResetR/WExternal wakeup event.
0 = Enabled
1 = Masked
1ResumeR/WExternal wakeup event.
0 = Enabled
1 = Masked
0EXT_INTR/WExternal wakeup event.
0 = Enabled
1 = Masked
Note 1: Interrupt events enabled by these bits are Ored and routed to the INT2 external interrupt input of the 8051
core.
SMSC DS – USB97C201Page 28Rev. 03/25/2002
PRELIMINARY
6.1.4.4 SIE & Buffer Control Registers
Table 24 –USB Address Register
USB_ADD
(0xA9 – RESET=0x00)USB ADDRESS REGISTER
BITNAMER/WDESCRIPTION
7ReservedRThis bit always reads a “1”.
[6:0]ADDR[6:0]R
This is the USB bus address that the device will respond to
when the EN bit is set. These bits are cleared for a
USB_RESET condition. This is automatically set during
enumeration by the SIE.
Table 25 – SIE Configuration Register
SIE_CONF
(0xAA - RESET=0x40)SIE CONFIGURATION REGISTER
BITNAMER/WDESCRIPTION
7ReservedRThis bit always reads a “0”.
6
[5:4]ReservedRThese bits always read “0”.
3ReservedR/WThis bit is reserved. It must never be written to a “1”.
2SPEEDR1 = High speed operation, if host is capable (See USB_STAT
1RESUMER/W1 = Forces the SIE to transmit Resume Signaling (“K” State) on the
0SUSPENDR/W1 = Forces the USB97C201’s PHY into power down mode for
DISCONNECT
R/W1 = Forces the PHY to the DISCONNECT state, removing the
RTERM resistor from the USB+ pin and forcing the PHY to ignore
signaling on the USB bus.
0= Normal operation.
register).
0 = Full Speed operation.
This bit is automatically set by the internal SIE during enumeration.
line, if this capability has been enabled by the
SET_FEATURE_REMOTE_WAKEUP command form the host. This
bit is set by the 8051 after it wakes up from a power down state, for
remote wakeup operation. The USB97C201 appropriately times the
duration of this signaling in accordance with the USB specifications.
This bit will not be automatically cleared at the end of the RESUME
signaling.
Note: In order for the USB97C201 to generate a remote wake-up,
the SUSPEND bit in this register MUST be cleared (0).
0 = Normal operation
SUSPEND operation and to enable the detection of resume events
and the setting of the RESUME interrupts in USB_STAT and
WU_SRC_1 registers.
0 = This bit is cleared by the 8051 during wake-up operations
(RESUME or Remote RESUME) to re-power the PHY and enable its
clocks.
Note: In order for the USB97C201 to generate a remote wake-up
using bit 1 of this register, this bit MUST be cleared (0).
Note 1: If a SETUP packet is received on Endpoint 0 that is not automatically handled by the SIE (See Section
6.2.36.2.1) :
1. Any STALL conditions will be cleared for EP0.
2. An interrupt is generated, if unmasked, by the SETUP bit in the ISR_0 register.
The reception of the packet will be indicated by the SETUP bits in the ISR_0 register being set. The pid
sequence is set to DATA-1 for both directions after a valid setup/DATA-0 transaction.
SMSC DS – USB97C201Page 29Rev. 03/25/2002
PRELIMINARY
Table 26 - USB Bus Status Register
USB_STAT
(0xAB - RESET=0x00)USB BUS STATUS REGISTER
BITNAMER/WDESCRIPTION
[7]ReservedRThis bit always reads “0”.
6EP2_ERRR/W1 = Indicates that a token in the opposite direction inferred
by the DIR bit of EP2_CTL register was received, ie an
unexpected IN or OUT token.
52.0R/W1 = Host is high speed capable. This bit is set if high speed
signaling is received from the host.
4USB_RESUMER/W1 = Indicates that RESUME signaling has been detected.
This is only valid if the USB97C201 is in the SUSPEND
state via bit 0 of the SIE_CONF register.
3USB_RESETR/W1 = Indicates that a USB Reset has been detected.
2ERRORR1 = Indicates that a USB Error has been detected. See the
USB_ERR register for details. This bit is cleared by clearing
the USB_ERR register.
1ReservedRThis bit always reads “0”.
0ReservedRThis bit always reads “0”.
The bits in this register (except bit 2) are cleared by writing a ‘1’ to the corresponding bit. These bits are ORed, if
unMASKED in the USB_MSK register, and drive a latch for the USB_STAT bit in the ISR_0 register.
Table 27 – USB Bus Status Mask Register
USB_MSK
(0xAC - RESET=0xFF)USB BUS STATUS MASK REGISTER
BITNAMER/WDESCRIPTION
[7]ReservedRThis bit always reads “1”.
6EP2_ERRR/W1 = Prevents generation of the USB_STAT bit in the ISR_0
register when the EP2_ERR bit is set in the USB_STAT
register.
52.0R/W1 = Prevents generation of the USB_STAT bit in the ISR_0
register when the 2.0 bit is set in the USB_STAT register.
4USB_RESUMER/W1 = Prevents generation of the USB_STAT bit in the ISR_0
register when the USB_RESUME bit is set in the
USB_STAT register.
3USB_RESETR/W1 = Prevents generation of the USB_STAT bit in the ISR_0
register when the USB_RESET bit is set in the USB_STAT
register.
2ERRORR/W1 = Prevents generation of the USB_STAT bit in the ISR_0
register when the ERROR bit is set in the USB_STAT
register.
1ReservedRThis bit always reads “1”.
0ReservedRThis bit always reads “1”.
Note1: The mask bits do not prevent the status in the USB_STAT register from being set, only from setting the
USB_STAT bit in the ISR_0 register.
SMSC DS – USB97C201Page 30Rev. 03/25/2002
PRELIMINARY
Table 28 – SIE Status Register
SIE_STAT
(0xB0 - RESET=0x00)SIE STATUS REGISTER
BITNAMER/WDESCRIPTION
[7]SET_STALLR/WSet to “1” if a SET_FEATURE_ENDPOINT_HALT command
is received on any endpoint by the SIE. Which endpoint is
STALLed can be determined by examining their CTL
registers.
6CLR_STALLR/WSet to “1” if a CLEAR_FEATURE_ENDPOINT_HALT
command is received on any endpoint by the SIE. Which
endpoint’s STALL condition is cleared can be determined
by examining their CTL registers.
5SET_CONFR/WSet to “1” if a SET_CONFIGURATION command is received
on endpoint 0 by the SIE and the resulting configuration is
set and reported in the USB_CONFIG register.
4ReservedRThis read only bit always returns the value of “0”.
3SET_INTFR/WSet to “1” if a SET_INTERFACE command is received on
endpoint 0 by the SIE.
2ReservedR-This read only bit always returns the value of “0”.
1SET_REMWUR/WSet to “1” if a SET_FEATURE_REMOTE_WAKE_UP
command is received on endpoint 0 by the SIE.
0CLR_REMWUR/WSet to “1” if a
CLEAR_FEATURE_ENDPOINT_REMOTE_WAKE_UP
command is received on endpoint 0 by the SIE.
Note: These bits are masked by the SIE_MSK register and OR’d to drive the INT3 interrupt line into the 8051 core.
They may be cleared writing a “1” to the bit location.
Note: The mask bits do not prevent the status in the SIE_STAT register from being set, only from driving the INT3
line of the 8051 core high.
SMSC DS – USB97C201Page 31Rev. 03/25/2002
PRELIMINARY
Table 30 – USB Configuration Number Register
USB_CONF
(0xAD - RESET=0x00)USB CONFIGURATION NUMBER REGISTER
BITNAMER/WDESCRIPTION
[7:4]ReservedRAlways returns a “0”.
{3:0}CONFIGRReflects the current configuration number of the
USB97C201 system as set by the host.
Table 31 – Endpoint 0 Receive Control Register
EP0RX_CTL
(0xAF - RESET=0x00)ENDPOINT 0 RECEIVE CONTROL REGISTER
BITNAMER/WDESCRIPTION
[7:4]ReservedRThis bit always reads “0”.
3DTOGRThis bit reflects the data toggle state of the last received
data token.
2STALLR/WWhen set to a “1”, EP0 will respond with the STALL
handshake to OUT tokens EXCEPT a SETUP, which it will
ACK unconditionally. Either the internal SIE or the user may
set this bit. Receipt of a SETUP packet or USB RESET
clears this bit. Writing a “0” to this bit has no effect.
1ReservedRThis bit always reads “0”.
0ENABLERReads 1 if EP0 Receive is enabled by SIE.
Table 32 – Endpoint 0 Transmit Control Register
EP0TX_CTL
(0xB1 - RESET=0x00)ENDPOINT 0 TRANSMIT CONTROL REGISTER
BITNAMER/WDESCRIPTION
7ReservedRThis bit always reads “0”.
6ReservedRThis bit always reads “0”.
5ReservedRThis bit always reads “0”.
4TXR/WWhen written with a “1”, allows the SIE to transfer data from
the buffer SRAM to EP0. OUT tokens will be NAK’d until the
transfer has been completed. It is cleared by the SIE when
transmission of the packet has been completed.
3ReservedRThis bit always reads “0”.
2STALLR/WWhen set to a “1”, EP0 TX will respond with the STALL
handshake to IN tokens. . Either the internal SIE or the user
may set this bit. Receipt of a SETUP packet or USB RESET
clears this bit. Writing a “0” to this bit has no effect.
1ReservedRThis bit always reads “0”.
0ENABLERReads “1” if EP0 Transmit is enabled by the SIE.
Table 33 – Endpoint 1 Receive Control Register
EP1RX_CTL
(0xB2 - RESET=0x00)ENDPOINT 1 RECEIVE CONTROL REGISTER
BITNAMER/WDESCRIPTION
[7:4]ReservedRThis bit always reads “0”.
3DTOGRThis bit reflects the data toggle state of the last received
data token.
2STALLR/WWhen set to a “1”, EP1 RX will respond with the STALL
handshake to OUT tokens. . Either the internal SIE or the
user may set this bit. Receipt of a “CLEAR FEATURE
ENDPOINT CLEAR” command for this endpoint or USB
SMSC DS – USB97C201Page 32Rev. 03/25/2002
PRELIMINARY
EP1RX_CTL
(0xB2 - RESET=0x00)ENDPOINT 1 RECEIVE CONTROL REGISTER
BITNAMER/WDESCRIPTION
RESET clears this bit. Writing a “0” to this bit has no effect.
1ReservedRThis bit always reads “0”.
0ENABLER/WEP1 Receive is enabled in the SIE if this bit is set to a “1”,
otherwise, it is disabled.
Table 34 – Endpoint 1 Transmit Control Register
EP1TX_CTL
(0xB3 - RESET=0x00)ENDPOINT 1 TRANSMIT CONTROL REGISTER
BITNAMER/WDESCRIPTION
7ReservedRThis bit always reads “0”.
6ReservedRThis bit always reads “0”.
5ReservedRThis bit always reads “0”.
4TXR/WWhen written with a “1”, allows the SIE to transfer data from
the buffer SRAM to EP1. Until the transmission or reception
is complete, OUT will be NAK’d. It is cleared by the SIE
when transmission of the packet has been completed.
3ReservedRThis bit always reads “0”.
2STALLR/WWhen set to a “1”, EP1 TX will respond with the STALL
handshake to IN tokens. . Either the internal SIE or the user
may set this bit. Receipt of a “CLEAR FEATURE
ENDPOINT CLEAR” command for this endpoint or USB
RESET clears this bit. Writing a “0” to this bit has no effect.
1ReservedRThis bit always reads “0”.
0ENABLEREP1 Transmit is enabled in the SIE if this bit is set to a “1”,
otherwise, it is disabled.
Table 35 – Endpoint 2 Control Register
EP2_CTL
(0xB4 - RESET=0x00)ENDPOINT 2 CONTROL REGISTER
BITNAMER/WDESCRIPTION
7DIRR/WSetting this bit to a “1” indicates that the data flow is from
the ATA interface to the SIE, a “0” indicates the opposite
direction. When a “1”, the SIE will set the EP2_ERR bit in
the USB_STATUS register if an OUT token is received.
When a “0”, the EP2_ERR bit set if the SIE receives an IN
token.
6RAMWR_
TOGVALID
5RAMWR_
TOGGLE
R/WIf this bit is set to a “1” when writes to this register occur,
then the value of bit 5 written to this register will have effect.
If cleared, then the values of bit 5, when this register is
written, is ignored. This bit always returns “0” on reads.
R/WWriting a “0” to this bit will enable writing of the 512 byte
SRAM A buffer and clear the RAMWRBC_A1/2 registers,
while writing a “1” will select loading of the SRAM B buffer
and clear the RAMWRBC_B1/2 registers. This bit indicates
which interleaved buffer is currently or was last written with
data. The RAMWRBC_A and RAMWRBC_B Registers
contain the byte counts for the last write to the A and B
input buffers, respectively. See Sections 6.4, 6.5, and 6.9
for more information. To avoid interrupting a transfer that is
in progress, it is important not to write this bit until it is
completed. Note that if AutoToggle mode is enabled by bit 3
of the ATA_CTL register, this bit will reflect that current
buffer being written(1=B, 0=A).
SMSC DS – USB97C201Page 33Rev. 03/25/2002
PRELIMINARY
EP2_CTL
(0xB4 - RESET=0x00)ENDPOINT 2 CONTROL REGISTER
BITNAMER/WDESCRIPTION
4RAMRD_
TOGGLE
3STALL_
RX
2STALL_TXR/WWhen set to a “1”, EP2 TX will respond with the STALL
1RAMRD_
TOGVALID
0ENABLERReads “1” if EP2 is enabled by the SIE in either direction.
WW riting a “0” to this bit will begin the output of the 512 byte
SRAM A buffer to either the SIE or the ATA interface,
depending on the value of the DIR bit in this register, while
writing a “1” will begin outputing of SRAM B buffer. See
Sections 6.4, 6.5, and 6.9 for more information. The
RAMRDBC_A and RAMRDBC_B Registers determine how
many bytes will be output from either the A or B SRAM
buffer, respectively. Writing this bit to a “1” will clear the
RAMRD_B bit in the ISR_0 register, while writing it to “0” will
clear the RAMRD_A bit in that register.
RUpon reads, this bit will reflect the current or last buffer
being read (1=B, 0=A).
R/WWhen set to a “1”, EP2 RX will respond with the STALL
handshake to all tokens. . Either the internal SIE or the user
may set this bit. This bit is only cleared when a SET
FEATURE ENDPOINT 2RX CLEAR or SET
CONFIGURATION command is received on EP0 from the
host, or by a USB reset.
handshake to all tokens. . Either the internal SIE or the user
may set this bit. This bit is only cleared when a SET
FEATURE ENDPOINT 2TX CLEAR or SET
CONFIGURATION command is received on EP0 from the
host, or by a USB reset.
R/WThis bit always reads “0”. If this bit is set to a “1” when
writes to this register occur, then the value of bit 4 written to
this register will have effect. If cleared, then the values of bit
4, when this register is written, is ignored.
Notes:
If the DIR bit is changed, then the RAMWR_TOGGLE bit must be written by the user to assure that the proper
buffer is selected. The user can NOT rely on reading the value of this bit to determine which buffer is active
immediately after changing the DIR bit.
Bit 2, above, will set the STALL condition for both TX and RX directions of EP2. If the host clears the stall in
either direction, then both direction’s STALL condition will be cleared. Bit 3 above will be reserved and always
read a “0”.
[7:0]COUNT[7:0]R/WBits 7 thru 0 the byte count of the packet to be transferred
from the SRAM. The packet is stored beginning at address
0x0300.
Table 48 – NAK Register (INT5)
NAK
(0xD7 - RESET=0x00)NAK REGISTER
BITNAMER/WDESCRIPTION
7NYET2RXR1 = indicates that an NYET has been sent to the host on
Endpoint 2 in response to an OUT token.
6NYET0RXR1 = indicates that an NYET has been sent to the host on
Endpoint 0 in response to an OUT token.
5NAK2TXR1 = indicates that an NAK has been sent to the host on
Endpoint 2 in response to an IN token.
SMSC DS – USB97C201Page 36Rev. 03/25/2002
PRELIMINARY
NAK
(0xD7 - RESET=0x00)NAK REGISTER
BITNAMER/WDESCRIPTION
4NAK2RXR1 = indicates that an NAK has been sent to the host on
Endpoint 2 in response to an OUT token.
3NAK1TXR1 = indicates that an NAK has been sent to the host on
Endpoint 1 in response to an IN token.
2NAK1RXR1 = indicates that an NAK has been sent to the host on
Endpoint 1 in response to an OUT token.
1NAK0TXR1 = indicates that an NAK has been sent to the host on
Endpoint 0 in response to an IN token.
0NAK0RXR1 = indicates that an NAK has been sent to the host on
Endpoint 0 in response to an OUT token.
Notes:
Any bit that is high in this register, if not masked by the corresponding mask bit in the NAK_MSK register will
generate INT5 to the 8051.
A bit in this register may be cleared by writing a “1” to it.
Table 49 – NAK Mask Register
NAK_MSK
(0xD9- RESET=0xFF)NAK MASK REGISTER
BITNAMER/WDESCRIPTION
7NYET2RXR/W1 = Prevents generation of the 8051 INT5 interrupt when the
NYET2RX bit is set in the NAK register.
6NYET0RXR/w1 = Prevents generation of the 8051 INT5 interrupt when the
NYET0RX bit is set in the NAK register.
5NAK2TXR/W1 = Prevents generation of the 8051 INT5 interrupt when the
NAK2TX bit is set in the NAK register.
4NAK2RXR/W1 = Prevents generation of the 8051 INT5 interrupt when the
NAK2RX bit is set in the NAK register.
3NAK1TXR/W1 = Prevents generation of the 8051 INT5 interrupt when the
NAK1TX bit is set in the NAK register.
2NAK1RXR/W1 = Prevents generation of the 8051 INT5 interrupt when the
NAK1RX bit is set in the NAK register.
1NAK0TXR/W1 = Prevents generation of the 8051 INT5 interrupt when the
NAK0TX bit is set in the NAK register.
0NAK0RXR/W1 = Prevents generation of the 8051 INT5 interrupt when the
NAK0RX bit is set in the NAK register.
Table 50 – USB Error Register
USB_ERR
(0xDA - RESET=0x00)USB ERROR REGISTER
BITNAMER/WDESCRIPTION
7ReservedRThis bit always reads a “0”.
6TOKENR/WW hen set, this bit indicates that an unexpected token has
been received on one of the device’s endpoints.
5ReservedRThis bit always reads a “0”.
4STALLR/WWhen set, indicates that a token has been received on a
endpoint of the device while that endpoint is in the STALL
condition.
3DTOGR/WWhen set, indicates that a data packet has been received
on one of the device’s endpoints that has an incorrect data
toggle.
2RXERRR/WWhen set, indicates that a packet has been received on one
of the device’s endpoint with an error in FS mode.
1ReservedRThis bit always reads a “0”.
0CRCR/WWhen set, indicates that a packet with an incorrect CRC
SMSC DS – USB97C201Page 37Rev. 03/25/2002
PRELIMINARY
USB_ERR
(0xDA - RESET=0x00)USB ERROR REGISTER
BITNAMER/WDESCRIPTION
has been received on an endpoint.
Note: Writing a “1” to a bit in this register will clear the bit.. If any bit is set in this register the USB_ERR bit is set in
the USB_STAT register.
Table 51 – MSB ATA Data Register
MSB_ATA
(0xDB - RESET=0x00)MSB ATA CONTROL/STATUS DATA REGISTER
BITNAMER/WDESCRIPTION
[7:0]D[15:8]R/WDuring 8051 writes to XDATA 0x31F0 (the ATA Drives
Control/Status register), data in this register represents the
MS byte of the 16 bit operation to this address. For a read
of 0x31F0, the MS byte data is returned in this register after
the PIO_COMPLETE bit is set in the ATA_CTL register. (the
data returned from the actual read of 31F0 should be
discarded)
Table 52 – LSB ATA Data Register
LSB_ATA
(0xDC - RESET=0x00)LSB ATA CONTROL/STATUS DATA REGISTER
BITNAMER/WDESCRIPTION
[7:0]D[7:0]R/WDuring 8051 reads to XDATA 0x31F1-7 and 33F6 (the ATA
Drive’s 8 bit registers), the actual data is returned in this
register after the PIO_COMPLETE bit is set in the ATA_CTL
register. During writes, this register is unused.
For 8051 read to XDATA 0x31F0, the LS byte of data is
returned in this register after the PIO_COMPLETE bit is set
in the ATA_CTL register. During writes, this register is
unused.
Table 53 – ATA Transfer Count Register 0
ATA_CNT0
(0xE1 - RESET=0x00)ATA TRANSFER COUNT REGISTER 0
BITNAMER/WDESCRIPTION
[7:0]D[7:0]R/WSee note below.
Table 54 – ATA Transfer Count Register 1
ATA_CNT1
(0xE2 - RESET=0x00)ATA TRANSFER COUNT REGISTER 1
BITNAMER/WDESCRIPTION
[7:0]D[15:8]R/WSee note below.
Table 55 – ATA Transfer Count Register 2
ATA_CNT2
(0xE3 - RESET=0x00)ATA TRANSFER COUNT REGISTER 2
BITNAMER/WDESCRIPTION
[7:0]D[23:16]R/WSee note below.
SMSC DS – USB97C201Page 38Rev. 03/25/2002
PRELIMINARY
Table 56 – ATA Transfer Count Register 3
ATA_CNT3
(0xE4 - RESET=0x00)ATA TRANSFER COUNT REGISTER 3
BITNAMER/WDESCRIPTION
[7:0]D[31:24]R/WSee note below.
Note: The ATA_CNT[3:0] register must be written with the byte count of the total ATA transfer to be made. Writing
the ATA_CNT0 register initializes the ATA block for the transfer and should be written last. Reading these registers,
will return the actual number of bytes remaining to be transferred. If the transfer is prematurely terminated or
aborted, then the ATA_ERR bit in the ATA_CTL register will be set.
Table 57 –ATA Control Register
ATA_CTL
(0xDD - RESET=0x00)ATA CONTROL REGISTER
BITNAMER/WDESCRIPTION
7
OUT_ CONTROL
6PIO COMPLETER/WThis bit is set once any PIO access to the external drive
5ATA_ABORTR/WSetting this bit to a “1” will abort any ATA transfer to/from
4ATA_ERRRA “1” on this bit indicates that an error has occurred during
3AUTO_TOGR/WWhen set to “1”, enables the automatic toggling between
2AUTO_TRANSR/WWhen set to a “1”, enables the automatic transfer mode of
1ReservedRThis bit always returns a “1”.
0EN0R/WPrimary Drive 0 UDMA Enable.
R/WSetting this bit to a “1” allows the IDE_SA[2:0], IDE_nIOR,
IDE_nIOW, IDE_nCS1, IDE_nCS0, IDE_DACK, and
IDE_D[15:0] pins operate normally. When cleared (“0”),
these pins are high impedance.
registers (31F0-31F7 & 33F6) has been completed (see
Section 6.3.2 for more information on PIO accesses). This
bit is cleared by writing a “1” to it. The value of the this bit is
mirrored in the ISR_1 register to allow and interrupt to be
generated, if desired. This bit is also cleared at the start of
any PIO access to the external drive registers.
the external device. The ATA_ERR bit will be set, also. It is
cleared upon initializing the next ATA transfer by writing a
value into the ATA_CNT0 register.
the ATA transfer/to/from the drive. It is cleared upon
initializing the next ATA transfer by writing a value into the
ATA_CNT0 register.
the A and B SRAM buffers when writing to the SRAM. See
Section 6.9 on page 50 for more information
operation. See Section 6.9 on page 50 for details. Writing
this bit to a “1”, automatically enables the automatic toggling
operation also, independent of the state of the AUTO-TOG
bit above.
1: Enable UDMA mode for primary channel drive 0.
0: Disable (default)..
Note: If an ATA_ERR occurs, the state of which buffers (A or B) are being used for reading or writing form/to the
ATA block are unchanged. The firmware may determine which buffer was being used by the ATA at the time of the
error by reading either bit 4 or bit 5 of the EP2_CTL register and determine how much of the transfer was completed
by reading the ATA_CNx registers.
These bit settings the Ultra DMA mode that the ATA
interface operates when Ultra DMA operation is enabled.
They therefore determine the minimum data write strobe
Cycle Time (CT) and minimum Ready to Pause time (RP).
are shown below:
000: CT= 267ns, RP= 333ns (Mode 0)
001: CT= 167ns, RP= 266ns (Mode 1)
010: CT= 133ns, RP= 200ns (Mode 2)
011: CT= 100ns, RP= 200ns (Mode 3)
100: CT= 66ns, RP= 200ns (Mode 4)
101 thru 111 reserved
ULTRA DMA TIMING MODES
Mode (Data
Strobe
Cycle Time)
Bit Settings000001010011100
(0xDF - RESET=0x00)IDE TIMING REGISTER
BITNAMER/WDESCRIPTION
[7:6]ISP[1:0]R/WIORDY Sample Point. This field selects the number of 30MHz
Mode 0
(~1267ns)
IDE_TIM
Mode 1
(~167ns)
Table 59 – IDE Timing Register
clocks (33ns/clock) between IDE_nIOx assertion and the first
IORDY sample point. In fast PIO timing mode (See bit 3
below), this sets the active period for the data strobe.
[5:4]RT[0:1]R/WRecovery Time. This field selects the minimum number of
30MHz clocks(33ns/clock) between the last IORDY sample
point and the next IDE_nIOx strobe. In fast PIO timing mode
(See bit 3 below), this sets the inactive period for the data
strobe.
1: Fast timing mode is enabled for non-UDMA DMA data. PIO
transfer to the IDE data port will run in compatible timing.
0: Both non-UDMA DMA and PIO data transfers to drive will
use the fast timing mode.
SMSC DS – USB97C201Page 40Rev. 03/25/2002
PRELIMINARY
IDE_TIM
(0xDF - RESET=0x00)IDE TIMING REGISTER
BITNAMER/WDESCRIPTION
2PPER/WPrefetch and Posting Enable.
1:Prefetch and posting to the IDE data port is enabled for the
drive.
0: Prefetch and posting is disabled for the drive .
1ISPER/WIORDY Sample Point Enable.
1: All accesses to the ATA I/O address range sample IORDY.
The IORDY sample point is specified by the “IORDY Sample
Point” field of this register.
0: IORDY sampling is disabled. The internal IORDY signal is
forced asserted guaranteeing that IORDY is sampled asserted
at the first sample point as specified by the “IORDY Sample
Point” field in this register.
0FTBR/WFast Timing Bank.
1: Accesses to the data port of the ATA IO address range
uses fast timings. PIO accesses to the data port use fast
timing only if bit 3 of this register is zero. Accesses to all nondata ports of the ATA I/O address range always use the 8 bit
compatible timings.
0: Accesses to the data port of the ATA I/O address range
uses the 16 bit compatible timing.
Note: the following settings should be used for the ISP, RT, DTE, and FTB bits for the various PIO and MWDMA
modes:
MODEISP[1:0]RT[1:0]FTBDTECOMMENT
PIO Mode 0001110ATA PIO cycle speed limited by 8051 data moves
PIO Mode 1011110ATA PIO cycle speed limited by 8051 data moves
PIO Mode 2-4101110ATA PIO cycle speed limited by 8051 data moves
MWDMA 000000xrequires compatibility mode timing to be used
MW DMA 110101x
MW DMA 210111x
SMSC DS – USB97C201Page 41Rev. 03/25/2002
PRELIMINARY
Table 60 –ATA Slew Rate Control A Register
ATA_SRCA
(0xE5 - RESET=0x00)ATA SLEW RATE CONTROL A REGISTER
BITNAMER/WDESCRIPTION
[7:6]SLEW 3R/WThese two bits are control inputs of the ATA pad for data
bits [15:12]. The bits can be used to vary the slew rate of
IDE_D[15:12] from minimum to maximum rate specified by
the ATA66 specification. The value 11b sets the slew rate
to be the maximum and the value of 00b sets the slew rate
to be the minimum.
[5:4]SLEW 2R/WThese two bits are control inputs of the ATA pad for data
bits [11:8]. The bits can be used to vary the slew rate of
IDE_D[11:8] from minimum to maximum rate specified by
the ATA66 specification. The value 11b sets the slew rate
to be the maximum and the value of 00b sets the slew rate
to be the minimum.
[3:2]SLEW 1R/WThese two bits are control inputs of the ATA pad for data
bits [7:4]. The bits can be used to vary the slew rate of
IDE_D[7:4] from minimum to maximum rate specified by the
ATA66 specification. The value 11b sets the slew rate to be
the maximum and the value of 00b sets the slew rate to be
the minimum.
[1:0]SLEW 0R/WThese two bits are control inputs of the ATA pad for data
bits [3:0]. The bits can be used to vary the slew rate of
IDE_D[3:0] from minimum to maximum rate specified by the
ATA66 specification. The value 11b sets the slew rate to be
the maximum and the value of 00b sets the slew rate to be
the minimum.
Table 61 –ATA Slew Rate Control B Register
ATA_SRCB
(0xE6 - RESET=0x00)ATA SLEW RATE CONTROL B REGISTER
BITNAMER/WDESCRIPTION
[7:2]ReservedRAlways returns “0” on reads
[1:0]SLEW4R/WThese two bits are control inputs of the ATA pad for
STROBE signaling during Ultra ATA writes to disk. The bits
can be used to vary the slew rate of STROBE from
minimum to maximum rate specified by the ATA66
specification. The value 11b sets the slew rate to be the
maximum and the value of 00b sets the slew rate to be the
minimum.
6.2 SIE Block
The SIE is a USB low-level protocol interpreter. The SIE controls the USB bus protocol, packet generation /
extraction, PID / Device ID parsing, and CRC coding / decodingwith autonomous error handling.
Parallel-to-serial / serial-to-parallel conversion, bit stuffing, and NRZI coding / decoding are handled in the PHY
block.
It is capable of operating either in USB 1.1 or 2.0 compliant modes. Unlike the normal 97Cxxx ser ies SI Es, i t has
more autonomous protocol handling functions like stall condition clearing on setup packets, suspend / resume / reset
conditions, and remote wakeup. It also autonomously handles the error conditions such as retry for CRC errors, Data
toggle errors, and generation of NYET, STALL, ACK and NACK depending on the endpoint buffer status.
During the power down state, the SIE clock is stopped. The SIE can asynchronously detect a USB Reset and/or
USB Resume condition and wakeup the 8051.
6.2.1 AUTONOMOUS USB PROTOCOL
SMSC DS – USB97C201Page 42Rev. 03/25/2002
PRELIMINARY
6.2.1.1 Automatic Retries - Out Transactions
If a packet is received with an incorrect data toggle, the SIE will ACK, but ignores the data packet. If more than 64
bytes received on EP0RX or EP1RX, or if more than 512 bytes are received on EP2, the USB SIE will ignore the
packet and set the appropriate “STALL” bit until the host acknowledges the condition by sending a “CLEAR
FEATURE ENDPOINT STALL” command for that endpoint, or, in the case of Endpoint 0, a SETUP is recieved.
If an error occurs during an OUT transaction, the USB97C201 reloads its USB SIE read pointer back to the
beginning of the buffer. The host then sends another OUT token and retransmits the packet.
Once the packet has been successfully received, the appropriate interrupt bit is set in ISR_0 or ISR_1. The SIE can
handle any number of back-to-back retries, but the host determines how many times a packet is retried.
If an endpoints’s buffer or buffers (in the case of EP2) are full, then the SIE sends a NACK. A TX direction Endpoint
will NAK all OUT packets.
6.2.1.2 Automatic Retries - In Transactions
If an timeout (No response from the host / lost ACK) occurs during an IN transaction, the USB97C201 reloads its
USB SIE side buffer read pointer back to the beginning of the failed packet. The host then sends another IN token
and the SIE re-transmits the packet with the same data toggle PID.
Once the host has successfully received the packet (only upon ACK received by SIE), the appropriate interrupt bit is
set in ISR_0 or ISR_1. The SIE can handle any number of back-to-back retries, but the host determines how many
times a packet is retried.
Upon reception of a SETUP token followed by the 8 byte DATA-0 packet on EP0, the internal DTOG bit for both
EP0RX and EP0TX are set to one.
6.2.1.3 Packet Lengths
The maximum packet length of an endpoint is fixed and 64 bytes for EP0 and EP1, and is 512 bytes for EP2 in HS
mode and 64 bytes in FS mode. For IN transactions, the USB97C201 will send the bytes in the buffer to the host.
For all OUT packets, the number of bytes received in the packet is indicated to the 8051 through the
Register of the respective endpoint.
BYTE COUNT
6.2.2 USB EVENTS
There are several events, which cause different parts of the SIE to be initialized. The following is the list of events
and the respective actions.
6.2.2.1 Reset
A reset via the external nRESET pin causes the following:
1. All endpoints are disabled, all SIE endpoint buffers are cleared, all stall conditions, and all registers clear to their
default state.
2. If USB97C201 was in power down state, then it is cleared.
3. The external crystal oscillator is allowed to run.
6.2.2.2 USB Bus Reset
USB Bus Reset is recognized only when the clocks are running. If the device is in SUSPEND mode with the clocks
stopped, a USB RESET will be first recognized as a RESUME event and if the WU_SRC1 bit for RESUME is
unmasked, will restart the clocks. The USB RESET can only then be detected. Upon recognition it causes the
following:
1. All SIE endpoint buffer byte count registers are cleared, all stall conditions, the SETUP bit, SETUP_DELAY bit,
SIE_SUSPEND, SIE_RESUME are cleared. The PID sequencers, internal DTOG are reset for all endpoints
2. The following registers will be set to their POR values: USB_ADD, SIE_STAT, USB_CONF, EP0RX_CTL,
EP0TX_CTL, EP1RX_CTL, EXP1TX_CTL, EP2_CTL, EP0RX_BC, EP0TX_BC, EP1RX_BC, EP1TX_BC,
RAMWRBC_A1, RAMWRBC_A2, RAMWRBC_B1, RAMWRBC_B2, RAMRDBC_A1, RAMRDBC_A2,
RAMRDBC_B1, RAMRDBC_B2, NAK, USB_ERR.
3. The seven bit USB device address is cleared.
4. Both EP0TX and EP0RX endpoints are enabled.
5. If the USB_RESET and USB_STAT bits are unmasked, then a ISR_0 interrupt (USB_STAT) is generated to the
8051 and the USB_RESET bit in the WU_SRC1 register will also be set and will generate an interrupt if
unmasked.
SMSC DS – USB97C201Page 43Rev. 03/25/2002
PRELIMINARY
6.2.2.3 Suspend
This is detected by the SIE when the idle condition on the USB bus occurs for a duration of more than 3ms. Upon
detection of this condition via the SUSPEND bit of ISR_1, the 8051 will place the USB97C201 into a low power mode
via the USB_SUSPEND bit and enter into a power down state.
6.2.2.4 Setup token Arrival
When a SETUP token is recognized, the following sequence happens.
1. Independent of the state of SETUP bit, the setup data packet is received on EP0RX and ACK is sent for the
received setup packet.
2. The stall condition, if any, for EP0TX and EP0RX are cleared, as well as the EP0RX_BC and EP0TX_BC
registers and the TX bit of EP0_CTL register .
3. The internal DTOG bit for both EP0TX and EP0RX are set to one.
4. The EP0RX_BC register is cleared, allowing the subsequent data packet( if not zero length) to be written into
the start of the buffer.
5. The SETUP bit in ISR_0 register is set. Until the SETUP bit is cleared by the 8051, all OUT packets to EP0RX
are NACKed.
6.2.2.5 Resume
This global resume condition is recognized asynchronously and does not require the SIE clock running. Upon
recognition it causes the following. A USB RESET will be interpreted as a RESUME if it occurs while clocks are
stopped.
If the USB_RESUME and USB_STAT bits are unmasked, then a ISR_0 interrupt (USB_STAT) is generated to the
8051. Also the RESUME bit in the WU_SRC1 register will be set and can generate an interrupt, if unmasked.
The SIE_SUSPEND bit is cleared automatically and the SIE resumes from power down state.
6.2.2.6 Remote Wakeup
When the 8051 is required to go into power down state, the SIE_SUSPEND should be set. W hen a remote wakeup
event is desired, the 8051 is responsible to clear the SIE_SUSPEND, and set the SIE_RESUME bits.
6.2.3 STANDARD DEVICE REQUESTS
The SIE also handles autonomously several standard device requests received on Endpoint 0.
These requests are:
These events (except SET_ADDRESS, GET_INTERFACE (always returns 0), and GET_CONFIGURATION) are
indicated in the SIE_STATUS register, which can generate an interrupt to the 8051 core’s INT3 line. The
configuration number, resulting from the SET_CONFIGURATION command is stored in the USB_CONF register.
This value is used when reporting to the host on a GET_CONFIGURATION Command, also. All other device
requests are handled normally and will generate the SETUP status bit when received.
6.2.4 SIE CONFIGURATIONS
Upon POR or the detection of USB RESET, the Configuration of the device is set to “0”. The host may change its
Configuration state to “1” with a “SET CONFIGURATION” command on Endpoint 0. All other Configuration number
requests by the host will result in a STALL condition on Endpoint 0. For Configuration 0, only Endpoint 0 RX and TX
are enabled, while all endpoints are enabled for Configuration 1.
6.3 IDE Controller Description
This is an ATA-66 core. The PIO I/O address range for the ATA interface in the 8051 XDATA space is decoded in
the range of 0X31F0 to 0X31F7, and 0x33F6
Transfers to/from SRAM will occur from/to the 16 bit ATA Data Port at CS0=1, CS1=0, A2-A0= 0.
SMSC DS – USB97C201Page 44Rev. 03/25/2002
PRELIMINARY
The most significant byte of transfer to/from this Data Port is available to the 8051 via the register located in SFR
space at 0xDB. Writes to 0x31F0 in the XDATA space by the 8051 would write both the contents of this register and
the data in the MOVEX instruction as a 16 bit DWORD to the ATA Data Port. Similarly, reads by the 8051 of 0x31F0
will return the actual drive data for reading by the 8051 at 0xDB and 0xDC.
6.3.1 IDE CONFIGURATIONS
The USB97C201 supports only a single primary drive on the IDE interface.
6.3.2 PIO IDE OPERATIONS
The IDE controller includes both compatible and fast timing modes. The fast timing mode only applies to the IDE
data ports. All other transactions to the IDE registers are run in single transaction mode with compatible timings.
The IDE_TIM register permits different timing modes, from Multi-word DMA ATA Mode 0 to ATA Mode 2, to be
programmed for the drive. These modes range from 3MB/sec to 16MB/sec in terms of data transfer rate. The Ultra
ATA/66 synchronous DMA timing modes can also be applied to each drive by programming the ATA_CTL and
ATA_DMA registers. When a drive is enabled in Ultra DMA mode operation, the DMA transfers are executed with the
Ultra ATA timings. The PIO data transfers are still executed using compatible timings or fast timings when enabled.
PIO accesses are not directly made to the drive from the 8051 via its XDATA address space, but are timed by the
ATA controller to meet required drive timing. A read access is accomplished by first reading the XDATA address
location, ignoring the returned data, and then waiting for the PIO_COMPLETE bit to be set in the ATA_CTL register.
The actual data retrieved from the drive can then be read at LSB and MSB( if a 16 bit access to 31F0) ATA Data
registers in SFR space. Writes to the drive are done normally, directly to the XDATA address desired( the MSB ATA
Data register must be loaded first for the 16 bit writes to 31F0), but a subsequent write (or read) cannot be initiated
until the PIO_COMPLETE bit is set. This bit is reflected in the ISR_1 register to allow an interrupt to be generated, if
desired.
Startup Latency: If the IDE_SA[2:0] and IDE_nCS[1:0] lines are not set up, startup latency is incurred when a cycle
that accesses the IDE data port is decoded. Startup latency provides the setup time for assertion of IDE_SA[2:0] and
IDE_nCS[1:0] lines prior to assertion of the read and write strobes (IDE_nIOR and IDE_nIOW).
Cycle Latency: Cycle latency consists of the I/O command strobe assertion length and recovery time. Recovery time
is needed so that back-to-back transactions, which does not incur startup and shutdown latency, may occur on the
IDE interface without violating minimum cycle periods for the IDE interface. The command strobe assertion width
(IORDY Sample Point: ISP) for the fast timing mode is programmable in the ISP field of the IDE_TIM Register. The
recovery time (RCT) is programmable in the RCT field of the IDE_TIM Register.
If the IORDY is asserted when the IORDY sample point is reached, no wait states are added to the command strobe
assertion length. If IORDY is negated when the sample point is reached, additional wait states are added.
IORDY Masking: The IORDY signal can be ignored and assumed asserted at the first IORDY Sample Point (ISP)
through the IDE_TIM register.
Shutdown Latency: Shutdown latency is incurred after the IDE data transactions (either a non-empty write post
buffer to the IDE drive or an outstanding read prefetch cycles from the IDE drive) have completed and before other
IDE transactions can proceed. The latency provides hold time on the IDE_SA[2:0] and IDE_nCS[1:0] lines with
respect to the read and write strobes (IDE_nIOR and IDE_nIOW). Shutdown latency is set to 67ns in duration.
Table 62 shows the IDE cycle timings for various IDE transaction types.
Table 62 – IDE Transaction Timing
STARTUP
IDE TRANSACTION TYPE
Non-Data Port Compatible133ns367ns733ns67ns
Data Port Compatible100ns200ns467ns67ns
Fast Timing Mode (for Data Port
Accessing)
LATENCY
67ns267-167ns33-133ns67ns
ISPRCT
SHUTDOWN
LATENCY
6.3.3 PIO IDE DATA PREFETCHING AND POSTING
The IDE Controller can be programmed via the IDE_TIM registers to allow data to be posted to and prefetched from
the IDE data ports. Data prefetching is initiated when a data port read occurs. The read prefetch eliminates latency
to the IDE data ports and allows them to be performed back to back for the highest possible PIO data transfer rates.
SMSC DS – USB97C201Page 45Rev. 03/25/2002
PRELIMINARY
The first data port read of a sector is called the demand read. Subsequent data port reads from the sector are called
prefetch reads. The demand read and all prefetch reads must be of the same size (16 or 32 bits).
Data posting is performed for writes to the IDE data ports. The IDE CONTROLLER will then run the IDE cycle to
transfer the data to the drive.
6.3.4 DMA TRANSFERS
When enabled and supported by the device, DMA transfers are executed on the IDE interface, the chip selects
(IDE_nCS1/0) will be negated (high). When the IDE device asserts IDE_DRQ, the IDE Controller will return
IDE_nDACK to the IDE device when it is ready for the DMA data transfer. For multiword DMA transfers, the
IDE_nIOR or IDE_nIOW signal will free run at the programmed rate as long as IDE_DRQ remains asserted and the
IDE Controller is prepared to complete a data transfer. If IDE_DRQ has not de-asserted by the rising edge of
IDE_nIOR or IDE_nIOW signal multiword DMA is assumed and at least one more cycle will be executed. If
IDE_DRQ de-asserts before IDE_nIOR or IDE_nIOW is de-asserted while IDE_nDACK is asserted, it indicates that
one last data transfer remains for the current session. In this case, IDE_nDACK will be de-asserted one clock after
the IDE_nIOR or IDE_nIOW signal de-asserts. This allows the IDE controller to support both single and multiword
DMA cycles automatically.
The IDE device’s DMA request signal is sampled when the IO strobe is deasserted. If inactive, the DMA
Acknowledge signal is deasserted and no more transfers take place until DMA request is again asserted.
The controller transfers data to or from the EP2 buffer(s) responding to the DMA requests from the IDE device. The
controller will continue this until stopped or the byte count in ATA_CNT[3:0] reaches zero.
6.3.4.1 Completion of DMA Data Transfers
The IDE device signals an interrupt (IDE_IRQ) once its programmed data count has been transferred or an error
occurs. The IDE device will also deassert its DMA request signal, causing the IDE Controller to stop transferring
data. On reads from the IDE device, it will cause any data read from the device to be transferred to the EP2 buffer(s),
as they become available.
6.3.5 ULTRA ATA/66 SYNCHRONOUS DMA OPERATION
Ultra ATA/66 is a new IDE transfer protocol used to transfer data between a Ultra ATA/66 capable IDE controller and
Ultra ATA/66 capable IDE devices. Ultra DMA/66 utilizes a “source synchronous” signaling protocol to transfer data
at rates up to 66 Mbytes/sec.
6.3.5.1 Ultra ATA/66 Signals
Although no additional signal pins are required for Ultra ATA/66 operation, the operation of some standard IDE
controller pins are redefined during Ultra ATA modes of operation. The Ultra DMA/66 protocol defines three handshaking signals: STOP, STROBE and DMARDY. Table 63 shows the mapping of the redefined Ultra ATA/66 signals
onto the standard IDE controller pins.
STOP: STOP is always driven by the the USB97C201 and is used to request that a transfer be stopped or as an
acknowledgment to stop a request from IDE device. The IDE_nIOW signal is redefined as STOP for both read and
write transfers.
STROBE: This is a data strobe signal driven by the TRANSMITTER of a data transfer, which is either the IDE device
of a DMA Read transfer or the USB97C201 of a DMA Write transfer, on which data is transferred during each rising
and falling edge transition of the signal. The IORDY signal is redefined as STROBE for reads (when transferring data
from the IDE device to the USB97C201). The IDE_nIOR signal is redefined as STROBE for writes (transferring data
from the USB97C201 to the IDE device).
nDMARDY: This is a signal driven by the RECEIVER of a data transfer, which is either the USB97C201 of a DMA
Read transfer or the IDE device of a DMA Write transfer, to signal that the RECEIVER is ready to transfer data or to
add wait states to the current transaction. The IDE_nIOR signal is redefined as nDMARDY for reads (when
transferring data from the IDE device to the USB97C201). The IORDY signal is redefined as nDMARDY for writes
(transferring data from the USB97C201 to the IDE device).
Table 63 – ULTRA ATA/66 Control Signal Assignments
Note:
“Ultra ATA/66 Read Cycle”:
“Ultra ATA/66 Write Cycle”: Data transfers are from the USB97C201 to the IDE device.
Data transfers are from the IDE device to the USB97C201.
6.3.6 ULTRA ATA/66 OPERATION
After initialization, there are two primary operations provided by the Ultra ATA/66 controller: data transfers and cyclic
redundancy checking (CRC).
6.3.6.1 Initialization
Initialization includes enabling and performing proper set up on the USB97C201and the IDE device. For the
USB97C201, it is necessary to enable Ultra ATA/66 mode for the IDE device and setting up the Ultra ATA/66 cycle
timings through the ATA_DMA register. The USB97C201 supports five timing modes: Mode 0 (120ns cycle time),
Mode 1 (80 ns cycle time), Mode 2 (60ns cycle time), Mode 3 (45ns cycle time), and Mode 4 (30ns cycle time).
6.3.6.2 Data Transfer Operation
The USB97C201 and the Ultra ATA compatible IDE device control the transfer via the Ultra ATA protocol. The
actual data transfer consists of three phases, a start-up phase, a data transfer phase, and a burst termination phase.
1)
Start-Up Phase: The IDE device begins the start-up phase by asserting DRQ signal. When ready to begin the
transfer, the USB97C201 will assert nDACK. When nDACK is asserted, the USB97C201 will drive CS0/1
inactive, and A0-A2 low.
For Write cycles, the USB97C201 will deassert STOP, wait for the IDE device to assert nDMARDY and then
drive the first data word and the STROBE signal.
For Read cycles, the USB97C201will tristate the data lines, deassert STOP, and assert nDMARDY. The
IDE device will then drive the first data word and the STROBE signal.
2)
Data-Transfer Phase: The burst data transfer continues with the data source (Writes: USB97C201, Reads: IDE
devices) providing data and toggling STROBE. Data is transferred (latched by receiver) on each rising and
falling edge of STROBE.
The source can pause the burst stream by holding STROBE high or low, resuming the burst stream by
again toggling STROBE.
The receiver can pause the burst stream by negating the nDMARDY and resumes the transfers by
asserting nDMARDY.
The USB97C201 may pause a burst transaction in order to toggle internal data buffer, or to prevent a buffer over or
under flow condition, resuming once the condition has cleared.
1)
Termination Phase: Either the source or the receiver can terminate a burst transfer. A burst termination
consists of a Stop Request, Stop Acknowledge and transfer of CRC data.
The USB97C201 can stop a burst by asserting STOP, with the IDE device acknowledged by deasserting
DRQ.
The IDE device stops a burst by deasserting DRQ and the USB97C201 acknowledges by asserting STOP.
The source then drives the STROBE signal to a high level. The USB97C201 then drive the CRC value onto
the data lines and deassert nDACK. The IDE devices will latch the CRC value on the rising edge of nDACK.
The USB97C201 will terminate a burst transfer if a Programmed I/O (PIO) cycle is executed to the IDE channel
currently running the burst, or upon transferring the last data from the final PRD.
At the completion of the entire transfer process, the IDE device will issue an interrupt, setting the ATA_IRQ bit and
forcing the remaining data to be sent to host on read operations.
Cyclic Redundancy Checking (CRC-16) is used for error checking on Ultra ATA/66 transfers. The CRC value is
calculated for all data by both the USB97C201 and the IDE device over the duration of the DMA burst transfer
segment. This segment is defined as all data transferred with a valid STROBE edge from DACK assertion to nDACK
deassertion. At the end of the transfer burst segment, the USB97C201 will drive the CRC value onto the D[15:0]
signals. The value is then latched by the IDE device on deassertion of nDACK. The IDE device compares the
USB97C201 CRC value to its own and reports an error if there is a mismatch.
6.4 SRAM Buffers
1.25K Bytes of Buffer SRAM are provided. The Memory Map of the buffers are given below:
Note: The above SRAM address in the table refers to the BYTE location within the SRAM. The SRAM is actually
physically organized as a 32 bit wide memory.
The buffers used for EP2 is organized as two 512 byte buffers: A and B. The A buffer has its address starting at
0X100, while the B is at address 0X300.. Byte counts for data received or to be transmitted is contained in the
RAMWRBC_A/B and RAMRDBC
bit in the EP2 Control register. If DIR=0 then data flow is from the SIE to SRAM and from the SRAM to the ATA
interface. If DIR=1 the data flow is in the opposite direction. Unlike EP0 and EP1, data for both directions can not be
simultaneously buffered in the SRAM for EP2. However, the dual buffers and automatic transfer operation (see
Section 6.9) allow for sustained 480Mbps transfers across the USB97C201.
_A/B register sets, respectively. The direction of data flow is determined by the DIR
6.5 8051 Options
The following 8051 core options are included:
256 SRAM in SFR space
Three timers
Single serial port
Extended external inputs (INT2-13)
External program memory and external data bus (XDATA) are pinned out as a common bus.
6.6 Address Multiplexing
Access to the SRAM for the three access points, ie SIE, ATA DMA, or 8051, is via a time division multiplexing
scheme (See Section 6.7). Each of the above blocks have access to read or write the SRAM during one of four subperiods (the fourth period being reserved for future expansion/idle) of a four phase 15 Mhz clock( ie 60 Mhz slice
clock). The values set in the EPx_BUFx , and IN_BUFx, or OUT_BUFx (depending on the direction set for EP2)
control the address counter for accesses by the EPs during their time-slice.
The IN_BUFx or OUT_BUFx (again,depending on the direction of EP2) controls the address for ATA access and
SRAM_ADDx does so for the 8051 accesses.
Which endpoint has access during the SIE’s time-slice is determined by the SIE, ie depending on what endpoint is
currently active on the USB bus. Since accesses occur at 15Mhz using DWORDs (32bits), this process is capable of
real time concurrency with the USB bus and does not require additional buffering in the SIE. Even if a received
packet is ultimately discarded, all that is required to do so is simply not generate the completion interrupt for that
endpoint. Similarly for the transmit process, allowing re-transmission.
SMSC DS – USB97C201Page 48Rev. 03/25/2002
PRELIMINARY
6.7 SRAM Time Multiplexer Operation
The SRAM access, read or write, occurs in four sequential phases, Ø0-3. These periods are 16.666ns long (60Mhz)
and are non-overlapping. Data to/from the SRAM are buffered by local DWORD latches close to the SRAM to
minimize high-speed bussing. The rest of the USB97C201 subsystems access these latches during the phases
when they are NOT being used to transfer data to/from the SRAM.
6.7.1 PHASE 0 (Ø0)
During this phase, the SIE has access to the SRAM through its associated DWORD latches.
If data from EP0 or EP1 is ready (ie either a full DWORD or the end of a packet has been received), this data will be
written into the appropriate buffer address space and the associated EPxRX_BUF register incremented to reflect the
amount of buffer used to this point. If data to EP0 or EP1 is required by the SIE, it will load the data from the SRAM
into the DWORD latch whose address is determined by an incrementing address counter. This counter will be
compared against the EPx_TX register value, to determine if the buffer transfer has been completed.
If the DIR bit in EP2_CTL is “0”, and data is requested by the SIE for transmission to the host on EP2, the TOKEN
error bit in the USB_ERR register will be set and no other action occurs. If data is received by the SIE on EP2 (IN
tokens) and either a full DWORD or EOP has been received, then this data will be written into either the SRAM A or
SRAM B buffer space, as appropriate, and the associated
If the DIR bit in EP2_CTL is “1”, and data is received by the SIE from the host on EP2, the TOKEN error bit in the
USB_ERR register will be set and no other action occurs. If data to EP2 is required by the SIE from the SRAM, the
data will be loaded in the DWORD latch from the A or B buffer space, as appropriate. The SRAM data address will
be determined by an incrementing address counter which will be compared against the RAMRDBC_A/B registers’
value to determine if the buffer transfer has been completed.
6.7.2 PHASE 1 (Ø1)
The ATA interface block has access to the SRAM via a DWORD latch during this phase.
I
f the DIR bit in EP2_CTL is “1”, when either a full DWORD or end of DMA has been received by the ATA interface
from the ATAPI/ATA device and loaded in to the DWORD latch, it will be written into either the A or B buffer space,
as appropriate, and the associated
RAMWRBC_A/B registers incremented.
RAMWRBC_A/B registers incremented.
If the DIR bit in EP2_CTL is “0”, data will be loaded in the DWORD latch from the A or B buffer space, as
appropriate, when the ATA interface requires data to be sent to the ATAPI/ATA device. The SRAM data address will
be determined by an incrementing address counter, which will be compared against the RAMRDBC_A/B registers’
value to determine if the buffer transfer has been completed.
6.7.3 PHASE 2 (Ø2)
During this phase, the DWORD latch that interfaces to the SRAM_DATA register will be normally repetitively loaded
with data READ from the SRAM at the address determined by the higher order bits of the SRAM_ADD1/2 register.
The 8051 can read this data with a read to the SRAM_DATA port. Bits 0&1 of the SRAM_ADD1 register will
determine the byte read of the DWORD latch.
In order to write data from the 8051 to the SRAM, the 8051 will write the data into the SRAM_DATA register. The
sub-byte of the DWORD latch determined by bits 0 & 1 of the SRAM_ADD1 register will be updated, and the entire
DWORD will be written to the SRAM at the address determined by the higher order address bits of the
SRAM_ADD1/2 registers during the next Ø2 interval. Subsequently, it will return to reading the SRAM data into the
DWORD latch on each Ø2 interval. This allows single byte modifications of the the 32 bit wide SRAM to be executed
by the 8051.
6.7.4 PHASE 3 (Ø3)
Phase 3 is an idle period during which no accesses occur to the SRAM. This period is reserved for future expansion
in derivative products to allow another high speed access path for additional IO.
6.8 EP2 SRAM Buffer Operation
In order to illustrate the operation of the buffering and the interactions between the SIE and ATA control blocks and
the firmware, the following scenario will be explained in detail in a timeline format for operation NOT using the Auto
Toggle or Auto Transfer features (ie totally firmware controlled):
1. Endpoint 2 is currently receiving data (ie a file segment) from the host for transfer to the ATA interface (DIR bit
of EP2_CTL = 0). The SRAM B buffer assigned to EP2 has just been filled with data from the SIE (ie a max
packet has been received).
SMSC DS – USB97C201Page 49Rev. 03/25/2002
PRELIMINARY
2. Endpoint 2 will be receiving more data (short packet, ie end of file segment) followed by a OUT packet from the
host on the control endpoint (EP0) requesting data. Data has already been placed in the SRAM EP0 TX Buffer,
its length loaded into the
Phase 0 (Ø0) will refer the 60MHz sub-period that the SIE has access to the SRAM, while Ø1 will be that for the ATA
interface and Ø2 will be for the 8051 (Ø3 is idle and reserved).
During one of the Ø0 periods, the SIE finishes loading the last of the packet data into the B buffer. RAMWR_B
interrupt bit is set notifying firmware of completion of packet. Assuming that the RAMWR_A=0 (the data in the A
SRAM buffer has been previously transferred), the RAMWR_TOGGLE bit is written to a “0” by the firmware, which
clears the RAMWRBC_A1/2 registers and directs the next data received from EP2 to the A buffer space in SRAM.
Firmware reads RAMWRBC_B1/2 to determine packet size, loads value into RAMRDBC_B1/2 register. The
RAMRD_TOGGLE bit of EP2_CTL is written by the firmware with a “1” which will begin the transfer of the B buffer to
ATA interface on the next Ø1 period.
On subsequent slices, the next DWORD of the incoming data packet from the host is loaded into the A buffer space
on Ø0 from the SIE, auto-incrementing the RAMWRBC_A1/2 register values. On Ø1 slices, the data from the B
buffer space is output to the ATA interface (appropriately flow controlled by that interface), and incrementing a
counter which is compared to the RAMRDBC_B1/2 registers to determine if the transfer is completed. During this
time, the SIE receives an IN on EP0. During the next Ø0 periods, and until the final transmission of the packet data
to the SIE is completed, data is read from the SRAM into the SIE for EP0 in response to INs. The writing of the A
buffer by the SIE on Ø0 periods will then resume with the reception of OUTs on EP2.
Assuming the incoming data completes loading into the A buffer space, before the B buffer is transferred to the ATA
interface, the RAMWR_A interrupt will be generated before the RAMRD_B interrupt. The firmware will then wait until
the RAMRD_B interrupt occurs, loads the RAMRDBC_A1/2 register with the count from the RAMWRBC
registers, flips the buffers (ie RAMRD_TOGGLE=0, RAMWR_TOGGLE=1), and clears the RAMWR_B bit (allowing
the reuse of the B buffer area).
EP0TX_BC register, and the TX bit of the EP0TX_CTL register written to a “1”.
_A1/2
On subsequent Ø0 slices, the SIE will read (for IN tokens) or write (for OUT tokens) the appropriate SRAM buffer
according to which EP is being accessed, if any, while the USB97C201 transfers the A buffer to the ATA interface
during Ø1. When an OUT packet on EP0 is received, the data in the SRAM will be transferred to the SIE on
subsequent Ø0 slices, DWORD at a time until completed.
6.9 EP2 Automatic Buffer Operations
Automatic operation of the interleaved SRAM buffers exists in two degrees: Automatic toggling of input buffers and
automatic transfer of input and output buffer data to/from the SIE and ATA interface. These features may be disabled
via bits in the ATA_CTL register.
6.9.1 RECEIVE AUTO-TOGGLE
If the AUTO_TOG bit of the ATA_CTL register is set to a “1”, then receive auto-toggling between the A and B buffers
for writes to the SRAM is enabled. Figure 3 illustrates the auto-toggle of the receive buffers.
SMSC DS – USB97C201Page 50Rev. 03/25/2002
PRELIMINARY
POR
RAMWR_A=0
RAMWR_B=0
RAMWR_
YesNo
TOGGLE=0?
RAMWR_A=1
RAMWR_B=1
(IN FLOW CONTROL
ACTIVE)
RAMWR_
YesNo
TOGGLE=0?
B
SRAM Data
Received?
A Buffer Output
Completed?
Yes
RAMWR_A=0
RAMWR_B=1
RAMWR_
TOGGLE=0
B Buffer Output
Completed?
No
A
SRAM Data
Received?
No
CLR
YesYes
RAMWR_B
CLR
RAMWR_TOGGLE;
(IN FLOW CONTRO L OFF)
Yes
CLR RAMWR_A;
RAMWR_TOGGLE=1;
(IN FLOW CONTROL
OFF)
CLR RAMWR_B;
CLEAR
RAMWR_A
Yes
Yes
RAMWR_A=1
RAMWR_B=0
RAMWR_
TOGGLE=1
A Buffer Output
Completed?
No
B
SRAM Data
Received?
No
NoNo
A
SRAM Data
Received?
NoNo
YesYes
B Buffer Output
Completed?
FIGURE 3 - RECEIVE BUFFER OPERATION
Trapezoidal shapes indicate actions performed by the firmware. The hardware state machine is responsible for
automatically changing the state of RAMWR_TOGGLE according to the state change of the RAMWR_B and
RAMWR_A bits, as shown in
Table 65. These bits are normally set by the USB97C201 upon completion of loading
the A or B SRAM buffer and are normally cleared by the firmware (except when Auto Transfer operation is enabled,
see Section 6.9.3).
Note that when both buffers are “full”, ie RAMWR_A and RAMWR_B status bits are BOTH set, that the
RAMWR_TOGGLE is not altered and that flow control is initiated on the input source. If this source is the SIE, it will
NYET or NAK further OUTs. If it is the ATA interface, nDAK will not be asserted in response to DRQ and data not
clocked in to the SRAM.
Figure 4 illustrates the operation of the transmit A and B buffers.
SMSC DS – USB97C201Page 51Rev. 03/25/2002
PRELIMINARY
POR
RAMRD_A=1
RAMRD_B=1
OUTPUT
FLOW CONTROL
ACTIVE
No
RAMRD_
TOGGLE
Written?
Yes
OUTPUT
FLOW CONTROL
INACTIVE
RAMRD_
TOGGLE=
0?
No
RAMRD_B=0
No
RAMRD_
TOGGLE=
0?
Yes
RAMRD_A=0;
Begin
Output A Buffer
SRAM Data
RAMRD_
TOGGLE
Written?
No
Output
Completed?
Yes
RAMRD_A=1
RAMRD_B=0?
Yes
No
Yes
Yes
No
RAMRD_B=0;
Begin
Output B Buffer
SRAM Data
RAMRD_
TOGGLE
Written?
No
No
Output
Yes
Completed?
Yes
RAMRD_B=1
RAMRD_A=0?
Yes
RAMRD_
TOGGLE=
1?
No
RAMRD_A=0
Yes
FIGURE 4 - TRANSMIT BUFFER OPERATION
Transmit buffer operations are always initiated by writing the RAMRD_TOGGLE bit in the EP2 Control register.
Output flow control to the device receiving data from the SRAM buffer is active once data in both buffers has been
transferred. If the destination is the SIE, then it will NYET or NAK further INs. If it is the ATA interface, nDAK will not
be asserted in response to DRQ data will not be clocked out.
6.9.3 AUTOMATIC TRANSFER OPERATION
If the AUTO_TRANS bit is set in the ATA_CTL register, then automatic manipulation of the RAMWR_TOGGLE,
RAMRD_TOGGLE, RAMWR_B, and RAMWR_A bits is executed by a state machine to allow continuous streaming
of the data between EP2 and the ATA DMA interface. Automatic transfer of byte counts between the
RAMWRBC_A/B and RAMRDBC_A/B registers is also implemented. This is illustrated in Figure 5.
Note: If the count in RAMWRBC_A/B is zero, no transfer will occur. This is likely to happen on transfers from the SIE
to the ATA at the very end of the transfer.
SMSC DS – USB97C201Page 52Rev. 03/25/2002
PRELIMINARY
AUT0_TRANS->1
RAMWR_A=0
RAMWR_B=0
RAMRD_A=1
RAMRD_B=1
RAMWR_A=1
& count<>0 ?
No
XFER COUNT
No
Yes
RAMWRBC_A1/2 ->
RAMRDBC_A1/2;
RAMRD_TOGGLE=0;
RAMWR_TOGGLE
=1
& CLR RAMWR_B
RAMWR_B=1
& count<>0 ?
XFER COUNT
RAMWRBC_B1/2 ->
RAMRDBC_B1/2;
RAMRD_TOGGLE=1
RAMRD_B=1?
YesCLR RAMWR_B
RAMWR_A=1
& count<>0 ?
RAMRD_B=1?
Yes
Yes
NoNo
Yes
No
No
RAMRD_A
RAMWR_B=1
& count<>0 ?
RAMRD_A
FIGURE 5 - AUTOMATIC DATA TRANSFER OPERATION
The trapezoidal shapes represent actions taken by the state machine.
Yes
=1?
NoNo
Yes
Yes
=1?
CLR
RAMWR_A
RAMWR_TOG
GLE=0 &
CLR
RAMWR_A
SMSC DS – USB97C201Page 53Rev. 03/25/2002
PRELIMINARY
7.0 DC PARAMETERS
O
O
MAXIMUM GUAR ANTEED RATING S
Operating Temperature Range...........................................................................................................................0oC to +70oC
Storage Temperature Range...........................................................................................................................-55
Lead Temperature Range (soldering, 10 seconds).....................................................................................................+325
o
to +150oC
o
Positive Voltage on any pin, with respect to Ground........................................................................................................5.5V
Negative Voltage on any pin, with respect to Ground.................................................................................................... -0.3V
*Stresses above the specified parameters could cause permanent damage to the device. This is a stress rating only
and functional operation of the device at any other condition above those indicated in the operation sections of this
specification is not implied.
Note: When powering this device from laboratory or system power supplies, it is important that the Absolute Maximum
Ratings not be exceeded or device failure can result. Some power supplies exhibit voltage spikes on their outputs when
the AC power is switched on or off. In addition, voltage transients on the AC power line may appear on the DC output.
When this possibility exists, it is suggested that a clamp circuit be used.
DC ELECTRICAL CHARACTERISTICS (TA = 0°C - 70°C, V
DDIO, VDDA
= +3.3 V ± 10%, V
DD, VDDP
= +2.5 V ± 10%,)
PARAMETERSYMBOLMINTYPMAXUNITSCOMMENTS
I Type Input Buffer
Low Input Level
High Input Level
V
ILI
V
IHI
2.0
0.8V
TTL Levels
V
ICLK Input Buffer
Low Input Level
V
ILCK
0.4V
C
High Input Level
Input Leakage
(All I and IS buffers)
Low Input Leakage
High Input Leakage
O8 Type Buffer
Low Output Level
High Output Level
Output Leakage
V
V
V
IHCK
I
IL
I
IH
OL
OH
I
OL
2.2
-10
-10
2.4
-10
+10
+10
0.4
+10
V
uAmAVIN = 0
V
= V
IN
V
= 8 mA @ V
I
OL
= 3.3V
IOH = -4mA @ V
V
= 3.3V
uA
= 0 to V
V
IN
(Note 1)
DDIO
DDI
DDI
DDIO
SMSC DS – USB97C201Page 54Rev. 03/25/2002
PRELIMINARY
PARAMETERSYMBOLMINTYPMAXUNITSCOMMENTS
O
O
O
O
I/O8 Type Buffer
Low Output Level
HIGH OUTPUT LEVEL
Output Leakage
I/O12 Type Buffer
Low Output Level
High Output Level
Output Leakage
I/O20 Type Buffer
V
OL
0.4
V
= 8 mA @ V
I
OL
DDI
= 3.3V
= -4 mA @ V
I
V
OH
I
OL
2.4
-10
+10
µA
OH
V
= 3.3V
= 0 to V
V
IN
DDI
DDIO
(Note 1)
V
OL
V
OH
I
OL
2.4
-10
0.4
+10
V
V
µA
= 12 mA @
I
OL
V
= 3.3V
DDIO
I
= -6mA @ V
OH
= 3.3V
VIN = 0 to V
DDIO
(Note 1)
DDI
Low Output Level
High Output Level
Output Leakage
V
OL
V
OH
I
OL
2.4
-10
IO-U
Note 2
Supply Current UnconfiguredI
Supply Current ActiveI
Supply Current StandbyI
CCINIT
CC
CSBY
TBDTBDTBDmA@ VDD = 2.5V
60100mA@ VDD = 2.5V
Note 1: Output leakage is measured with the current pins in high impedance.
Note 2: See Appendix A for USB DC electrical characteristics.
All pins except USB pins
(and pins under test tied
to AC ground)
DDI
SMSC DS – USB97C201Page 55Rev. 03/25/2002
PRELIMINARY
8.0 AC SPECIFICATIONS
8.1 ATA/ATAPI
The USB97C201 conforms to all timing diagrams and specifications for ATAPI-5 as set forth in the T13/1321D
Revision 3 NCITS specification. Please refer to this specification for more information.
8.2 USB2.0 Timing
The USB97C201 conforms to all timing diagrams and specifications for USB peripheral silicon building blocks as set
forth in the USB-IF USB 2.0 specification. Please refer to this specification for more information.
Note 1: Controlling Unit: millimeter
Note 2: Minimum space between protrusion and an adjacent lead is .007 mm.
Note 3: Package body dimensions D1 and E1 do not include the mold protrusion. Maximum mold protrusion is 0.25
mm
Note 5: Details of pin 1 identifier are optional but must be located within the zone indicated.
SMSC DS – USB97C201Page 57Rev. 03/25/2002
PRELIMINARY
FIGURE 7 – 100 PIN QFP PACKAGE
X
A
W
MINNOMINALMA
~~3.4Overall Package Height
A1
A2
D
D1
E
E1
H
L
L1
e
θθθθ
0.05~0.5Standoff
2.55~3.05Body Thickness
23.65~24.15X Span
19.90~20.10X body Size
17.65~18.15Y Span
13.90~14.10Y body Size
0.11~0.23Lead Frame Thickness
0.730.881.03Lead Foot Length
~1.95~Lead Length
o
0
0.20~0.40Lead Width
R1
R2
ccc
Notes:
1
Controlling Unit: millimeter.
2
Tolerance on the true position of the leads is ± 0.065 mm maximum
3
Package body dimensions D1 and E1 do not include the mold protrusion.
Maximum mold protrusion is 0.25 mm.
4
Dimension for foot length L measured at the gauge plane 0.25 mm above the seating plane.
5
Details of pin 1 identifier are optional but must be located within the zone indicated.
0.10~0.25Lead Shoulder Radius
0.15~0.40Lead Foot Radius
~~0.10Coplanarity
REMARKS
0.65 BasicLead Pitch
~7
o
Lead Foot Angle
SMSC DS – USB97C201Page 58Rev. 03/25/2002
PRELIMINARY
10.0 USB97C201 REVISIONS
PAGE(S)SECTION/FIGURE/ENTRYCORRECTION
105.0 PIN DESCRIPTIONSChanges on the following (see italicized
text): RBIAS, FS-, FS+
146.1.1 MCU Memory Map: Code SpaceDescription change (see italicized text)03/25/02
27Table 21 - MCU Clock Source SelectChanges on the following (see italicized
text): CLKVALID
29Table 25 – SIE Configuration RegisterChanges on the following (see italicized
text): SPEED
547.0 DC PARAMETERSChanges on supply references (see
italicized text)
DATE
REVISED
03/25/02
03/25/02
03/25/02
03/25/02
SMSC DS – USB97C201Page 59Rev. 03/25/2002
PRELIMINARY
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.