SLAA457B September   2013  – October 2018 MSP430F5500 , MSP430F5501 , MSP430F5502 , MSP430F5503 , MSP430F5504 , MSP430F5505 , MSP430F5506 , MSP430F5507 , MSP430F5508 , MSP430F5509 , MSP430F5510 , MSP430F5513 , MSP430F5514 , MSP430F5515 , MSP430F5517 , MSP430F5519 , MSP430F5521 , MSP430F5522 , MSP430F5524 , MSP430F5525 , MSP430F5526 , MSP430F5527 , MSP430F5528 , MSP430F5529 , MSP430F5630 , MSP430F5631 , MSP430F5632 , MSP430F5633 , MSP430F5634 , MSP430F5635 , MSP430F5636 , MSP430F5637 , MSP430F5638 , MSP430F5658 , MSP430F5659 , MSP430F6630 , MSP430F6631 , MSP430F6632 , MSP430F6633 , MSP430F6634 , MSP430F6635 , MSP430F6636 , MSP430F6637 , MSP430F6638 , MSP430F6658 , MSP430F6659 , MSP430FG6425 , MSP430FG6426 , MSP430FG6625 , MSP430FG6626

 

  1.   Starting a USB Design Using MSP430™ MCUs
    1.     Trademarks
    2. 1 USB and the Art of Making Something Complex Look Simple
      1. 1.1 What Has Made USB So Successful?
      2. 1.2 But It Looks So Simple!
      3. 1.3 TI's Approach for MSP430 USB
    3. 2 MSP430 USB Silicon
      1. 2.1 How MSP430 Devices are Documented
      2. 2.2 USB-Equipped MSP430 Derivatives
      3. 2.3 MSP430 USB Module
      4. 2.4 USB Certification of the Silicon
    4. 3 Software
      1. 3.1 USB Developers Package: Overview
      2. 3.2 USB API Stacks: Features
      3. 3.3 MSP430 USB Descriptor Tool
      4. 3.4 Host Software, and the Java HID Demo App
      5. 3.5 USB API Programmer's Guide and Examples Guide
      6. 3.6 MSP430 USB Field Firmware Upgrade Tools
    5. 4 MSP430 USB Hardware Design
      1. 4.1 TI Reference Design for USB Interface
      2. 4.2 Selecting a Power Configuration
      3. 4.3 Selecting a Clock Configuration
        1. 4.3.1 Choosing a Source
        2. 4.3.2 Choosing a Frequency
      4. 4.4 Other Reference Design Commentary
    6. 5 MSP430 USB Software Design
      1. 5.1 How to Choose a USB Device Class
      2. 5.2 How to Select a Vendor ID (VID) and Product ID (PID)
        1. 5.2.1 What are the VID and PID?
        2. 5.2.2 How are They Chosen (or Obtained)?
        3. 5.2.3 Using VIDs and PIDs During Development
    7. 6 Getting Started: Evaluating MSP430 USB
      1. 6.1 Software Development Environments
      2. 6.2 F5529 LaunchPad Development Kit
      3. 6.3 MSP430F5529 USB Experimenter's Board
      4. 6.4 FET Target Boards
    8. 7 More Information
  2.   A USB Glossary
  3.   Revision History

4.2 Selecting a Power Configuration

The USB host provides 5-V power over the USB cable, called VBUS. A device can draw some or all of its power from VBUS. For devices that will be permanently "tethered" to the host, this can eliminate the need for a local power source.

For battery-powered devices – those that must be able to operate when detached from the host – VBUS power is still very valuable, because USB attachment can keep a device active for long periods of time, increasing the power requirements beyond what would be required otherwise. These devices can switch their power to VBUS while attached, to avoid draining the battery.

USB-equipped MSP430 devices have an integrated LDO that reduces 5-V VBUS to a nominal 3.3 V. This rail can be used to source:

  • the USB module
  • the MSP430 DVCC power rail (most MSP430 devices use a 1.8-V to 3.6-V DVCC rail)
  • the rest of the board

The connection between the LDO and the USB module is internal. The rail is also made available on the VUSB pin. There is no internal connection between VUSB and DVCC; they are isolated from each other. This preserves flexibility for the engineer designer to arrange power in a way that is best for a given application.

The maximum current that can be drawn out of the VUSB pin, for use on DVCC and elsewhere on the board, is approximately 12 mA (see the device data sheet for specific parametric values). In some applications, this is sufficient for the entire system and can eliminate the need for any other LDO.

powering_the_entire_syst_slaa457.gifFigure 9. Powering the Entire System From the Internal LDO

Many other power arrangements are possible. For example:

  • VUSB might be used only for USB, using a different source for DVCC or the rest of the system. If more than 12 mA is needed, this is a convenient approach.
  • The internal 3.3-V LDO might be disabled, and 3.3 V can be driven into VUSB from an external source. Choosing an external LDO with ultra-low quiescent current can reduce current drain on VBUS during USB suspend.
  • A switched approach can be employed: source DVCC and the system from a battery when USB is not attached but, upon attachment to a host, switch them to VBUS and VUSB
  • USB battery charging can be employed, using a device such as TI's BQ24030.

VSSU is the ground for the USB module, including the transceiver and LDOs. The capacitors on VUSB and V18 should be kept as close as possible to VSSU, and VSSU should be tied to board ground.

For developers who want to source into VUSB from an external source, the Descriptor Tool includes a checkbox for this. If checked, it causes the USB API to keep the internal 3.3-V LDO disabled. However, you must still attach the VBUS signal from the USB cable to the VBUS pin, in the manner shown. The presence of 5 V on VBUS is the way in which USB devices determine whether a host is available; therefore, software needs this signal.