L-USS820D-DB LSI, L-USS820D-DB Datasheet

no-image

L-USS820D-DB

Manufacturer Part Number
L-USS820D-DB
Description
Manufacturer
LSI
Datasheet

Specifications of L-USS820D-DB

Operating Temperature (min)
-20C
Operating Temperature Classification
Commercial
Operating Temperature (max)
85C
Rad Hardened
No
Lead Free Status / RoHS Status
Compliant
USS-820D
USB Device Controller
Features
Full compliance with the Universal Serial Bus
Specification Revision 1.1.
Backward compatible with USS-820B and
USS-820C revisions.
Self-powered or bus-powered USB device. Meets
USB power specifications for bus-powered
devices.
Full-speed USB device (12 Mbits/s).
USB device controller with protocol control and
administration for up to 16 USB endpoints.
Supports control, interrupt, bulk, and isochronous
transfers for all 16 endpoints.
Programmable endpoint types and FIFO sizes and
internal 1120-byte logical (2240-byte physical for
dual-packet mode) shared FIFO storage allow a
wide variety of configurations.
Dual-packet mode of FIFOs reduces latency.
Supports USB remote wake-up feature.
On-chip crystal oscillator allows external 12 MHz
crystal or 3 V/5 V clock source.
On-chip analog PLL creates 48 MHz clock from
internal 12 MHz clock.
Integrated USB transceivers.
5 V tolerant I/O buffers allow operation in 3 V or
5 V system environments for 0 °C to 70 °C temper-
ature range.
5 V tolerant I/O buffers allow operation in 3 V only
system environments for –20 °C to +85 °C temper-
ature range.
Implemented in Agere Systems Inc. 0.25 µm, 3 V
standard-cell library.
44-pin MQFP (USS-820D) (Lead-free package also
available. (See Ordering Information on page 52.)
Evaluation kit available.
New Features After Revision B
Applications
Note: Advisories are issued as needed to update
New, centralized FIFO status bits and interrupt out-
put pin reduce firmware load.
New, additional nonisochronous transmit mode
allows NAK response to cause interrupt.
Isochronous behavior enhancements simplify firm-
ware control.
Additional FIFO sizes for nonisochronous end-
points.
USB RESET can be programmed to clear device
address.
USB RESET output status pin.
Firmware ability to wake up and reset a suspended
device.
Lower power.
5 V supply no longer required for 5 V tolerant oper-
ation.
Suitable for peripherals with embedded micropro-
cessors.
Glueless interface to microprocessor buses.
Support of multifunction USB implementations,
such as printer/scanner and integrated multimedia
applications.
Suitable for a broad range of device class peripher-
als in the USB standard.
product information. When using this data
sheet for design purposes, please contact
your Agere Systems Account Manager to
obtain the latest advisory on this product.
Data Sheet, Rev. 7
September 2004

Related parts for L-USS820D-DB

L-USS820D-DB Summary of contents

Page 1

... MHz clock. Integrated USB transceivers tolerant I/O buffers allow operation system environments for 0 ° °C temper- ature range tolerant I/O buffers allow operation only system environments for –20 °C to +85 °C temper- ature range. Implemented in Agere Systems Inc. 0.25 µ standard-cell library. ...

Page 2

... FIFO Programmability .............................................................................................................................................4 FIFO Access ........................................................................................................................................................... 4 Transmit FIFO ...................................................................................................................................................... 5 Receive FIFO ....................................................................................................................................................... 6 Pin Information .........................................................................................................................................................7 Register Timing Characteristics.................................................................................................................................8 Register Interface ....................................................................................................................................................11 Special Firmware Action for Shared Register Bits ................................................................................................13 Register Reads with Side Effects..........................................................................................................................14 Register Descriptions ............................................................................................................................................15 Interrupts .................................................................................................................................................................40 Firmware Responsibilities for USB SETUP Commands..........................................................................................41 Other Firmware Responsibilities..............................................................................................................................42 Frame Timer Behavior.............................................................................................................................................42 SUSPEND and RESUME Behavior ...

Page 3

... The USS-820D can be clocked either by connecting a 12 MHz crystal to the XTAL1 and XTAL2 pins using a 12 MHz external oscillator. The internal 12 MHz clock period, which is a function of either of these clock sources, is referred to as the device clock period (t throughout this data sheet ...

Page 4

... Register changes that affect the allocation of the shared FIFO storage among endpoints must not be made while there is valid data present in any of the enabled endpoints’ FIFOs. Any such changes will ren- der all FIFO contents undefined. Register bits that ...

Page 5

... The CPU writes to the FIFO location that is specified by the write pointer. After a write, the write pointer automati- cally increments by 1. The read marker points to the first byte of data written to a data set, and the read pointer points to the next FIFO location to be read by the USB interface. After a read, the read pointer automatically incre- ments by 1 ...

Page 6

... After a write, the write pointer automatically increments by 1. The write marker points to the first byte of data written to a data set, and the read pointer points to the next FIFO location to be read by the CPU. After a read, the read pointer automatically increments by 1. ...

Page 7

... V V SS2, SSX 34 Active-low signals within this document are indicated following the symbol names. † Pins marked as NC must have no external connections, except where noted. Agere Systems Inc. Name/Description 3.3 V Power Supply for Analog PLL. I Crystal/Clock Input. If the internal oscillator is used, this is the crystal input ...

Page 8

... Active-low signals within this document are indicated following the symbol names. † Pins marked as NC must have no external connections, except where noted. Register Timing Characteristics All register timing specifications assume a 100 pF load on the D[7:0] package pins and load on all other package pins. Table 3. Timing Parameters ...

Page 9

... Read Address Hold (starts after the trailing edge of RDN or IOCSN, whichever is first): Operational Suspended tRDDV1, Read Data Valid (from the leading edge of RDN or IOCSN or from tRDDV2 address valid, whichever is last, to data valid): Operational Suspended tRDDZ Read Data to Z State (starts after the trailing edge of RDN or ...

Page 10

... Write Minimum Pulse Width (from the leading edge of WRN or IOCSN, whichever is last, to the trailing edge of WRN or IOCSN, whichever is first) tWRDSU Write Data Setup (from data valid to the trailing edge of WRN or IOCSN, whichever is first) tWRDHD Write Data Hold (from the trailing edge of WRN or IOCSN, whichever is ...

Page 11

... A register read is accomplished by placing the register address on the A bus and asserting the IOCSN and RDN pins. After read data valid (tRDDV), the register data will appear on the D bus. A register write is accomplished by placing the register address on the A bus and the data to be written on the D bus, and asserting the IOCSN and WRN pins. ...

Page 12

... Scratch Firmware Information Register 1CH MCSR Miscellaneous Control/Status Register 1DH DSAV Data Set Available 1EH DSAV1 Data Set Available 1 * Indexed by EPINDEX. † Contains shared bits. See Special Firmware Action for Shared Register Bits section. 12 Description Data Sheet, Rev. 7 September 2004 Table Page ...

Page 13

... FIFO before resetting the PEND bit the receive done indication of the second data set was in fact saved in the pended SBI/ SBI1 register, then the standard copy of the SBI/SBI1 bit will be set when firmware resets the PEND bit to 0. USS-820D Update Behavior ...

Page 14

... FIFO. Therefore, firmware must be prepared to service a receive done interrupt where no data sets are present in the indicated FIFO. Table 9 shows the values loaded into each of the stan- dard copies of the shared register bits when firmware . resets the PEND register bit Table 9 ...

Page 15

... FTXIE4 Function Transmit Interrupt Enable 4. Enables transmit done interrupt for endpoint 4 (FTXD4). * For all bits indicates the interrupt is enabled and causes an interrupt to be signaled to the microcontroller indicates the associated interrupt source is disabled and cannot cause an interrupt. However, the interrupt bit’s value is still reflected in the SBI/SBI1 register. All of these bits can be read/written by firmware ...

Page 16

... If TXNAKE = 1, this also may indicate that a NAK was sent to the host in response packet that was received when TXFIF = 00. This condition also sets TXVOID. This SBI/SBI1 setting will persist until firmware clears TXVOID (or clears TXNAKE) ...

Page 17

... If TXNAKE = 1, this also may indicate that a NAK was sent to the host in response packet that was received when TXFIF = 00. This condition also sets TXVOID. This SBI/SBI1 setting will persist until firmware clears TXVOID (or clears TXNAKE) ...

Page 18

... Time Stamp Received from Host. TS[10:8] are the upper 3 bits of the 11-bit frame number issued with an SOF token. This time stamp is valid only if the SOFACK bit is set shared bit PEND must be set when writing this bit. See Special Firmware Action for Shared Register Bits section. 18 Bit 4 ...

Page 19

... See the Receive FIFO section for more details. * The EPINDEX register identifies the endpoint pair and selects the associated transmit and receive FIFO pair. The value in this register plus SFR addresses select the associated band of endpoint-indexed SFRs (TXDAT, TXCON, TXFLG, TXCNTH/L, RXDAT, RXCON, RXFLG, RXCNTH/L, EPCON, TXSTAT, and RXSTAT) ...

Page 20

... IN token. This bit is hardware read only. Note: Endpoint 0 is enabled for transmission upon RESET shared bit PEND must be set when writing this bit. See Special Firmware Action for Shared Register Bits section. 20 Bit 4 ...

Page 21

... SOF, setting TXFLUSH. * For normal operation, this bit should not be modified by the user except as required by the implementation of USB standard commands, such as SET_CONFIGURATION, SET_INTERFACE, and CLEAR_FEATURE [stall]. The SIE handles all sequence bit tracking required by normal USB traffic, as documented in the USB specification, Section 8.6. † ...

Page 22

... For isochronous transactions, TXACK is not updated until the next SOF. This bit is not updated at SOF if TXFLUSH is performed. * For normal operation, this bit should not be modified by the user except as required by the implementation of USB standard commands, such as SET_CONFIGURATION, SET_INTERFACE, and CLEAR_FEATURE [stall]. The SIE handles all sequence bit tracking required by normal USB traffic, as documented in the USB specification, Section 8.6. † ...

Page 23

... SET_CONFIGURATION, SET_INTERFACE, and CLEAR_FEATURE [stall]. The SIE handles all sequence bit tracking required by normal USB traffic, as documented in the USB specification, Section 8.6. † shared bit PEND must be set when writing this bit. See Special Firmware Action for Shared Register Bits section. Agere Systems Inc. ...

Page 24

... OUT token. Receive void is closely associated with the NACK/STALL handshake returned by the function after a valid OUT token. This void condition occurs when the endpoint input is disabled (RXIE = 0) or stalled (RXSTL = 1), the FIFO contains a setup packet (RXSETUP = 1), the FIFO has no available data sets (RXFIF = 11, or RXFIF = 01/10 and RXSPM = 1), or there is an existing FIFO error (RXURF = 1 or RXOVF = 1) ...

Page 25

... Reserved. Write 0s to these bits. Reads always return 0s. 9:0 BC[9:0] Transmit Byte Count (Write, Conditional Read). 10-bit, ring buffer. These bits store transmit byte count (TXCNT). Note: To send a status stage after a control write, no data control command null packet, write 0 to TXCNT. Agere Systems Inc. Bit 4 Bit 3 A5 ...

Page 26

... This bit is effective only when the ADVRM, ATM, and TXCLR bits are all clear. * Assumes MCSR.FEAT = 1. If MCSR.FEAT = 0, these FFSZ settings indicate 64 bytes. † ATM mode is recommended for normal operation. ADVRM and REVRP, which control the read marker and read pointer when ATM = 0, are used for test purposes. 26 ...

Page 27

... The TXFIF bits are set in sequence after each write to TXCNT to reflect the addition of a data set. Likewise, the TXFIF1 and TFIF0 are cleared in sequence after each advance of the read marker to indicate that the set is effectively discarded. The bit is cleared whether the read marker is advanced by firmware (setting ADVRM) or automatically by hardware (ATM = 1) ...

Page 28

... TXFIF[1:0] Transmit FIFO Index Flags (Read Only) (continued). If MCSR.FEAT = 1: TXFIF bits are not visible to the host until the first SOF is written, which occurs after the data set. Prior to that SOF, the device will return a zero-length data set in response (unless there is another, older data set present from the prior frame). This ensures that a given data set may only be sent during the subsequent frame, as required by the USB specification ...

Page 29

... TXOVF Transmit FIFO Overrun Flag (Read, Clear Only). This bit is set when an additional byte is written to a full FIFO, or TXCNT is written while TXFIF[1:0] = 11. This bit must be cleared by firmware through TXCLR. When this bit is set, the FIFO unknown state; thus recommended that the FIFO is reset in the error management routine using the TXCLR bit in TXCON. When the transmit FIFO overruns, the write pointer does not advance ...

Page 30

... Table 27. Receive FIFO Byte-Count High and Low Registers (RXCNTH, RXCNTL)—Address: RXCNTH = 07H, RXCNTL = 06H; Default: RXCNTH = 0000 0000B, RXCNTL = 0000 0000B High and low registers are in a two-register ring buffer that is used to store the byte count for the data packets received in the receive FIFO specified by EPINDEX. These registers are endpoint indexed. ...

Page 31

... REVWP is used when a data packet is bad. When the function interface receives the data packet again, the write starts at the origin of the previous (bad) data set. * ARM mode is recommended for normal operation. ADVWM and REVWP, which control the write marker and write pointer when ARM = 0, are used for test purposes. ...

Page 32

... USB Device Controller USB Device Controller Register Interface (continued) Table 29. Receive FIFO Flag Register (RXFLG)—Address: 09H; Default: 0000 1000B These flags indicate the status of the data packets in the receive FIFO specified by EPINDEX. This register is endpoint indexed. Bit 7 Bit 6 Bit 5 RXFIF1 ...

Page 33

... SOF). Firmware must not be late on consecutive frames— this will cause a loss of frame/data synchronization with the host—data sets may be visible to firmware during the wrong frame. Firmware must always set RXFFRC at the end of a data set read, even if RXFLUSH = 1. RXFLUSH is reset the setting of RXFFRC RXEMP Receive FIFO Empty Flag (Read Only) ...

Page 34

... RXOVF Receive FIFO Overrun Flag (Read, Clear Only). This bit is set when the SIE writes an additional byte to a full receive FIFO or writes a byte count to RXCNT with RXFIF[1:0] = 11. This bit must be cleared by firmware through RXCLR, although it can be cleared by hardware if a SETUP packet is received after an RXOVF error has already occurred. ...

Page 35

... RESET. If MCSR.FEAT = 1, SSR.SUPPO = 0 and MCSR.SUSPLOE = 0: This bit may also be set to 1 while the device is suspended. The effect of this write is to wake up the device remote wake-up had been performed, with the following excep- tions: 1) RESUME signaling is not transmitted to the host, 2) The feature is enabled regard- less of the SCR ...

Page 36

... IE_RESET set), an interrupt is generated to the controller. Firmware clears this bit shared bit PEND must be set when writing this bit. See Special Firmware Action for Shared Register Bits section. Table 32. Hardware Revision Register (REV)—Address: 18H; Default: 0001 0011B This register contains the hardware revision number, which will be incremented for each version of the hardware ...

