SLAU533D September   2013  – April 2017

 

  1.   MSP430F5529 LaunchPad™ Development Kit (MSP‑EXP430F5529LP)
    1.     Trademarks
    2. 1 Getting Started
      1. 1.1 Key Features
      2. 1.2 Kit Contents
      3. 1.3 Out-of-Box Experience
        1. 1.3.1 Step 1: Install a Software Development Platform
        2. 1.3.2 Step 2: Connect the Hardware
        3. 1.3.3 Step 3: Verify the storage volume has been loaded
        4. 1.3.4 Step 4: Open a text editor, and press the buttons
        5. 1.3.5 Step 5: Customize the strings
    3. 2 Hardware
      1. 2.1 Block Diagram
      2. 2.2 Hardware Features
        1. 2.2.1 MSP430F5529
        2. 2.2.2 eZ-FET lite Onboard Emulator
        3. 2.2.3 Integrated Full-Speed USB Hub
        4. 2.2.4 Power
        5. 2.2.5 Clocking
        6. 2.2.6 Application (or "Backchannel") UART
        7. 2.2.7 Emulator and Target Isolation Jumper Block
        8. 2.2.8 Isolation Jumper Block: 3.3-V and 5-V Jumpers
        9. 2.2.9 Isolation Jumper Block: Emulator Connection and Application UART
      3. 2.3 Measure Current Draw of MSP430 MCU
      4. 2.4 Using an External Power Source
        1. 2.4.1 External 3.3-V Power Source
        2. 2.4.2 External 5-V Power Source Without USB Connection
        3. 2.4.3 External 5-V Power Source With USB Connection
      5. 2.5 Using the eZ-FET lite Emulator With a Different Target
      6. 2.6 USB BSL Button
      7. 2.7 BoosterPack Plug-in Module Pinout
      8. 2.8 Design Files
      9. 2.9 Hardware Change Log
    4. 3 Software Examples
      1. 3.1 MSP430 Software Libraries: driverlib and the USB API
      2. 3.2 Viewing the Code
        1. 3.2.1 CCS
        2. 3.2.2 IAR
      3. 3.3 Example Project Software Organization
      4. 3.4 USB Configuration Files
      5. 3.5 Out-of-Box Experience: emulStorageKeyboard
        1. 3.5.1  Flowchart
        2. 3.5.2  Pre-Initialization
        3. 3.5.3  Initialization
          1. 3.5.3.1 Configuring the Keyboard
          2. 3.5.3.2 Configuring the MSC Interface
        4. 3.5.4  Handling SCSI Commands
        5. 3.5.5  LPM0 Entry
        6. 3.5.6  LPM0 Exit
        7. 3.5.7  Emulated Storage Volume
        8. 3.5.8  Sending Data as a USB Keyboard
        9. 3.5.9  Properly Handling USB Unplug Events
        10. 3.5.10 Non-Maskable Interrupt (NMI) Vector
      6. 3.6 Example: simpleUsbBackchannel
        1. 3.6.1 What It Does
        2. 3.6.2 Installing the CDC Interface
        3. 3.6.3 Operating the Example
        4. 3.6.4 Backchannel UART Library: bcUart.c, bcUart.h
        5. 3.6.5 Code Description: Initialization
          1. 3.6.5.1 Stopping the Watchdog
          2. 3.6.5.2 Configuring VCORE
          3. 3.6.5.3 Configuring Clocks
          4. 3.6.5.4 Configuring Ports
          5. 3.6.5.5 Initializing the Backchannel UART
          6. 3.6.5.6 Configuring USB
        6. 3.6.6 Code Description: Main Loop
        7. 3.6.7 Modifying to Use an HID-Datapipe Interface
      7. 3.7 Starting Device Manager
    5. 4 Additional Resources
      1. 4.1 LaunchPad Development Kit Websites
      2. 4.2 Information on the MSP430F5529
      3. 4.3 Download CCS, IAR, mspgcc, or Energia
      4. 4.4 USB Developers Package
      5. 4.5 MSP430Ware and TI Resource Explorer
      6. 4.6 F5529 Code Examples
      7. 4.7 MSP430 Application Notes
      8. 4.8 TI E2E Community
      9. 4.9 Community at Large
    6. 5 FAQs
    7. 6 Schematics
  2.   Revision History

