0
登录后你可以
  • 下载海量资料
  • 学习在线课程
  • 观看技术视频
  • 写文章/发帖/加入社区
创作中心
发布
  • 发文章

  • 发资料

  • 发帖

  • 提问

  • 发视频

创作活动
TUSB3210PM

TUSB3210PM

  • 厂商:

    BURR-BROWN(德州仪器)

  • 封装:

    LQFP-64

  • 描述:

    IC USB CNTRLR STORAGE 64-LQFP

  • 数据手册
  • 价格&库存
TUSB3210PM 数据手册
Product Folder Sample & Buy Support & Community Tools & Software Technical Documents TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 TUSB3210 Universal Serial Bus General-Purpose Device Controller 1 Features 2 Applications • • • • • 1 • • • • • • • • • Multiproduct Support With One Code and One Chip (up to 16 Products With One Chip) Fully Compliant With USB 2.0 Full-Speed Specifications: TID #40270269 Supports 12-Mbits/s USB Data Rate (Full Speed) Supports USB Suspend, Resume, and Remote Wake-Up Operation Integrated 8052 Microcontroller With: – 256 × 8 RAM for Internal Data – 8K × 8 RAM Code Space Available for Downloadable Firmware From Host or I2C Port – 8K × 8 RAM for Development – 512 × 8 Shared RAM Used for Data Buffers and Endpoint Descriptor Blocks (EDB) – Buffer Space for USB Packet Transactions – Four 8052 GPIO Ports: Port 0, 1, 2, and 3 – Master I2C Controller for External Slave Device Access – Watchdog Timer Operates From a 12-MHz Crystal On-Chip PLL Generates 48 MHz Supports a Total of Three Input and Three Output (Interrupt, Bulk) Endpoints Power-Down Mode 64-Pin LQFP Package Keyboards Barcode Readers Flash Memory Readers General-Purpose Controllers 3 Description The TUSB3210 device is a USB-based controller targeted as a general-purpose MCU with GPIO. The TUSB3210 device has 8K × 8 RAM space for application development. In addition, the programmability of the TUSB3210 device makes it flexible enough to use for various other general USB I/O applications. Device Information(1) PART NUMBER TUSB3210 PACKAGE LQFP (64) BODY SIZE (NOM) 10.00 mm × 10.00 mm (1) For all available packages, see the orderable addendum at the end of the data sheet. Application Example Out GPIO Host (PC or On-the-Go Dual-Role Device) USB TUSB3210 GPIO Device In 1 An IMPORTANT NOTICE at the end of this data sheet addresses availability, warranty, changes, use in safety-critical applications, intellectual property matters and other important disclaimers. PRODUCTION DATA. TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com Table of Contents 1 2 3 4 5 6 7 Features .................................................................. Applications ........................................................... Description ............................................................. Revision History..................................................... Pin Configuration and Functions ......................... Specifications......................................................... 1 1 1 2 4 6 6.1 6.2 6.3 6.4 6.5 6 6 6 6 7 Absolute Maximum Ratings ..................................... ESD Ratings.............................................................. Recommended Operating Conditions....................... Thermal Information .................................................. Electrical Characteristics........................................... Detailed Description .............................................. 8 7.1 7.2 7.3 7.4 Overview ................................................................... Functional Block Diagram ......................................... Feature Description................................................... Device Functional Modes.......................................... 8 8 9 9 7.5 Register Maps ......................................................... 10 8 Application and Implementation ........................ 39 8.1 Application Information............................................ 39 8.2 Typical Applications ................................................ 40 9 Power Supply Recommendations...................... 43 10 Layout................................................................... 43 10.1 Layout Guidelines ................................................. 43 10.2 Layout Example .................................................... 44 11 Device and Documentation Support ................. 45 11.1 11.2 11.3 11.4 11.5 Documentation Support ........................................ Community Resources.......................................... Trademarks ........................................................... Electrostatic Discharge Caution ............................ Glossary ................................................................ 45 45 45 45 45 12 Mechanical, Packaging, and Orderable Information ........................................................... 45 4 Revision History REVISION DATE CHANGES F December 2015 1. Pin Configuration and Functions section, ESD Ratings table, Thermal Information table, Feature Description section, Device Functional Modes, Application and Implementation section, Power Supply Recommendations section, Layout section, Device and Documentation Support section, and Mechanical, Packaging, and Orderable Information section E August 2007 1. Deleted reference to 8K × 8 ROM 2. Clarified Section 2.2.2, bit 0. 3. Clarified Section 2.6.5 (VID/PID support) June 2004 1. Corrected description for pin 20 (TEST2). 2. Added description of programmable delay to the P2[7:0], P3.3 Interrupt (INT1) section. 3. Added delay values for I[3:0] to the INTCFG register description. C Nov-2003 1. Added USB logo to cover page. 2. Corrected pin 37 (1.8VDD) polarity in Terminal Functions table. 3. Removed note for pin 20 (TEST2) from Terminal Functions table. 4. Removed application diagram Figure 7. 5. Clarified Section 4-2, Reset Timing B April 2003 1. Grammatical clean-up 2. Clarification on pin 55 (P3.3) and its functionality as INT1. 3. Additional corrections in the 8052 Interrupt and Status Registers section. D 2 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 Revision History (continued) REVISION DATE CHANGES A February 2003 1. Removed most references to ROM version, including the MCU Memory Map (ROM Version) figure. 2. Clarified pin names and descriptions for pins 8 (S2), 9 (S3), 21 (GND), 37 (VDD18), 57 (P3.1/S1/TXD), and 58 (P3.0/S0/RXD). 3. Removed NOTE from cover page. 4. Expanded Ordering Information table. 5. Clarified pin functions for pins 14 (TEST0) and 15 (TEST1) (14 & 15) in Terminal Functions table. Simplified Terminal Function table for GPIO ports. 7. Added note on open-drain output pins for Terminal Functions table. 8. Added ET2 information to the 8052 Interrupt Location Map table and further clarified the entire 8052 Interrupt and Status Registers section. 9. Corrected quiescent and suspend current values in Electrical Characteristics table. * February 2001 Initial release Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 3 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 5 Pin Configuration and Functions P0.5 P0.4 P0.3 P0.2 P0.1 P0.0 GND P1.7 P1.6 VCC VREN 1.8VDD P1.5 P1.4 P1.3 P1.2 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 PM Package 64-Pin LQFP Top View P0.6 49 32 P1.1 P0.7 50 31 P1.0 P3.7 51 30 P2.7 P3.6 52 29 P2.6 P3.5 53 28 P2.5 P3.[4:7] 54 27 P2.4 P3.3 55 26 P2.3 P3.2 56 25 P2.2 Thermal Pad 4 Submit Documentation Feedback 16 PUR SUSP 17 15 64 TEST1 NC 14 DP TEST0 18 13 63 RST NC 12 DM SCL 19 11 62 SDA VCC 10 TEST2 VCC 20 9 61 S3 X1 8 GND S2 21 7 60 NC X2 6 P2.0 NC 22 5 59 GND GND 4 P2.1 RSV 23 3 58 NC P3.0/S0/RXD 2 GND NC 24 1 57 RSV P3.1/S1/TXD Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 Pin Functions PIN I/O DESCRIPTION NAME NO. 1.8VDD 37 I/O DM 19 I/O Differential data-minus USB 18 I/O Differential data-plus USB DP GND 5, 21, 24, 42, 59 NC 2, 3, 6, 7, 63, 64 — 1.8 V. When VREN is high, 1.8 V must be applied externally to provide current for the core during suspend. Power supply ground No connection P0.[0:7] 43, 44, 45, 46, 47, 48, 49, 50 I/O General-purpose I/O port 0 bits 0–7, Schmitt-trigger input, 100-µA active pullup, open-drain output P1.[0:7] 31, 32, 33, 34, 35, 36, 40, 41 I/O General-purpose I/O port 1 bits 0–7, Schmitt-trigger input, 100-µA active pullup, open-drain output P2.[0:7] 22, 23, 25, 26, 27, 28, 29, 30 I/O General-purpose I/O port 2 bits 0–7, Schmitt-trigger input, 100-µA active pullup, open-drain output P3.0: General-purpose I/O port 3 bit 0, Schmitt-trigger input, 100-µA active pullup, open-drain output P3.0/S0/RXD 58 I/O S0: See VIDSTA: VID/PID Status Register RXD: Can be used as a UART interface P3.1: General-purpose I/O port 3 bit 1, Schmitt-trigger input, 100-µA active pullup, open-drain output P3.1/S1/TXD 57 I/O S1: See VIDSTA: VID/PID Status Register TXD: Can be used as a UART interface P3.2 56 I/O General-purpose I/O port 3 bit 2, Schmitt-trigger input, 100-µA active pullup, open-drain output; INT0 only used internally (see Logical Interrupt Connection Diagram (INT0)) P3.3 55 I/O General-purpose I/O port 3 bit 3, Schmitt-trigger input, 100-µA active pullup, open-drain output; may support INT1 input, depending on configuration (see Figure 6) P3.[4:7] 54, 53, 52, 51 I/O General-purpose I/O port 3 bits 4–7, Schmitt-trigger input, 100-µA active pullup, open-drain output PUR 17 O Pullup resistor connection pin (3-state) push-pull CMOS output (±4 mA) RST 13 I Controller master reset signal, Schmitt-trigger input, 100-µA active pullup RSV 1, 4 — S2 8 I General-purpose input, can be used for VID/PID selection under firmware control. This input has no internal pullup; therefore, it must be driven or pulled either low or high and cannot be left unconnected. S3 9 I General-purpose input. This input has no internal pullup; therefore, it must be driven or pulled either low or high and cannot be left unconnected. SCL 12 O Serial clock I2C; push-pull output SDA 11 I/O Serial data I2C; open-drain output SUSP 16 O Suspend status signal: suspended (HIGH); unsuspended (LOW) TEST0 14 I Test input0, Schmitt-trigger input, 100-µA active pullup TEST1 15 I Test input1, Schmitt-trigger input, 100-µA active pullup TEST2 20 I Test input2, Schmitt-trigger input, 100-µA active pullup. This pin is reserved for testing purposes and must be left unconnected. VCC Reserved (Do not connect these pins.) 10, 39, 62 — VREN 38 I Power supply input, 3.3-V typical Voltage regulator enable: enable active-LOW; disable active-HIGH X1 61 I 12-MHz crystal input X2 60 O 12-MHz crystal output Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 5 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 6 Specifications 6.1 Absolute Maximum Ratings over operating free-air temperature range (unless otherwise noted) (1) MIN MAX UNIT VCC Supply voltage –0.5 4 V VI Input voltage –0.5 VCC + 0.5 V VO Output voltage –0.5 VCC + 0.5 V IIK Input clamp current ±20 mA IOK Output clamp current ±20 mA Tstg Storage temperature 150 °C (1) –65 Stresses beyond those listed under Absolute Maximum Ratings may cause permanent damage to the device. These are stress ratings only, and functional operation of the device at these or any other conditions beyond those indicated under Recommended Operating Conditions is not implied. Exposure to absolute-maximum-rated conditions for extended periods may affect device reliability. 6.2 ESD Ratings VALUE V(ESD) (1) (2) Electrostatic discharge Human body model (HBM), per ANSI/ESDA/JEDEC JS-001 (1) ±2000 Charged-device model (CDM), per JEDEC specification JESD22C101 (2) ±500 UNIT V JEDEC document JEP155 states that 500-V HBM allows safe manufacturing with a standard ESD control process. JEDEC document JEP157 states that 250-V CDM allows safe manufacturing with a standard ESD control process. 6.3 Recommended Operating Conditions MIN NOM MAX VCC Supply voltage 3 3.3 3.6 UNIT V VI Input voltage 0 VCC V VIH High-level input voltage 2 VCC V VIL Low-level input voltage 0 0.8 V TA Operating temperature 0 70 °C 6.4 Thermal Information TUSB3210 THERMAL METRIC (1) PM (LQFP) UNIT 64 PINS RθJA Junction-to-ambient thermal resistance 61.3 °C/W RθJC(top) Junction-to-case (top) thermal resistance 25.1 °C/W RθJB Junction-to-board thermal resistance 32.4 °C/W ψJT Junction-to-top characterization parameter 2.4 °C/W ψJB Junction-to-board characterization parameter 32.1 °C/W RθJC(bot) Junction-to-case (bottom) thermal resistance n/a °C/W (1) 6 For more information about traditional and new thermal metrics, see the Semiconductor and IC Package Thermal Metrics application report, SPRA953. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 6.5 Electrical Characteristics TA = 25°C, VCC = 3.3 V ± 0.3 V, GND = 0 V PARAMETER TEST CONDITIONS MIN TYP MAX VCC – 0.5 UNIT VOH High-level output voltage IOH = –4 mA VOL Low-level output voltage IOL = 4 mA V VIT+ Positive input threshold voltage VI = VIH VIT– Negative input threshold voltage VI = VIL Vhys Hysteresis (VIT+ – VIT–) VI = VIH IIH High-level input current VI = VIH ±1 µA IIL Low-level input current VI = VIL ±1 µA IOZ Output leakage current (Hi-Z) VI = VCC or VSS 10 µA CI Input capacitance 5 pF CO Output capacitance 7 pF ICC Quiescent ICCx Suspend ICCx1.8 Suspend 1.8 VDD 0.5 V 2 V 0.8 V 1 25 V 45 mA 45 µA 1 µA Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 7 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7 Detailed Description 7.1 Overview The TUSB3210 device is a USB-based controller targeted as a general-purpose MCU with GPIO. The TUSB3210 device has 8K × 8 RAM space for application development. In addition, the programmability of the TUSB3210 device makes it flexible enough to use for various general USB I/O applications. Unique vendor identification and product identification (VID/PID) can be selected without the use of an external EEPROM. The onboard oscillator generates the internal system clocks using a 12-MHz crystal. The TUSB3210 device can be programmed through an inter-IC (I2C) serial interface at power on from an EEPROM, or the application firmware can be downloaded from a host PC through USB. The popular 8052-based microprocessor allows several thirdparty standard tools to be used for application development. In addition, the vast amounts of application code available in the general market can also be used (this may or may not require some code modification due to hardware variations). 7.2 Functional Block Diagram 12 MHz Clock Oscillator PLL and Dividers USB-0 Reset, Interrupt and WDT 8052 Core USB TxR 6K × 8 ROM 8 8K × 8 RAM[1] 8 8 RSTI 2 × 16-Bit Timers Port 0 8 P0.[7:0] Port 1 8 P1.[7:0] Port 2 8 P2.[7:0] Port 3 8 P3.[7:0] 8 512 × 8 SRAM 8 Logic USB SIE 8 CPU - I/F Suspend/ Resume 8 UBM USB Buffer Manager 8 8 I2C Controller I2C Bus TDM Control Logic NOTE: 8K × 8 ROM version is available. Contact TI Marketing. 8 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.3 Feature Description 7.3.1 USB 2.0 Full-Speed Compliant The TUSB3210 device s fully compliant with USB 2.0 full-speed; it supports 12 Mbits/s of USB data rate (full speed) as well as supporting USB suspend, resume, and remote wake-up operation. 7.3.2 Code Space Available The TUSB3210 device has 8K × 8 RAM for firmware development. This firmware can be loaded though USB or using I2C serial interface from an EEPROM. The MCU executes a read from an external EEPROM and tests to determine if it contains the code (test for boot signature). If it contains the code, the MCU reads from EEPROM and writes to the 8K RAM in XDATA space. If not, the MCU proceeds to boot from the USB. 7.3.3 Clock Generation The TUSB3210 device accepts a 12-MHz crystal input to drive an internal oscillator of 48 MHz. If a clock is provided to X1 instead of a crystal, X2 is left open. Otherwise, if a crystal is used, the connection must follow the guidelines shown in Figure 1. Because X1 and X2 are coupled to other leads and supplies on the PCB, it is important to keep the leads as short as possible and away from any switching leads. TI also recommends minimizing the capacitance between X1 and X2, which can be accomplished by shielding C1 and C2 with the clean ground lines. R1 1M Y1 XI 12 MHz TUSB3210 CLOCK C1 XO C2 Figure 1. Clock Generation Diagram 7.3.4 UART Interface The TUSB3210 device can use P3.0 and P3.1 as UART port; this UART is normally used for debug purposes. 7.4 Device Functional Modes 7.4.1 Interface Configuration The TUSB3210 device contains onboard ROM microcode, which enables the MCU to enumerate the device as a USB peripheral. The ROM microcode can also load application code into internal RAM from either external memory through the I2C bus or from the host through the USB. 7.4.2 GPIO Controller The TUSB3210 device is a USB-based controller targeted as a general-purpose MCU with GPIO. The TUSB3210 device has 8K × 8 RAM space for application development to control these GPIOs. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 9 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5 Register Maps Table 1. Test0 and Test1 Functions TEST0 TEST1 0 0 Selects 48-MHz clock input (from an oscillator or other onboard clock source) FUNCTION 0 1 Reserved for testing purposes 1 0 Reserved for testing purposes 1 1 Selects 12-MHz crystal as clock source (default) 7.5.1 MCU Memory Map Figure 2 illustrates the MCU memory map under boot and normal operation. It must be noted that the internal 256 bytes of IDATA are not shown because it is assumed to be in the standard 8052 location (0000 to 00FF). The shaded areas represent the internal ROM/RAM. When the SDW bit = 0 (boot mode): The 6K ROM is mapped to address 0000–17FF and is duplicated in location 8000–97FF in code space. The internal 8K RAM is mapped to address range 0000–1FFF in data space. Buffers, MMR and I/O are mapped to address range (FD80–FFFF) in data space. When the SDW bit = 1 (normal mode): The 6K ROM is mapped to 8000–97FF in code space. The internal 8K RAM is mapped to address range 0000–1FFF in code space. Buffers, MMR, and I/O are mapped to address range FD80–FFFF in data space. Normal Mode (SDW = 1) Boot Mode (SDW = 0) CODE XDATA XDATA CODE 8K RAM Read/Write 8K Code RAM Read Only 0000 6K Boot ROM 17FF 1FFF 8000 6K Boot ROM 6K Boot ROM 97FF FD80 FF80 512 Bytes RAM 512 Bytes RAM MMR MMR FFFF Figure 2. MCU Memory Map (TUSB3210) 10 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.2 Miscellaneous Registers 7.5.2.1 TUSB3210 Boot Operation Because the code space is in RAM (with the exception of the boot ROM), the TUSB3210 firmware must be loaded from an external source. Two options for booting are available: an external serial EEPROM source can be connected to the I2C bus, or the host can be used through the USB. On device reset, the SDW bit (in the ROM register) and the CONT bit in the USB control register (USBCTL) are cleared. This configures the memory space to boot mode (see Table 3) and keeps the device disconnected from the host. The first instruction is fetched from location 0000 (which is in the 6K ROM). The 8K RAM is mapped to XDATA space (location 0000h). The MCU executes a read from an external EEPROM and tests to determine if it contains the code (test for boot signature). If it contains the code, the MCU reads from EEPROM and writes to the 8K RAM in XDATA space. If not, the MCU proceeds to boot from the USB. Once the code is loaded, the MCU sets SDW to 1. This switches the memory map to normal mode; that is, the 8K RAM is mapped to code space, and the MCU starts executing from location 0000h. When the switch is done, the MCU sets CONT to 1 (in USBCTL register) This connects the device to the USB bus, resulting in the normal USB device enumeration. 7.5.2.2 MCNFG: MCU Configuration Register This register is used to control the MCU clock rate (R/O notation indicates read only by the MCU). 7 RSV R/W 6 XINT R/W 5 RSV R/O 4 R3 R/O 3 R2 R/O 2 R1 R/O 1 R0 R/O 0 SDW R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION This bit enables/disables boot ROM. 0 SDW 4–1 R[3:0] 5 RSV SDW = 0 When clear, the MCU executes from the 6K boot ROM space. The boot ROM appears in two locations: 0000 and 8000h. The 8K RAM is mapped to XDATA space; therefore, read/write operation is possible. This bit is set by the MCU after the RAM load is completed. The MCU cannot clear this bit. It is cleared on power-up reset or function reset. SDW = 1 When set by the MCU, the 6K boot ROM maps to location 8000h, and the 8K RAM is mapped to code space, starting at location 0000h. At this point, the MCU executes from RAM, and write operation is disabled (no write operation is possible in code space). 0 No effect These bits reflect the device revision number. 0 Reserved INT1 source control bit 6 7 XINT RSV 0 0 XINT = 0 INT1 is connected to the P3.3 pin and operates as a standard INT1 interrupt. XINT = 1 INT1 is connected to the OR of the port-2 inputs. Reserved Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 11 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.2.3 PUR_n: GPIO Pullup Register for Port n (n = 0 to 3) PUR_0: GPIO pullup register for port 0 PUR_1: GPIO pullup register for port 1 PUR_2: GPIO pullup register for port 2 PUR_3: GPIO pullup register for port 3 7 PORT_n.7 R/W 6 PORT_n.6 R/W 5 PORT_n.5 R/W 4 PORT_n.4 R/W 3 PORT_n.3 R/W 2 PORT_n.2 R/W 1 PORT_n.1 R/W 0 PORT_n.0 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 0–7 PORT_n.N (N = 0 to 7) 0 FUNCTION The MCU can write to this register. If the MCU sets this bit to 1, the internal pullup resistor is disconnected from the pin. If the MCU clears this bit to 0, the pullup resistor is connected to the pin. The pullup resistor is connected to the VCC power supply. 7.5.2.4 INTCFG: Interrupt Configuration 7 RSV R/O 6 RSV R/O 5 RSV R/O 4 RSV R/O 3 I3 R/W 2 I2 R/W 1 I1 R/W 0 I0 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION The MCU can write to this register to set the interrupt delay time for port 2 on the MCU. The value of the lower nibble represents the delay in ms. Default after reset is 2 ms. 0–3 4–7 12 I[3:0] RSV 0010 0 I[3:0] Delay 0000 5 ms 0001 5 ms 0010 2 ms (default) 0011 3 ms 0100 4 ms 0101 5 ms 0110 6 ms 0111 7 ms 1000 8 ms 1001 9 ms 1010 10 ms 1011 5 ms 1100 5 ms 1101 5 ms 1110 5 ms 1111 5 ms Reserved Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.2.5 WDCSR: Watchdog Timer, Control, and Status Register A watchdog timer (WDT) with 1-ms clock is provided. The watchdog timer works only when a USB start-of-frame has been detected by the TUSB3210. If this register is not accessed for a period of 32 ms, the WDT counter resets the MCU (see Figure 3, Reset Diagram). When the IDL bit in PCON is set, the WDT is suspended until an interrupt is detected. At this point, the IDL bit is cleared and the WDT resumes operation. The WDE bit of this register is cleared only on power up or USB reset (if enabled). When the MCU writes a 1 to the WDE bit of this register, the WDT starts running (W/O notation indicates write only by the MCU). 7 WDE R/W 6 WDR R/W 5 RSV R/O 4 RSV R/O 3 RSV R/O 2 RSV R/O 1 RSV R/O 0 WDT W/O LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION 0 WDT 0 The MCU must write a 1 to this bit to prevent the WDT from resetting the MCU. If the MCU does not write a 1 in a period of 31 ms, the WDT resets the device. Writing a 0 has no effect on the WDT. (WDT is a 5-bit counter using a 1-ms CLK.) This bit is read as 0. 5–1 RSV 0 Reserved = 0 Watchdog reset indication bit. This bit indicates if the reset occurred due to power-on reset or watchdog timer reset. 6 WDR 0 WDR = 0 A power-up or USB reset occurred. WDR = 1 A watchdog time-out reset occurred. To clear this bit, the MCU must write a 1. Writing a 0 has no effect. Watchdog timer enable. 7 WDE 0 WDE = 0 Disabled WDE = 1 Enabled 7.5.2.6 PCON: Power Control Register (at SFR 87h) 7 SMOD R/W 6 RSV R/O 5 RSV R/O 4 RSV R/O 3 GF1 R/W 2 GF0 R/W 1 RSV R/O 0 IDL R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION MCU idle mode bit. This bit can be set by the MCU and is cleared only by the INT1 interrupt. 0 IDL IDL = 0 The MCU is not in idle mode. This bit is cleared by the INT1 interrupt logic when INT1 is asserted for at least 400 μs. IDL = 1 The MCU is in idle mode and RAM is in low-power mode. The oscillator/APLL is off and the WDT is suspended. When in suspend mode, only INT1 can be used to exit from idle state and generate an interrupt. INT1 must be asserted for at least 400 μs for the interrupt to be recognized. 0 1 RSV 0 Reserved 3–2 GF[1:0] 00 General-purpose bits. The MCU can write and read them. 6–4 RSV 0 Reserved 7 SMOD 0 Double baud-rate control bit. For more information, see the UART serial interface in the M8052 core specification. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 13 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.3 Buffers + I/O RAM Map The address range from FD80 to FFFF is reserved for data buffers, set-up packet, endpoint descriptor blocks (EDB), and all I/O. RAM space of 512 bytes [FD80–FF7F] is used for EDB and buffers. The FF80–FFFF range is used for memory-mapped registers (MMR). represents the internal XDATA space allocation. The address range from FD80 to FFFF is reserved for data buffers, set-up packet, endpoint descriptor blocks(EDB), and all I/O. RAM space of 512 bytes [FD80–FF7F] is used for EDB and buffers. The FF80–FFFF range is used for memory-mapped registers (MMR). Table 2 represents the internal XDATA space allocation and Table 3 describes the registers function. Table 2. XDATA Space DESCRIPTION ADDRESS RANGE Internal memory-mapped registers (MMR) FFFF ↑ FF80 FF7F Endpoint descriptor blocks (EDB) ↑ FF08 FF07 Set-up packet buffer ↑ FF00 FEFF Input endpoint-0 buffer ↑ 512-Byte RAM FEF8 FEF7 Output endpoint-0 buffer ↑ FEF0 FEEF Data buffers (368 bytes) ↑ FD80 14 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 Table 3. Memory-Mapped Register Summary (XDATA Range = FF80 → FFFF) ADDRESS REGISTER FFFF FUNADR FUNADR: Function address register DESCRIPTION FFFE USBSTA USBSTA: USB status register FFFD USBMSK USBMSK: USB interrupt mask register FFFC USBCTL USBCTL: USB control register ↑ RESERVED FFF6 VIDSTA ↑ RESERVED VIDSTA: VID/PID status register FFF3 I2CADR I2CADR: I2C address register FFF2 I2CDAI I2CDAI: I2C data-input register FFF1 I2CDAO I2CDAO: I2C data-output register FFF0 I2CSTA I2CSTA: I2C status and control register ↑ RESERVED FF97 PUR3 Port 3 pullup resistor register FF96 PUR2 Port 2 pullup resistor register FF95 PUR1 Port 1 pullup resistor register FF94 PUR0 Port 0 pullup resistor register FF93 WDCSR WDCSR: Watchdog timer, control and status register FF92 VECINT VECINT: Vector interrupt register FF91 RESERVED FF90 MCNFG ↑ RESERVED MCNFG: MCU configuration register FF84 INTCFG FF83 OEPBCNT_0 INTCFG: Interrupt delay configuration register OEPBCNT_0: Output endpoint-0 byte count register FF82 OEPCNFG_0 OEPCNFG_0: Output endpoint-0 configuration register FF81 IEPBCNT_0 IEPBCNT_0: Input endpoint-0 byte count register FF80 IEPCNFG_0 IEPCNFG_0: Input endpoint-0 configuration register Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 15 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.4 Endpoint Descriptor Block (EDB-1 to EDB-3) Data transfers between USB, MCU and external devices are defined by an endpoint descriptor block (EDB). Four input and four output EDBs are provided. With the exception of EDB-0 (I/O endpoint 0), all EDBs are located in SRAM as shown in Table 4. Each EDB contains information describing the X and Y buffers. In addition, it provides general status information. Table 4. EDB and Buffer Allocations in XDATA ADDRESS SIZE DESCRIPTION 32 bytes RESERVED 8 bytes Input endpoint 3: configuration 8 bytes Input endpoint 2: configuration 8 bytes Input endpoint 1: configuration 40 bytes RESERVED 8 bytes Output endpoint 3: configuration 8 bytes Output endpoint 2: configuration 8 bytes Output endpoint 1: configuration 8 bytes Setup packet block 8 bytes Input endpoint 0: buffer 8 bytes Output endpoint 0: buffer FF7F ↑ FF60 FF5F ↑ FF58 FF57 ↑ FF50 FF4F ↑ FF48 FF47 ↑ FF20 FF1F ↑ FF18 FF17 ↑ FF10 FF0F ↑ FF08 FF07 ↑ FF00 FEFF ↑ FEF8 FEF7 ↑ FEF0 FEEF ↑ FD80 16 Top of buffer space 368 bytes Buffer space Start of buffer space Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 Table 5 lists the EDB entries for EDB-1 to EDB-3. EDB-0 registers are described separately. Table 5. EDB Entries in RAM (n = 1 to 3) OFFSET ENTRY NAME DESCRIPTION 07 EPSIZXY_n I/O endpoint_n: X/Y buffer size 06 EPBCTY_n I/O endpoint_n: Y byte count 05 EPBBAY_n I/O endpoint_n: Y buffer base address 04 SPARE Not used 03 SPARE Not used 02 EPBCTX_n I/O endpoint_n: X byte count 01 EPBBAX_n I/O endpoint_n: X buffer base address 00 EPCNF_n I/O endpoint_n: configuration 7.5.4.1 OEPCNF_n: Output Endpoint Configuration (n = 1 to 3) 7 UBME R/W 6 ISO R/W 5 TOGLE R/W 4 DBUF R/W 3 STALL R/W 2 USBIE R/W 1 RSV R/O 0 RSV R/O LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 1–0 RSV 0 2 USBIE x FUNCTION Reserved USB interrupt enable on transaction completion. Set/cleared by MCU. USBIE = 0 No interrupt USBIE = 1 Interrupt on transaction completion USB stall condition indication. Set/cleared by MCU. 3 STALL 0 STALL = 0 No stall STALL = 1 USB stall condition. If set by MCU, a STALL handshake is initiated and the bit is cleared by the MCU. Double buffer enable. Set/cleared by MCU. 4 DBUF x DBUF = 0 Primary buffer only (X-buffer only) DBUF = 1 Toggle bit selects buffer 5 TOGLE x USB toggle bit. This bit reflects the toggle sequence bit of DATA0, DATA1. 6 ISO x ISO = 0 7 UBME x Non-isochronous transfer. This bit must be cleared by the MCU because only nonisochronous transfer is supported. UBM enable/disable bit. Set/cleared by the MCU. UBME = 0 UBM cannot use this endpoint. UBME = 1 UBM can use this endpoint. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 17 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.4.2 OEPBBAX_n: Output Endpoint X-Buffer Base Address (n = 1 to 3) 7 A10 R/W 6 A9 R/W 5 A8 R/W 4 A7 R/W 3 A6 R/W 2 A5 R/W 1 A4 R/W 0 A3 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME 7–0 A[10:3] RESET FUNCTION x A[10:3] of X-buffer base address (padded with 3 LSB of zeros for a total of 11 bits). This value is set by the MCU. UBM or DMA uses this value as the start address of a given transaction. Furthermore, UBM or DMA does not change this value at the end of a transaction. 7.5.4.3 OEPBCTX_n: Output Endpoint X-Byte Count (n = 1 to 3) 7 NAK R/W 6 C6 R/W 5 C5 R/W 4 C4 R/W 3 C3 R/W 2 C2 R/W 1 C1 R/W 0 C0 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 6–0 C[6:0] x 7 NAK x FUNCTION X-Buffer Byte count: 000 0000b → Count = 0 000 0001b → Count = 1 byte . . . 011 1111b → Count = 63 bytes 100 0000b → Count = 64 bytes Any value ≥ 100 0001b produces unpredictable results. NAK = 0 No valid data in buffer. Ready for host-out. NAK = 1 Buffer contains a valid packet from host (host-out request is NAK). 7.5.4.4 OEPBBAY_n: Output Endpoint Y-Buffer Base Address (n = 1 to 3) 7 A10 R/W 6 A9 R/W 5 A8 R/W 4 A7 R/W 3 A6 R/W 2 A5 R/W 1 A4 R/W 0 A3 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset 18 BIT NAME RESET FUNCTION 7–0 A[10:3] x A[10:3] of Y-buffer base address (padded with 3 LSB of zeros for a total of 11 bits). This value is set by the MCU. UBM or DMA uses this value as the start address of a given transaction. Furthermore, UBM or DMA does not change this value at the end of a transaction. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.4.5 OEPBCTY_n: Output Endpoint Y-Byte Count (n = 1 to 3) 7 NAK R/W 6 C6 R/W 5 C5 R/W 4 C4 R/W 3 C3 R/W 2 C2 R/W 1 C1 R/W 0 C0 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 6–0 C[6:0] x 7 NAK x FUNCTION Y-Buffer Byte count: 000 0000b → Count = 0 000 0001b → Count = 1 byte . . . 011 1111b → Count = 63 bytes 100 0000b → Count = 64 bytes Any value ≥ 100 0001b produces unpredictable results. NAK = 0 No valid data in buffer. Ready for host-out NAK = 1 Buffer contains a valid packet from host (host-out request is NAK). 7.5.4.6 OEPSIZXY_n: Output Endpoint X-/Y-Buffer Size (n = 1 to 3) 7 RSV R/O 6 S6 R/W 5 S5 R/W 4 S4 R/W 3 S3 R/W 2 S2 R/W 1 S1 R/W 0 S0 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION 6–0 S[6:0] x X- and Y-Buffer size: 000 0000b → Count = 0 000 0001b → Count = 1 byte . . . 011 1111b → Count = 63 bytes 100 0000b → Count = 64 bytes Any value ≥ 100 0001b produces unpredictable results. 7 RSV 0 Reserved Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 19 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.4.7 IEPCNF_n: Input Endpoint Configuration (n = 1 to 3) 7 UBME R/W 6 ISO R/W 5 TOGLE R/W 4 DBUF R/W 3 STALL R/W 2 USBIE R/W 1 RSV R/O 0 RSV R/O LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 1–0 RSV x 2 USBIE x FUNCTION Reserved = 0 USB interrupt enable on transaction completion USBIE = 0 No interrupt USBIE = 1 Interrupt on transaction completion USB stall condition indication. Set by UBM, but can be set/cleared by the MCU. 3 STALL 0 STALL = 0 No stall STALL = 1 USB stall condition. If set by the MCU, a STALL handshake is initiated and the bit is cleared automatically. Double buffer enable 4 DBUF x 5 TOGLE x 6 ISO x DBUF = 0 Primary buffer only (X-buffer only) DBUF = 1 Toggle bit selects buffer USB toggle bit. This bit reflects the toggle sequence bit of DATA0, DATA1. ISO = 0 Non-isochronous transfer. This bit must be cleared by the MCU because only nonisochronous transfer is supported. UBM enable/disable bit. Set/cleared by the MCU. 7 UBME x UBME = 0 UBM cannot use this endpoint. UBME = 1 UBM can use this endpoint. 7.5.4.8 IEPBBAX_n: Input Endpoint X-Buffer Base Address (n = 1 to 3) 7 A10 R/W 6 A9 R/W 5 A8 R/W 4 A7 R/W 3 A6 R/W 2 A5 R/W 1 A4 R/W 0 A3 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME 7–0 A[10:3] RESET FUNCTION x A[10:3] of X-buffer base address (padded with 3 LSB of zeros for a total of 11 bits). This value is set by the MCU. UBM or DMA uses this value as the start address of a given transaction. Furthermore, UBM or DMA does not change this value at the end of a transaction. 7.5.4.9 IEPBCTX_n: Input Endpoint X-Byte Base Address (n = 1 to 3) 7 NAK R/W 6 C6 R/W 5 C5 R/W 4 C4 R/W 3 C3 R/W 2 C2 R/W 1 C1 R/W 0 C0 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT 20 NAME RESET 6–0 C[6:0] x 7 NAK x FUNCTION X-Buffer Byte count: 000 0000b → Count = 0 000 0001b → Count = 1 byte . . . 011 1111b → Count = 63 bytes 100 0000b → Count = 64 bytes Any value ≥ 100 0001b produces unpredictable results. NAK = 0 Buffer contains a valid packet for host-in transaction NAK = 1 Buffer is empty (host-in request is NAK) Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.4.10 IEPBBAY_n: Input Endpoint Y-Buffer Base Address (n = 1 to 3) 7 A10 R/W 6 A9 R/W 5 A8 R/W 4 A7 R/W 3 A6 R/W 2 A5 R/W 1 A4 R/W 0 A3 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT 7–0 NAME A[10:3] RESET FUNCTION x A[10:3] of Y-buffer base address (padded with 3 LSB of zeros for a total of 11 bits). This value is set by the MCU. UBM or DMA uses this value as the start address of a given transaction. Furthermore, UBM or DMA does not change this value at the end of a transaction. 7.5.4.11 IEPBCTY_n: Input Endpoint Y-Byte Count (n = 1 to 3) 7 NAK R/W 6 C6 R/W 5 C5 R/W 4 C4 R/W 3 C3 R/W 2 C2 R/W 1 C1 R/W 0 C0 R/W 1 S1 R/W 0 S0 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 6–0 C[6:0] x 7 NAK x FUNCTION X-Buffer Byte count: 000 0000b → Count = 0 000 0001b → Count = 1 byte . . . 011 1111b → Count = 63 bytes 100 0000b → Count = 64 bytes Any value ≥ 100 0001b produces unpredictable results. NAK = 0 Buffer contains a valid packet for host-in transaction NAK = 1 Buffer is empty (host-in request is NAK) 7.5.4.12 IEPSIZXY_n: Input Endpoint X-/Y-Buffer Size (n = 1 to 3) 7 RSV R/O 6 S6 R/W 5 S5 R/W 4 S4 R/W 3 S3 R/W 2 S2 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION 6–0 S[6:0] x X- and Y-Buffer size: 000 0000b → Count = 0 000 0001b → Count = 1 byte . . . 011 1111b → Count = 63 bytes 100 0000b → Count = 64 bytes Any value ≥ 100 0001b produces unpredictable results. 7 RSV x Reserved Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 21 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.5 Endpoint-0 Descriptor Registers Unlike EDB-1 to EDB-3, which are defined as memory entries in SRAM, endpoint-0 is described by a set of four registers (two for output and two for input). Table 6 defines the registers and their respective addresses used for EDB-0 description. EDB-0 has no Base-Address Register, because these addresses are hardwired to FEF8 and FEF0. Note that the bit positions have been preserved to provide consistency with EDB-n (n = 1 to 3). Table 6. Input/Output EDB-0 Registers ADDRESS REGISTER NAME DESCRIPTION FF83 OEPBCNT_0 Output endpoint_0: byte-count register FF82 OEPCNFG_0 Output endpoint_0: configuration register FF81 IEPBCNT_0 Input endpoint_0: byte-count register FF80 IEPCNFG_0 Input endpoint_0: configuration register BASE ADDRESS FEF0 FEF8 7.5.5.1 IEPCNFG_0: Input Endpoint-0 Configuration Register 7 UBME R/W 6 RSV R/O 5 TOGLE R/O 4 RSV R/O 3 STALL R/W 2 USBIE R/W 1 RSV R/O 0 RSV R/O LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 1–0 RSV 0 FUNCTION Reserved USB interrupt enable on transaction completion. Set/cleared by the MCU 2 USBIE 0 USBIE = 0 No interrupt USBIE = 1 Interrupt on transaction completion USB stall condition indication. Set/cleared by the MCU 3 STALL 0 STALL = 0 No stall STALL = 1 USB stall condition. If set by the MCU, a STALL handshake is initiated and the bit is cleared automatically by the next setup transaction. 4 RSV 0 Reserved 5 TOGLE 0 USB toggle bit. This bit reflects the toggle sequence bit of DATA0, DATA1. 6 RSV 0 Reserved UBM enable/disable bit. Set/cleared by the MCU 7 22 UBME 0 UBME = 0 UBM cannot use this endpoint. UBME = 1 UBM can use this endpoint. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.5.2 IEPBCNT_0: Input Endpoint-0 Byte-Count Register 7 NAK R/W 6 RSV R/O 5 RSV R/O 4 RSV R/O 3 C3 R/W 2 C2 R/W 1 C1 R/W 0 C0 R/W 1 RSV R/O 0 RSV R/O LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 3–0 C[3:0] 0000 6–4 RSV 0 7 NAK 1 FUNCTION Byte count: 0000b → Count = 0 . . . 0111b → Count = 7 1000b → Count = 8 1001b to 1111b are reserved. (If used, defaults to 8) Reserved NAK = 0 Buffer contains a valid packet for host-in transaction. NAK = 1 Buffer is empty (host-in request is NAK). 7.5.5.3 OEPCNFG_0: Output Endpoint-0 Configuration Register 7 UBME R/W 6 RSV R/O 5 TOGLE R/O 4 RSV R/O 3 STALL R/W 2 USBIE R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 1–0 RSV 0 2 USBIE 0 FUNCTION Reserved USB interrupt enable on transaction completion. Set/cleared by the MCU USBIE = 0 No interrupt USBIE = 1 Interrupt on transaction completion USB stall condition indication. Set/cleared by the MCU 3 STALL 0 STALL = 0 No stall STALL = 1 USB stall condition. If set by the MCU, a STALL handshake is initiated and the bit is cleared automatically. 4 RSV 0 Reserved 5 TOGLE 0 USB toggle bit. This bit reflects the toggle sequence bit of DATA0, DATA1. 6 RSV 0 Reserved 7 UBME 0 UBM enable/disable bit. Set/cleared by the MCU UBME = 0 UBM cannot use this endpoint. UBME = 1 UBM can use this endpoint. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 23 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.5.4 OEPBCNT_0: Output Endpoint-0 Byte-Count Register 7 NAK R/W 6 RSV R/O 5 RSV R/O 4 RSV R/O 3 C3 R/W 2 C2 R/W 1 C1 R/W 0 C0 R/W 1 FA1 R/W 0 FA0 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 3–0 C[3:0] 0000 6–4 RSV 0 7 NAK 1 FUNCTION Byte count: 0000b → Count = 0 . . . 0111b → Count = 7 1000b → Count = 8 1001b to 1111b are reserved (if used, defaults to 8). Reserved = 0 NAK = 0 No valid data in buffer. Ready for host-out NAK = 1 Buffer contains a valid packet from host (NAK the host). 7.5.6 USB Registers 7.5.6.1 FUNADR: Function Address Register This register contains the device function address. 7 RSV R/O 6 FA6 R/W 5 FA5 R/W 4 FA4 R/W 3 FA3 R/W 2 FA2 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT 24 NAME 6–0 FA[6:0] 7 RSV RESET FUNCTION These bits define the current device address assigned to the function. The MCU writes a value to this 000 0000 register as a result of a SET-ADDRESS host command. 0 Reserved Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.6.2 USBSTA: USB Status Register All bits in this register are set by the hardware and are cleared by the MCU when writing a 1 to the proper bit location (writing a 0 has no effect). In addition, each bit can generate an interrupt if its corresponding mask bit is set (R/C notation indicates read and clear only by the MCU). 7 RSTR R/C 6 SUSR R/C 5 RESR R/C 4 PWOFF R/C 3 PWON R/C 2 SETUP R/C 1 RSV R/O 0 STPOW R/C LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION SETUP overwrite bit. Set by hardware when setup packet is received while there is already a packet in the setup buffer. 0 1 STPOW RSV 0 0 STPOW = 0 MCU can clear this bit by writing a 1. (Writing 0 has no effect.) STPOW = 1 SETUP overwrite Reserved SETUP transaction received bit. As long as SETUP is 1, IN and OUT on endpoint-0 are NAK regardless of the value of their real NAK bits. 2 SETUP 0 SETUP = 0 MCU can clear this bit by writing a 1. (Writing 0 has no effect.) SETUP = 1 SETUP transaction has been received. Power-on request for port 3.This bit indicates if power on to port 3 has been received. This bit generates a PWON interrupt (if enabled). 3 PWON 0 PWON = 0 MCU can clear this bit by writing a 1. (Writing 0 has no effect.) PWON = 1 Power on to port 3 has been received. Power-off request for port 3. This bit indicates whether power off to port 3 has been received. This bit generates a PWOFF interrupt (if enabled). 4 PWOFF 0 PWOFF = 0 MCU can clear this bit by writing a 1. (Writing 0 has no effect.) PWOFF = 1 Power off to port 3 has been received. Function resume request bit 5 RESR 0 RESR = 0 MCU can clear this bit by writing a 1. (Writing 0 has no effect.) RESR = 1 Function resume is detected. Function suspended request bit. This bit is set in response to a global or selective suspend condition. 6 SUSR 0 SUSR = 0 MCU can clear this bit by writing a 1. (Writing 0 has no effect.) SUSR = 1 Function suspend is detected. Function reset request bit. This bit is set in response to host initiating a port reset. This bit is not affected by USB function reset. 7 RSTR 0 RSTR = 0 MCU can clear this bit by writing a 1. (Writing 0 has no effect.) RSTR = 1 Function reset is detected. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 25 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.6.3 USBMSK: USB Interrupt Mask Register 7 RSTR R/W 6 SUSR R/W 5 RESR R/W 4 PWOFF R/W 3 PWON R/W 2 SETUP R/W 1 RSV R/O 0 STPOW R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION SETUP overwrite interrupt enable bit 0 STPOW 0 1 RSV 0 2 SETUP 0 STPOW = 0 STPOW interrupt disabled STPOW = 1 STPOW interrupt enabled Reserved = 0 SETUP interrupt enable bit SETUP = 0 SETUP interrupt disabled SETUP = 1 SETUP interrupt enabled Power-on interrupt enable bit 3 PWON 0 PWON = 0 PWON interrupt disabled PWON = 1 PWON interrupt enabled Power-off interrupt enable bit 4 PWOFF 0 PWOFF = 0 PWOFF interrupt disabled PWOFF = 1 PWOFF interrupt enabled Function resume interrupt enable 5 RESR 0 RESR = 0 Function resume interrupt disabled RESR = 1 Function resume interrupt enabled Function suspend interrupt enable 6 SUSR 0 SUSR = 0 Function suspend interrupt disabled SUSR = 1 Function suspend interrupt enabled Function reset interrupt enable 7 26 RSTR 0 RSTR = 0 Function reset interrupt disabled RSTR = 1 Function reset interrupt enabled Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.6.4 USBCTL: USB Control Register Unlike the other registers, this register is cleared by the power-up-reset signal only. The USB reset cannot reset this register (see the reset diagram in Figure 3). 7 CONT R/W 6 RSV R/O 5 RWUP R/W 4 FRSTE R/W 3 RWE R/W 2 B/S R/O 1 SIR R/W 0 DIR R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION As a response to a setup packet, the MCU decodes the request and sets or clears this bit to reflect the data transfer direction. 0 DIR 0 DIR = 0 USB data OUT transaction (from host to TUSB3210) DIR = 1 USB data IN transaction (from TUSB3210 to host) SETUP interrupt status bit. This bit is controlled by the MCU to indicate to the hardware when the SETUP interrupt is being served. 1 SIR 0 SIR = 0 SETUP interrupt is not served. MCU clears this bit before exiting the SETUP interrupt routine. SIR = 1 SETUP interrupt is in progress. MCU sets this bit when servicing the SETUP interrupt. Bus-/self-power control bit 2 B/S 0 B/S = 0 The device is bus-powered. B/S = 1 The device is self-powered. Remote wake-up enable bit 3 RWE 0 RWE = 0 MCU clears this bit when host sends command to clear the feature. RWE = 1 MCU writes 1 to this bit when host sends set device feature command to enable the remote wake-up feature Function reset connection bit. This bit connects/disconnects the USB function reset from the MCU reset. 4 FRSTE 1 FRSTE = 0 Function reset is not connected to the MCU reset. FRSTE = 1 Function reset is connected to the MCU reset. Device remote wake-up request. This bit is set by the MCU and is cleared automatically. 5 RWUP 0 6 RSV 0 7 CONT 0 RWUP = 0 Writing a 0 to this bit has no effect. RWUP = 1 When the MCU writes a 1, a remote wake-up pulse is generated. Reserved Connect and Disconnect bit CONT = 0 Upstream port is disconnected. Pullup disabled CONT = 1 Upstream port is connected. Pullup enabled Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 27 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.6.5 VIDSTA: VID/PID Status Register This register is used to read the value on four external pins. The firmware can use this value to select one of the vendor identification/product identifications (VID/PID) stored in memory. The TUSB3210 supports up to 16 unique VID/PIDs with application code to support different products. This provides a unique opportunity for original equipment manufacturers (OEMs) to have one device to support up to 16 different product lines by using S0–S3 to select VID/PID and behavioral application code for the selected product. 7 RSV R/O 6 RSV R/O 5 RSV R/O 4 RSV R/O 3 S3 R/O 2 S2 R/O 1 S1 R/O 0 S0 R/O LEGEND: R/W = Read/Write; R = Read only; -n = value after reset (1) BIT NAME RESET FUNCTION 3–0 S[3:0] x VID/PID selection bits. These bits reflect the status of the external pins as defined by Table 7 (1). 7–4 RSV 0 Reserved = 0 A pin tied low is reflected as a 0 and a pin tied high is reflected as a 1. Table 7. External Pin Mapping to S[3:0] in VIDSTA Register VIDSTA REGISTER, S[3:0] PIN COMMENTS NO. NAME S0 58 P3.0 Dual function P3.0 I/O or S0 input S1 57 P3.1 Dual function P3.1 I/O or S1 input S2 8 S2 S2-pin is input S3 9 S3 S3-pin is input 7.5.7 Function Reset and Power-Up Reset Interconnect Figure 3 represents the logical connection of the USB-function-reset (USBR) and power-up-reset (RST) pins. The internal RESET signal is generated from the RST pin (PURS signal) or from the USB-reset (USBR signal). The USBR can be enabled or disabled by the FRSTE bit in the USBCTL register (on power up FRSTE = 0). The internal RESET is used to reset all registers and logic, with the exception of the USBCTL and MISCTL registers. The USBCTL and MCU configuration registers (MCNFG) are cleared by the PURS signal only. USBCTL Register MCNFG Register All Internal MMR RST PURS RESET USBR MCU WDT Reset WDE USB Function Reset FRSTE Figure 3. Reset Diagram 28 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.8 Pullup Resistor Connect and Disconnect After reading firmware into RAM, the TUSB3210 can re-enumerate using the new firmware (no need to physically disconnect and reconnect the cable). Figure 4 shows an equivalent circuit implementation for Connect and Disconnect from a USB upstream port (also see Figure 11b). When the CONT bit in the USBCTL register is 1, the CMOS driver sources VDD to the pullup resistor (PUR pin) presenting a normal connect condition to the USB hub (high speed). When the CONT bit is 0, the PUR pin is driven low. In this state, the 1.5-kΩ resistor is connected to GND, resulting in device disconnection state. The PUR driver is a CMOS driver that can provide VDD – 0.1 V minimum at 8 mA of source current. CMOS PUR 1.5 kΩ TUSB2036A HUB CONT-Bit D+ DP0 D- DM0 15 kΩ 15 kΩ TUSB3210 Figure 4. Pullup Resistor Connect and Disconnect Circuit 7.5.9 8052 Interrupt and Status Registers All seven 8052-standard interrupt sources are preserved (see Table 8). SIE is the standard interrupt enable register, which controls the seven interrupt sources. All the additional interrupt sources are connected together as an OR to generate INT0. The INT0 signal is provided to interrupt the MCU (see interrupt connection diagram, Figure 5). Table 8. 8052 Interrupt Location Map INTERRUPT SOURCE DESCRIPTION START ADDRESS ET2 Timer-2 interrupt 002Bh ES UART interrupt 0023h 001Bh ET1 Timer-1 interrupt EX1 Internal INT1 or INT1 0013h ET0 Timer-0 interrupt 000Bh INT0 Internal INT0 0003h Reset COMMENTS Used for P2[7:0] interrupt Used for all internal peripherals 0000h Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 29 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.9.1 8052 Standard Interrupt Enable Register 7 EA R/W 6 RSV R/O 5 ET2 R/O 4 ES R/W 3 ET1 R/W 2 EX1 R/W 1 ET0 R/W 0 INT0 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION Enable or disable interrupt-0 0 INT0 0 INT0 = 0 Interrupt-0 is disabled. INT0 = 1 Interrupt-0 is enabled. Enable or disable timer-0 interrupt 1 ET0 0 ET0 = 0 Timer-0 interrupt is disabled. ET0 = 1 Timer-0 interrupt is enabled. Enable or disable interrupt-1 2 EX1 0 EX1 = 0 Interrupt-1 is disabled. EX1 = 1 Interrupt-1 is enabled. Enable or disable timer-1 interrupt 3 ET1 0 ET1 = 0 Timer-1 interrupt is disabled. ET1 = 1 Timer-1 interrupt is enabled. Enable or disable serial port interrupts 4 ES 0 ES = 0 Serial port interrupt is disabled. ES = 1 Serial port interrupt is enabled. Enable or disable timer-2 interrupt 5 ET2 0 6 RSV 0 7 EA 0 ET1 = 0 Timer-2 interrupt is disabled. ET1 = 1 Timer-2 interrupt is enabled. Reserved Enable or disable all interrupts (global disable) EA = 0 Disable all interrupts. EA = 1 Each interrupt source is individually controlled. 7.5.9.2 Additional Interrupt Sources All nonstandard 8052 interrupts (USB, I2C, and so on) are connected as an OR to generate an internal INT0. It must be noted that the external INT0 and INT1 are not used. Furthermore, INT0 must be programmed as an active-low level interrupt (not edge-triggered). A vector interrupt register is provided to identify all interrupt sources (see vector interrupt register definition, VECINT: Vector Interrupt Register). Up to 64 interrupt vectors are provided. It is the responsibility of the MCU to read the vector and dispatch the proper interrupt routine. 30 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.9.3 VECINT: Vector Interrupt Register This register contains a vector value identifying the internal interrupt source that trapped to location 0003h. Writing any value to this register removes the vector and updates the next vector value (if another interrupt is pending). Note that the vector value is offset. Therefore, its value is in increments of two (bit 0 is set to 0). When no interrupt is pending, the vector is set to 00h. Table 9 lists the vector interrupt values. As shown, the interrupt vector is divided into two fields; I[2:0] and G[3:0]. The I-field defines the interrupt source within a group (on a firstcome, first-served basis) and the G-field defines the group number. Group G0 is the lowest and G15 is the highest priority. 7 G3 R/W 6 G2 R/W 5 G1 R/W 4 G0 R/W 3 I2 R/W 2 I1 R/W 1 I0 R/W 0 RSV R/O LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 0 RSV 0 FUNCTION 3–1 I[2:0] 000 This field defines the interrupt source in a given group. See Table 9: Vector Interrupt Values. Bit 0 is always 0; therefore, vector values are offset by two. 7–4 G[3:0] 0000 This field defines the interrupt group. I[2:0] and G[3:0] combine to produce the actual interrupt vector. Reserved Table 9. Vector Interrupt Values G[3:0] (Hex) I[2:0] (Hex) VECTOR (Hex) 0 0 00 No interrupt INTERRUPT SOURCE 1 0 10 RESERVED 1 1 12 Output endpoint-1 1 2 14 Output endpoint-2 Output endpoint-3 1 3 16 1 4–7 18–1E RESERVED 2 0 20 RESERVED 2 1 22 Input endpoint-1 2 2 24 Input endpoint-2 2 3 26 Input endpoint-3 2 4–7 28–2E 3 0 30 STPOW packet received 3 1 32 SETUP packet received 3 2 34 PWON interrupt 3 3 36 PWOFF interrupt 3 4 38 RESR interrupt 3 5 3A SUSR interrupt 3 6 3C RSTR interrupt 3 7 3E RESERVED 4 0 40 I2C TXE interrupt 4 1 42 I2C RXF interrupt 4 2 44 Input endpoint-0 4 3 46 Output endpoint-0 4 4–7 48–4E RESERVED 5–F X 90–FE RESERVED RESERVED Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 31 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.9.4 Logical Interrupt Connection Diagram (INT0) Figure 5 represents the logical connection of the interrupt sources and the relation of the logical connection with INT0. The priority encoder generates an 8-bit vector, corresponding to 64 interrupt sources (not all are used). The interrupt priorities are hard wired. Vector 46h is the highest and 12h is the lowest. Table 9 lists the interrupt source for each valid interrupt vector. Interrupts Priority Encoder 46h L Interrupt Sources INT0 12h Vector Figure 5. Internal Vector Interrupt (INT0) 7.5.9.5 P2[7:0], P3.3 Interrupt (INT1) Figure 6 illustrates the conceptual port-2 interrupt. All port-2 input signals are connected in a logical OR to generate the INT1 interrupt. Note that the inputs are active-low and INT1 is programmed as a level-triggered interrupt. In addition, INT1 is connected to the suspend/resume logic for remote wake-up support. As illustrated, the XINT bit in the MCU configuration register (MCNFG) is used to select the EX1 interrupt source. When XINT = 0, P3.3 is the source, and when XINT = 1, P2[7:0] is the source. The programmable delay is determined by the setting of I[3:0] in the INTCFG register. P2[7:0] INT1 Programmable Delay P3.3 Suspend/ Resume Logic XINT Bit Figure 6. P2[7:0], P3.3 Input Port Interrupt Generation 32 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.10 I2C Registers The TUSB3210 device only supports a master-slave relationship; therefore, it does not support bus arbitration. 7.5.10.1 I2CSTA: I 2C Status and Control Register This register is used to control the stop condition for read and write operations. In addition, it provides transmitter and receiver handshake signals with their respective interrupt enable bits. 7 RXF R/C 6 RIE R/W 5 ERR R/C 4 1/4 R/W 3 TXE R/C 2 TIE R/W 1 SRD R/W 0 SWR R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET FUNCTION Stop write condition. This bit defines whether the I2C controller generates a stop condition when data from the I2CDAO register is transmitted to an external device. 0 SWR 0 SWR = 0 Stop condition is not generated when data from the I2CDAO register is shifted out to an external device. SWR = 1 Stop condition is generated when data from the I2CDAO register is shifted out to an external device. Stop read condition. This bit defines whether the I2C controller generates a stop condition when data is received and loaded into I2CDAI register. 1 SRD 0 SRD = 0 Stop condition is not generated when data from SDA line is shifted into the I2CDAI register. SRD = 1 Stop condition is generated when data from SDA line is shifted into the I2CDAI register. I2C transmitter empty interrupt enable 2 TIE 0 TIE = 0 Interrupt disabled TIE = 1 Interrupt enabled 2 I C transmitter empty. This bit indicates that data can be written to the transmitter. It can be used for polling or it can generate an interrupt. 3 TXE 1 TXE = 0 Transmitter is full. This bit is cleared when the MCU writes a byte to the I2CDAO register. TXE = 1 Transmitter is empty. The I2C controller sets this bit when the content of the I2CDAO register is copied to the SDA shift register. Bus speed selection 4 1/4 0 1/4 = 0 100-kHz bus speed 1/4 = 1 400-kHz bus speed Bus error condition. This bit is set by the hardware when the device does not respond. It is cleared by the MCU. 5 ERR 0 ERR = 0 No bus error ERR = 1 Bus error condition has been detected. Clears when the MCU writes a 1. Writing a 0 has no effect. I2C receiver ready interrupt enable 6 RIE 0 RIE = 0 Interrupt disabled RIE = 1 Interrupt enabled I2C receiver full. This bit indicates that the receiver contains new data. It can be used for polling or it can generate an interrupt. 7 RXF 0 RXF = 0 Receiver is empty. This bit is cleared when the MCU reads the I2CDAI register. RXF = 1 Receiver contains new data. This bit is set by the I2C controller when the received serial data has been loaded into the I2CDAI register. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 33 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.10.2 I2CADR: I 2C Address Register This register holds the device address and the read/write command bit. 7 A6 R/W 6 A5 R/W 5 A4 R/W 4 A3 R/W 3 A2 R/W 2 A1 R/W 1 A0 R/W 0 R/W R/W 2 D2 R/O 1 D1 R/O 0 D0 R/O LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME RESET 0 R/W 0 FUNCTION Read/write command bit 7–1 A[6:0] R/W = 0 Write operation R/W = 1 Read operation 000 0000 Seven address bits for device addressing 7.5.10.3 I2CDAI: I 2C Data-Input Register This register holds the received data from an external device. 7 D7 R/O 6 D6 R/O 5 D5 R/O 4 D4 R/O 3 D3 R/O LEGEND: R/W = Read/Write; R = Read only; -n = value after reset BIT NAME 7–0 D[7:0] RESET 0 FUNCTION 2 8-bit input data from an I C device 7.5.10.4 I2CDAO: I 2C Data-Output Register This register holds the data to be transmitted to an external device. Writing to this register starts the transfer on the SDA line. 7 D7 R/W 6 D6 R/W 5 D5 R/W 4 D4 R/W 3 D3 R/W 2 D2 R/W 1 D1 R/W 0 D0 R/W LEGEND: R/W = Read/Write; R = Read only; -n = value after reset 34 BIT NAME RESET 7–0 D[7:0] 0 FUNCTION 8-bit output data to an I2C device Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.11 Read/Write Operations 7.5.11.1 Read Operation (Serial EEPROM) A serial read requires a dummy byte write sequence to load in the 16-bit data word address. When the device address word and data address word are clocked out and acknowledged by the device, the MCU starts a current address sequence. The following describes the sequence of events to accomplish this transaction: Device Address + EEPROM [High Byte] 1. The MCU sets I2CSTA[SRD] = 0.This prevents the I2C controller from generating a stop condition after the content of the I2CDAI register is received. 2. The MCU sets I2CSTA[SWR] = 0. This prevents the I2C controller from generating a stop condition after the content of the I2CDAO register is transmitted. 3. The MCU writes the device address (R/W bit = 0) to the I2CADR register (write operation). 4. The MCU writes the high byte of the EEPROM address into the I2CDAO register, starting the transfer on the SDA line. 5. The TXE bit in I2CSTA is cleared, indicating busy. 6. The content of the I2CADR register is transmitted to the EEPROM (preceded by start condition on SDA). 7. The content of the I2CDAO register is transmitted to the EEPROM (EEPROM address). 8. The TXE bit in I2CSTA is set, and interrupts the MCU, indicating that the I2CDAO register has been transmitted. 9. No stop condition is generated. EEPROM [Low Byte] 1. The MCU writes the low byte of the EEPROM address into the I2CDAO register. 2. The TXE bit in I2CSTA is cleared, indicating busy. 3. The content of the I2CDAO register is transmitted to the device (EEPROM address). 4. The TXE bit in I2CSTA is set, and interrupts the MCU, indicating that the I2CDAO register has been transmitted. 5. This completes the dummy write operation. At this point, the EEPROM address is set and the MCU can do a single or a sequential read operation. 7.5.11.2 Current Address Read Operation When the EEPROM address is set, the MCU can read a single byte by executing the following steps: 1. The MCU sets I2CSTA[SRD] = 1, forcing the I2C controller to generate a stop condition after the I2CDAI register is received. 2. The MCU writes the device address (R/W bit = 1) to the I2CADR register (read operation). 3. The MCU writes a dummy byte to the I2CDAO register, starting the transfer on the SDA line. 4. The RXF bit in I2CSTA is cleared. 5. The content of the I2CADR register is transmitted to the device, preceded by a start condition on SDA. 6. Data from the EEPROM is latched into the I2CDAI register (stop condition is transmitted). 7. The RXF bit in I2CSTA is set, and interrupts the MCU, indicating that the data is available. 8. The MCU reads the I2CDAI register. This clears the RXF bit (I2CSTA[RXF] = 0). Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 35 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.11.3 Sequential Read Operation When the EEPROM address is set, the MCU can execute a sequential read operation by executing the following steps: NOTE This example illustrates a 32-byte sequential read. 1. Device Address (a) The MCU sets I2CSTA[SRD] = 0. This prevents the I2C controller from generating a stop condition after the I2CDAI register is received. (b) The MCU writes the device address (R/W bit = 1) to the I2CADR register (read operation). (c) The MCU writes a dummy byte to the I2CDAO register, starting the transfer on the SDA line. (d) The RXF bit in I2CSTA is cleared. (e) The content of the I2CADR register is transmitted to the device (preceded by a start condition on SDA). 2. N-Byte Read (31 bytes) (a) Data from the device is latched into the I2CDAI register (stop condition is not transmitted). (b) The RXF bit in I2CSTA is set and interrupts the MCU, indicating that data is available. (c) The MCU reads the I2CDAI register, clearing the RXF bit (I2CSTA[RXF] = 0). (d) This operation repeats 31 times. 3. Last-Byte Read (byte no. 32) (a) The MCU sets I2CSTA[SRD] = 1. This forces the I2C controller to generate a stop condition after the I2CDAI register is received. (b) Data from the device is latched into the I2CDAI register (stop condition is transmitted). (c) The RXF bit in I2CSTA is set and interrupts the MCU, indicating that data is available. (d) The MCU reads the I2CDAI register, clearing the RXF bit (I2CSTA[RXF] = 0). 36 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 7.5.11.4 Write Operation (Serial EEPROM) The byte write operation involves three phases: 1) device address + EEPROM [high byte] phase, 2) EEPROM [low byte] phase, and 3) EEPROM [DATA]. The following describes the sequence of events to accomplish the byte write transaction: Device Address + EEPROM [High Byte] 1. The MCU sets I2CSTA[SWR] = 0. This prevents the I2C controller from generating a stop condition after the content of the I2CDAO register is transmitted. 2. The MCU writes the device address (R/W bit = 0) to the I2CADR register (write operation). 3. The MCU writes the high byte of the EEPROM address into the I2CDAO register, starting the transfer on the SDA line. 4. The TXE bit in I2CSTA is cleared, indicating busy. 5. The content of the I2CADR register is transmitted to the device (preceded by a start condition on SDA). 6. The content of the I2CDAO register is transmitted to the device (EEPROM high-address). 7. The TXE bit in I2CSTA is set and interrupts the MCU, indicating that the I2CDAO register has been transmitted. EEPROM [Low Byte] 1. The MCU writes the low byte of the EEPROM address into the I2CDAO register. 2. The TXE bit in I2CSTA is cleared, indicating busy. 3. The content of the I2CDAO register is transmitted to the device (EEPROM address). 4. The TXE bit in I2CSTA is set and interrupts the MCU, indicating that the I2CDAO register has been transmitted. EEPROM [DATA] 1. The MCU sets I2CSTA[SWR] = 1. This forces the I2C controller to generate a stop condition after the content of the I2CDAO register is transmitted. 2. The MCU writes the DATA to be written to the EEPROM into the I2CDAO register. 3. The TXE bit in I2CSTA is cleared, indicating busy. 4. The content of the I2CDAO register is transmitted to the device (EEPROM data). 5. The TXE bit in I2CSTA is set and interrupts the MCU, indicating that the I2CDAO register has been transmitted. 6. The I2C controller generates a stop condition after the content of the I2CDAO register is transmitted. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 37 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 7.5.11.5 Page Write Operation The page write operation is initiated the same way as byte write, with the exception that a stop condition is not generated after the first EEPROM [DATA] is transmitted. The following describes the sequence of writing 32 bytes in page mode: Device Address + EEPROM [High Byte] 1. The MCU sets I2CSTA[SWR] = 0. This prevents the I2C controller from generating a stop condition after the content of the I2CDAO register is transmitted. 2. The MCU writes the device address (R/W bit = 0) to the I2CADR register (write operation). 3. The MCU writes the high byte of the EEPROM address into the I2CDAO register. 4. The TXE bit in I2CSTA is cleared, indicating busy. 5. The content of the I2CADR register is transmitted to the device (preceded by a start condition on SDA). 6. The content of the I2CDAO register is transmitted to the device (EEPROM address). 7. The TXE bit in I2CSTA is set and interrupts the MCU, indicating that the I2CDAO register has been sent. EEPROM [Low Byte] 1. The MCU writes the low byte of the EEPROM address into the I2CDAO register. 2. The TXE bit in I2CSTA is cleared, indicating busy. 3. The content of the I2CDAO register is transmitted to the device (EEPROM address). 4. The TXE bit in I2CSTA is set and interrupts the MCU, indicating that the I2CDAO register has been sent. 31 Bytes EEPROM [DATA] 1. The MCU writes the DATA to be written to the EEPROM into the I2CDAO register. 2. The TXE bit in I2CSTA is cleared, indicating busy. 3. The content of the I2CDAO register is transmitted to the device (EEPROM data). 4. The TXE bit in I2CSTA is set and interrupts the MCU, indicating that the I2CDAO register has been sent. 5. This operation repeats 31 times. Last Byte EEPROM [DATA] 1. The MCU sets I2CSTA[SWR] = 1. This forces the I2C controller to generate a stop condition after the content of the I2CDAO register is transmitted. 2. The MCU writes the last DATA byte to be written to the EEPROM into the I2CDAO register. 3. The TXE bit in I2CSTA is cleared, indicating busy. 4. The content of the I2CDAO register is transmitted to the EEPROM (EEPROM data). 5. The TXE bit in I2CSTA is set and interrupts the MCU, indicating that the I2CDAO register has been sent. 6. The I2C controller generates a stop condition after the content of the I2CDAO register is transmitted, terminating the 32-byte page write operation. 38 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 8 Application and Implementation NOTE Information in the following applications sections is not part of the TI component specification, and TI does not warrant its accuracy or completeness. TI’s customers are responsible for determining suitability of components for their purposes. Customers should validate and test their design implementation to confirm system functionality. 8.1 Application Information 8.1.1 Reset Timing There are three requirements for the reset signal timing. First, the minimum reset pulse duration is 100 μs. At power up, this time is measured from the time the power ramps up to 90% of the nominal VCC until the reset signal exceeds 1.2 V. The second requirement is that the clock must be valid during the last 60 μs of the reset window. The third requirement is that, according to the USB specification, the device must be ready to respond to the host within 100 ms. This means that within the 100-ms window, the device must come out of reset, load any pertinent data from the I2C EEPROM device, and transfer execution to the application firmware if any is present. Because the latter two events can require significant time, the amount of that can change from system to system, TI recommends having the device come out of reset within 30 ms, leaving 70 ms for the other events to complete. This means the reset signal should rise to 1.8 V within 30 ms. These requirements are depicted in Figure 7. Notice that when using a 12-MHz crystal or the 48-MHz oscillator, the clock signal may take several milliseconds to ramp up and become valid after power up. Therefore, the reset window may need to be elongated up to 10 ms or more to ensure that there is a 60-µs overlap with a valid clock. 3.3 V VCC CLK 90% RESET 1.8 V 1.2 V 0V t >60 µs 100 µs < RESET TIME RESET TIME < 30 ms Figure 7. Reset Timing Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 39 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com Application Information (continued) 8.1.2 Generic EVM The TUSB3210 generic EVM is designed for use with a personal computer running a USB-enabled operating system. The PC must be USB 1.1 specification compliant, which implies that the BIOS, chipsets, and operating system are all USB 1.1 specification compliant. If the BIOS is not specification compliant, the system may not boot up when USB devices are connected at power up, and the EVM may not function. NOTE An AC-DC power supply adapter is optional equipment (but included), because the EVM can function in either bus-powered mode or self-powered mode. Figure 8. Generic EVM 8.2 Typical Applications 8.2.1 Example LED Connection Figure 9 illustrates the port-3 pins that are assigned to drive the four example LEDs. For the connection example shown, P3[5:2] can sink up to 8 mA each (open-drain outputs). Figure 7 illustrates the downstream connection (only one port shown). VCC TUSB3210 P3.2 P3.3 P3.4 P3.5 Figure 9. Example LED Connection 40 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 Typical Applications (continued) 8.2.1.1 Design Requirements Table 10 lists the design requirements for the LED connection application. Table 10. Design Requirements DESIGN PARAMETER VALUE VCC Supply 3.3 V VDD1/8 1.8 V Upstream port USB (FS) FS XTAL 12 MHz 8.2.1.2 Detailed Design Procedure 8.2.1.2.1 Partial Connection Bus Power Mode Figure 10 illustrates the partial connection bus power mode. C5 C4 TPS76333 X1 3.3 V VR 5V X2 VCC SCL VCC SDA EPROM C1 C2 C3 R5 TUSB3210 R1 VCC 1.8VDD R2 VREN SUSP R3 Figure 10. Partial Connection Bus Power Mode 8.2.1.2.2 Upstream Connection Figure 11 shows the USB upstream connection. PUR Bus PWR (5 V) 3.3 V 1.5 kΩ 1.5 kΩ D+ DP0 D+ DP0 D- DM0 D- DM0 (a) (b) Figure 11. Upstream Connection (a) Non-Switching Power Mode (b) Switching Power Mode Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 41 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 8.2.1.2.3 Crystal Implementation Figure 12 shows the crystal implementation setup. R1 1M Y1 XI 12 MHz TUSB3210 22 pF XO CLOCK 22 pF Figure 12. Crystal Implementation Diagram 8.2.1.2.4 TUSB3210 Power Implementation Figure 13 shows the power implementation for the TUB3210 device. +3.3 V U1 1 Vbus 2 [Wait 10 ms before enable 3.3 V] R2 C1 0.1 µF 100K 3 C4 0.1 µF IN OUT 5 GND EN NC R18 4 TPS76333DBV +1.8 V C2 4.7 µF 100K R3 100K C5 4.7 µF Figure 13. Power Implementation Diagram 42 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 9 Power Supply Recommendations The TUSB3210 device requires a 3.3-V digital power source. The 3.3-V terminals are named VDD33 and supply power to most of the input and output cells. VDD33 supplies must have 0.1-µF bypass capacitors to VSS (ground) to ensure proper operation. One capacitor per power terminal is sufficient and must be placed as close to the terminal as possible to minimize trace length. TI recommends placing smaller value capacitors (like 0.01-µF) on the digital supply terminals. When placing and connecting all bypass capacitors, follow high-speed board design rules. 10 Layout 10.1 Layout Guidelines A primary concern when designing a system is accommodating and isolating high-speed signals. As highspeed signals are most likely to impact or be impacted by other signals, they must be laid out early (preferably first) in the PCB design process to ensure that prescribed routing rules can be followed. Table 11 outlines the signals requiring the most attention in a USB layout. Table 11. Critical Signals SIGNAL NAME DESCRIPTION DP USB 2.0 differential pair, positive DM USB 2.0 differential pair, negative SSTXP SuperSpeed differential pair, TX, positive SSTXN SuperSpeed differential pair, TX, negative SSRXP SuperSpeed differential pair, RX, positive SSRXN SuperSpeed differential pair, RX, negative 10.1.1 Differential Signal Spacing To minimize crosstalk in USB implementations, the spacing between the signal pairs must be a minimum of 5 times the width of the trace. This spacing is the 5-W rule. Also, maintain a minimum keep-out area of 30 mils to any other signal throughout the length of the trace. Where the USB differential pair abuts a clock or a periodic signal, increase this keep-out to a minimum of 50 mils to ensure proper isolation. DP 30 General Keep-Out 6 DM 8 6 50 High-Speed and Periodic Keep-out Figure 14. USB2 Differential Signal Spacing (mils) SPACE Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 43 TUSB3210 SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 www.ti.com 10.1.2 Differential Signal Rules • Do not place probe or test points on any USB differential signal. • Do not route USB traces under or near crystals, oscillators, clock signal generators, switching power regulators, mounting holes, magnetic devices, or ICs that use or duplicate clock signals. • After BGA breakout, keep USB differential signals clear of the SoC because high current transients produced during internal state transitions can be difficult to filter out. • When possible, route the USB differential pair signals on the top or bottom layer of the PCB with an adjacent GND layer. TI does not recommend stripline routing of the USB differential signals. • Ensure that USB differential signals are routed ≥ 90 mils from the edge of the reference plane. • Ensure that USB differential signals are routed at least 1.5 W (calculated trace-width × 1.5) away from voids in the reference plane. This rule does not apply where SMD pads on the USB differential signals are voided. • Maintain constant trace width after the SoC BGA escape to avoid impedance mismatches in the transmission lines. • Maximize differential pair-to-pair spacing when possible. For specific USB 2.0 layout guidelines, see the USB Layout Guidelines Application Report (SPRAAR7). 33 2 22 pF 1 6 2 1 1 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 2 1 1 4 2 3 USB Type B Connector 22 pF 2 13 14 15 16 TUSB3210 36 35 34 33 10.2 Layout Example 33 5 Figure 15. Layout Example for TUSB3210 44 Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 TUSB3210 www.ti.com SLLS466G – FEBRUARY 2001 – REVISED DECEMBER 2015 11 Device and Documentation Support 11.1 Documentation Support 11.1.1 Related Documentation For related documentation see the following: SPRAAR7 USB Layout Guidelines Application Report 11.2 Community Resources The following links connect to TI community resources. Linked contents are provided "AS IS" by the respective contributors. They do not constitute TI specifications and do not necessarily reflect TI's views; see TI's Terms of Use. TI E2E™ Online Community TI's Engineer-to-Engineer (E2E) Community. Created to foster collaboration among engineers. At e2e.ti.com, you can ask questions, share knowledge, explore ideas and help solve problems with fellow engineers. Design Support TI's Design Support Quickly find helpful E2E forums along with design support tools and contact information for technical support. 11.3 Trademarks E2E is a trademark of Texas Instruments. All other trademarks are the property of their respective owners. 11.4 Electrostatic Discharge Caution These devices have limited built-in ESD protection. The leads should be shorted together or the device placed in conductive foam during storage or handling to prevent electrostatic damage to the MOS gates. 11.5 Glossary SLYZ022 — TI Glossary. This glossary lists and explains terms, acronyms, and definitions. 12 Mechanical, Packaging, and Orderable Information The following pages include mechanical, packaging, and orderable information. This information is the most current data available for the designated devices. This data is subject to change without notice and revision of this document. For browser-based versions of this data sheet, refer to the left-hand navigation. Submit Documentation Feedback Copyright © 2001–2015, Texas Instruments Incorporated Product Folder Links: TUSB3210 45 PACKAGE OPTION ADDENDUM www.ti.com 4-May-2018 PACKAGING INFORMATION Orderable Device Status (1) Package Type Package Pins Package Drawing Qty Eco Plan Lead/Ball Finish MSL Peak Temp (2) (6) (3) Op Temp (°C) Device Marking (4/5) TUSB3210PM LIFEBUY LQFP PM 64 160 Green (RoHS & no Sb/Br) CU NIPDAU Level-3-260C-168 HR 0 to 70 TUSB3210PM TUSB3210PMG4 LIFEBUY LQFP PM 64 160 Green (RoHS & no Sb/Br) CU NIPDAU Level-3-260C-168 HR 0 to 70 TUSB3210PM (1) The marketing status values are defined as follows: ACTIVE: Product device recommended for new designs. LIFEBUY: TI has announced that the device will be discontinued, and a lifetime-buy period is in effect. NRND: Not recommended for new designs. Device is in production to support existing customers, but TI does not recommend using this part in a new design. PREVIEW: Device has been announced but is not in production. Samples may or may not be available. OBSOLETE: TI has discontinued the production of the device. (2) RoHS: TI defines "RoHS" to mean semiconductor products that are compliant with the current EU RoHS requirements for all 10 RoHS substances, including the requirement that RoHS substance do not exceed 0.1% by weight in homogeneous materials. Where designed to be soldered at high temperatures, "RoHS" products are suitable for use in specified lead-free processes. TI may reference these types of products as "Pb-Free". RoHS Exempt: TI defines "RoHS Exempt" to mean products that contain lead but are compliant with EU RoHS pursuant to a specific EU RoHS exemption. Green: TI defines "Green" to mean the content of Chlorine (Cl) and Bromine (Br) based flame retardants meet JS709B low halogen requirements of
TUSB3210PM 价格&库存

很抱歉,暂时无法提供与“TUSB3210PM”相匹配的价格&库存,您可以联系我们找货

免费人工找货