Page 37

... Table 35. Scratch Firmware Information Register (SCRATCH)—Address: 1BH; Default: 0000 0000B This register contains a 7-bit scratch field that can be used by firmware to save and restore information. One possible use would be to save the device’s USB state (e.g., DEFAULT, ADDRESSED) during SUSPEND power off. ...

Page 38

... Updated by hardware on each wake-up from a suspended state. This bit is set the wake-up was caused by a remote wake-up event (RWUPN pin asserted). Otherwise reset to 0 (on a global RESUME or USB RESET). If RWUPN is asserted simultaneously with a global wake-up, the bit is reset to 0 (global wake-up wins). When set, this bit indicates that RESUME signaling will be transmitted upstream ...

Page 39

... For receive FIFOs, this register indicates that one or more data sets 5 RXAV2 are available to be read. For transmit FIFOs, this register indicates that one or more data 4 TXAV2 sets are available to be written. Bits always read 0 for endpoints which are not enabled ...

Page 40

... Each status bit has a corresponding enable bit that allows the event to cause an interrupt. Interrupts can be masked globally by the T_IRQ bit of the SCR register. The active level and signaling mode (level vs. pulse) of the IRQN output pin can be controlled by the IRQPOL and IRQLVL bits of the SCR register. All interrupts have equal priority— ...

