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

2.2.2 eZ-FET lite Onboard Emulator

To simplify development and keep the user's costs low, TI's LaunchPad development kit development tools integrate an emulator for programming and debugging. The F5529 LaunchPad development kit has the new eZ-FET lite emulator (see Figure 10).

ez-fet_lite_emulator_slau533.pngFigure 10. eZ-FET lite Emulator

The dotted line along the bottom of the image divides the emulator area from the target area. (On the board, the power and hub area that is shown in Figure 8 is grouped with the emulator.)

The eZ-FET lite is simple and low cost. Like the emulator on the G2 LaunchPad development kit (MSP-EXP430G2), it provides a "backchannel" UART-over-USB connection with the host, which can be very useful during debugging. But unlike the G2 emulator, it:

  • supports almost all MSP430 MCUs
  • has a configurable backchannel UART baudrate
  • is completely open source!

The hardware and firmware designs are both available for you to customize. Further details and source can be found on http://processors.wiki.ti.com/index.php/EZ-FET_lite.

The eZ-FET lite needs a host-side interface. TI provides the "MSP430 DLL", through which PC applications can access the eZ-FET lite. Such applications include IAR or CCS software environments, MSP430Flasher, Elprotronic's FET-Pro430, mspgcc, and Energia. These solutions generally bundle the DLL.

On Windows, the MSP430 DLL is a DLL file, while on Linux it is a *.so file. Like the rest of the eZ-FET lite solution, the DLL is open source.

Mac OS X has a limitation that prevents it from enumerating composite USB devices that include a CDC interface. For this reason, the eZ-FET lite currently does not work with the default OS X.

The eZ-FET lite works with almost all MSP430 target devices. If you want to work with a different target than the F5529 device on the F5529 LaunchPad development kit, you can disconnect the F5529 using the isolation jumper block and wire your hardware to the emulator through this block.

Features of the eZ-FET lite:

  • USB debugging and programming interface
  • No need to install a driver on the host Windows or Linux PC – it loads silently
  • Application ("backchannel UART") virtual COM port connection with the host, over USB, up to 1 Mbaud
  • LEDs for visual feedback
  • Field-updatable firmware
  • Supports almost all MSP430 MCUs

Hardware and software requirements

  • PC with Windows or Linux
  • MSP430.DLL 3.3.0.6 or higher

The eZ-FET lite LEDs provide feedback to the user about the emulator status (see Table 2). This behavior is similar to that of the MSP-FET430UIF emulator.

Table 2. eZ-FET lite LED Feedback Behavior

Green LED (Power) Red LED (Mode) Description
OFF OFF eZ-FET lite is not connected to the PC. eZ-FET lite is not ready (for example, after an update). Disconnect the LaunchPad development kit from the PC and reconnect it.
ON OFF eZ-FET lite is connected and ready, but the. eZ-FET lite interface has not been opened by IDE.
ON ON eZ-FET lite interface is used by IDE, but no data transfer is taking place.
ON Blinking eZ-FET lite is in action: data transfer between eZ-FET lite and IDE is taking place.
OFF ON A severe ERROR has occurred; disconnect and reconnect the eZ-FET lite. If this does not resolve the error, send for repair.
Alternating green and red blinking A critical update is running on the eZ-FET lite. Do not interfere with it during this time. Wait until it is finished.