5 FAQs

Q: I can't get the backchannel UART to connect. What's wrong?

A: Check the following:

  • Do the baudrate in the host's terminal application and the USCI_A1 settings match?
  • Are the appropriate jumpers in place, on the isolation jumper block?
  • Probe on RXD and send data from the host; if you don't see data, it might be a problem on the host side.
  • Probe on TXD while sending data from the MSP430. If you don't see data, it might be a configuration problem on the USCI_A1 module.
  • Consider the use of the hardware flow control lines (especially for higher baud rates)

Q: So the onboard emulator is really open source? And I can build my own onboard emulator?

A: Yes! We encourage you to do so. The design files are on ti.com.

Q: Why are the character strings printed to the screen incorrect when using the keyboard demo?

A: If you are using a different regional keyboard, certain characters may appear differently. This can be fixed by opening the *.txt files and entering new strings.

Q: My ASCII art rocket does not look right?

A: A couple possibilities…

  • If typing the rocket into Notepad++, the image can become skewed due to a setting that automatically tabs into the next line after a carriage return. You can fix this by changing these settings or by using the standard Notepad application or another text editor. (To open Notepad, click the Start button, then click Run…, type "notepad" in the Open text box, and click OK.)
  • If you are using a word processor like Microsoft Word, be sure to use a fixed-width font like Courier New.

Q: I tried building my own project with driverlib and got a warning: "#303-D typedef name has already been declared (with same type)." How do I resolve this?

warning_303_slau533.png

A: This warning can occur with CCS v5.4. The version of driverlib in the F5529 LaunchPad development kit software examples is from MSP430Ware v1.40.01.44, which is targeted at CCS v5.5. CCS v5.5 has a new and improved set of MSP430 header files in it (for example, msp430f5529.h), and the driverlib in these examples is dependent on that new header file. To resolve this problem in the demo, TI put the new and improved header file (from CCS v5.5) into this project, allowing the project to be compatible with v5.4. However, if you are now working with a different project, this new header file may be missing. You can copy the msp430f5529.h file out of the demo project into your project, or you can upgrade to CCS v5.5.

Q: The MSP430 G2 LaunchPad development kit had a socket, allowing me change the target device. Why doesn't the F5529 LaunchPad development kit use one?

A: The F5529 LaunchPad development kit provides more functionality, and this requires it to use a device with more pins. Sockets for devices with this many pins are too expensive for the tool's target price.

Q: I'm trying to power the LaunchPad development kit from a USB power supply (not an actual USB host), and it is not working. Does the LaunchPad development kit not support this?

This problem is fixed in Rev1.5 and later LaunchPad development kits. Unfortunately Rev1.4 does not. USB hubs typically shouldn't enable power to their downstream devices until the hubs themselves enumerate on the host, and that's what the TUSB2046 on the Rev1.4 F5529 LaunchPad development kit does through the TPS2041B power switches. If the hub never enumerates, power is not provided to the target F5529. Because the downstream device is permanently attached in this application, the TPS2041B switches are not required by the USB specification. Rev1.5 and newer F5529 LaunchPad development kits have these switches removed, to avoid this problem.

Again, the benefit of the hub is single-cable development. Other power supplies can still be applied through the power header.

Q: With the female headers on the bottom, the board does not sit flat on the table, and I can't unsolder them. Why did TI do this?

A: For several reasons. A major feedback item on previous LaunchPad development kits was the desire for female headers instead of male ones. But simply using female instead is problematic, because compatibility with existing BoosterPack plug-in modules would be lost, and some people prefer male headers. So, adding female headers without removing male ones satisfies both preferences. It also allows more flexibility in stacking BoosterPack plug-in modules and other LaunchPad development kits.

The downside to this approach is perhaps that the board does not sit flat. But while a USB cable is attached (the usual development model), it tends to not sit flat anyway.

For those wishing the board to sit flat, holes are drilled in the corners so that standoffs can be fastened. Rubber bumper feet also should work.