Page 41

... FIFO while hardware is writing a new setup packet. Firmware must reset the EDOVW bit, read the SETUP command from the FIFO, and then check the STOVW and EDOVW bits. If either is set, the SETUP that was just read out is old and should be discarded. Firmware must then proceed with reading the new SETUP command. ...

Page 42

... USB host frame timer, and to synthesize lost SOF packets, as required by the USB specification. The frame timer requires three valid SOF packets from the host in order to lock to the host frame timer. This locked status is indicated by the FTLOCK status bit in SOFH. In order to achieve this ...

Page 43

... The following sections describe each of these steps in more detail. Hardware SUSPEND Detect The USS-820D detects a USB SUSPEND condition state persists on the bus for at least 3 ms. When this SUSPEND condition is detected, hardware sets the SSR.SUSPEND register status bit and, if IE_SUSP = 1, causes an interrupt. ...

Page 44

... A[4:0], IOCSN, RDN, WRN: Input-only pins. Their value will be determined by external logic, and must be a logic avoid current draw in the USS- 820D. Data Sheet, Rev. 7 September 2004 as specified in Table 46), its OSC Agere Systems Inc ...

Page 45

... SUSPN: Output-only pin, driven USS-820D to indicate SUSPEND. XTAL1: Input connection to internal oscillator crystal is used as a clock source, there are no special consid- erations for this pin external oscillator is used as a clock source, this input must be driven to a stable 1 by external logic. RESET: Driven to 0 during SUSPEND by external logic. ...

Page 46

... In applications where the external controller is powered off during SUSPEND (firmware has set SSR.SUSPPO), the SOFN pin must be connected to an external pull-down even if the pin is not functionally required. The pin is actually bidirectional, where the input mode is only used in chip test modes. The pull-down is required to avoid excessive power consumption by the input stage when the device is suspended ...

Page 47

... Leakage Current (D[7:0], SOFN) Leakage Current (USBR, DSA, DPPU) Leakage Current (XTAL1, A[4:0], RWUPN, IRQN, RESET, IOCSN, RDN, WRN) Note: These parameters may vary slightly when operating at ambient temperatures below 0 °C. Agere Systems Inc ° ° 3.3 V ± 0.165 Symbol Test Conditions ...

Page 48

... USB. All current values assume load on the package pins. The limit for suspended devices can only be met if careful measures are taken to control the interface to the USS- 820D, as documented in the SUSPEND and RESUME Behavior section. ...

Page 49

... The physical connection of the USS-820D to the USB bus requires only minimal components to provide proper USB electrical terminations. Both DPLS and DMNS require 24 Ω ± 1% series resis- tors for USB impedance matching. Additionally, a 1.5 kΩ pull-up resistor is required on DPLS for full- speed/low-speed differentiation. ...

Page 50

... Oscillator Connection Requirements The USS-820D requires an internal 48 MHz clock that it creates from an internal 12 MHz clock via a 4X PLL. Two methods of clock generation may be used to create this internal 12 MHz clock. Figure 10 shows the internal oscil- lator mode which requires only an external 12 MHz crystal and bias capacitors. The values of the capacitors should be chosen as indicated by the crystal manufacturer in order to cause the crystal to operate in a parallel resonant condition ...

Page 51

... Data Sheet, Rev. 7 September 2004 Outline Diagrams 44-Pin MQFP (USS-820D) Dimensions are in millimeters DETAIL A 0.80 TYP 1.60 REF 0.25 GAGE PLANE SEATING PLANE DETAIL A Agere Systems Inc. 13.20 ± 0.20 10.00 ± 0.20 PIN #1 IDENTIFIER ZONE DETAIL B 0.25 MAX 0.73/1.03 USS-820D ...

Page 52

... USS-820D USB Device Controller USB Device Controller Ordering Information Device Code USS820D-DB L-USS820D-DB 44-Pin MQFP (lead-free effort to better serve its customers and the environment, Agere is converting to lead-free material set on this product. 52 Package Comcode 44-Pin MQFP 108557463 * 700070793 Data Sheet, Rev. 7 September 2004 ...

Page 53

... Data Sheet, Rev. 7 September 2004 Appendix A. Special Function Register Bit Names Table 47. Alphabetical Listing of Special Function Register Bit Names Bit Name Register Table A[6:0] FADDR ADVRM TXCON ADVWM RXCON ARM RXCON ASOF SOFH ATM TXCON BC[7:0] RXCNTL BC[7:0] TXCNTL BC[9:8] RXCNTH ...

Page 54

... USS-820D USB Device Controller USB Device Controller Appendix B. USS-820D Register Map Table 48. USS-820D Register Map Register TXDAT TXCNTL TXCNTH TXCON TXCLR TXFFSZ[1:0] TXFLG TXFIF[1:0] RXDAT RXCNTL RXCNTH RXCON RXCLR RXFFSZ [1:0] RXFLG RXFIF[1:0] EPINDEX EPCON RXSTL TXSTL TXSTAT TXSEQ TXDSAM RXSTAT ...

Page 55

... DSAV register bit and assert the new DSA output pin (assuming they are enabled). This mode changes the meaning of TXVOID to indicate that such a NAK was sent, and it is the responsibility of firmware to clear TXVOID. While TXVOID = 1, the corresponding SBI/SBI1 register bit will remain SET as well ...

Page 56

... Tel. (44) 1344 296 400 Agere Systems Inc. reserves the right to make changes to the product(s) or information contained herein without notice. No liability is assumed as a result of their use or application. Agere is a registered trademark of Agere Systems Inc. Agere Systems and the Agere logo are trademarks of Agere Systems Inc. ...

Related keywords