Texas Instruments LaunchPad MSP-EXP430F5529LP User manual

MSP-EXP430F5529LP LaunchPad™
Development Kit
User's Guide
Literature Number: SLAU533B
September 2013–Revised June 2014

Contents
1 Getting Started .................................................................................................................... 5
1.1 Key Features.............................................................................................................. 6
1.2 Kit Contents............................................................................................................... 6
1.3 Out-of-Box Experience .................................................................................................. 6
2 Hardware........................................................................................................................... 11
2.1 Block Diagram........................................................................................................... 12
2.2 Hardware Features..................................................................................................... 13
2.3 Measure MSP430 Current Draw...................................................................................... 20
2.4 Using an External Power Source..................................................................................... 21
2.5 Using the eZ-FET lite Emulator With a Different Target........................................................... 25
2.6 USB BSL Button ........................................................................................................ 25
2.7 BoosterPack Pinout .................................................................................................... 27
2.8 Design Files ............................................................................................................ 29
2.9 Hardware Change Log................................................................................................. 29
3 Software Examples............................................................................................................. 30
3.1 MSP430 Software Libraries: driverlib and the USB API........................................................... 30
3.2 Viewing the Code....................................................................................................... 30
3.3 Example Project Software Organization............................................................................. 32
3.4 USB Configuration Files ............................................................................................... 33
3.5 Out-of-Box Experience: emulStorageKeyboard .................................................................... 34
3.6 Example: simpleUsbBackchannel.................................................................................... 40
3.7 Starting Device Manager .............................................................................................. 48
4 Additional Resources.......................................................................................................... 50
4.1 LaunchPad Websites................................................................................................... 50
4.2 Information on the MSP430F5529.................................................................................... 50
4.3 Download CCS, IAR, mspgcc, or Energia........................................................................... 50
4.4 USB Developers Package............................................................................................. 50
4.5 MSP430Ware and TI Resource Explorer............................................................................ 51
4.6 F5529 Code Examples................................................................................................. 53
4.7 MSP430 Application Notes............................................................................................ 53
4.8 TI E2E Community ..................................................................................................... 53
4.9 Community at Large.................................................................................................... 54
5 FAQs ................................................................................................................................ 54
6 Schematics........................................................................................................................ 56
Revision History.......................................................................................................................... 60
2Table of Contents SLAU533B–September 2013–Revised June 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated

www.ti.com
List of Figures
1 MSP430F5529 LaunchPad................................................................................................. 5
2 Jumper Requirements Necessary for Software Demo.................................................................. 7
3 Storage Volume, Mounted from the MSC Interface..................................................................... 8
4 Files on the Storage Volume............................................................................................... 8
5 Default Text Typed From Button S1....................................................................................... 9
6 ASCII-Art LaunchPad Rocket, Typed from Button S2 .................................................................. 9
7 EVM Features and Controls .............................................................................................. 11
8 Block Diagram .............................................................................................................. 12
9 MSP430F5529 Pinout ..................................................................................................... 13
10 eZ-FET lite Emulator....................................................................................................... 14
11 On-Board USB Bus Path.................................................................................................. 15
12 F5529 LaunchPad USB Interfaces....................................................................................... 16
13 F5529 LaunchPad Power Supply ........................................................................................ 16
14 Backchannel UART Pathway............................................................................................. 18
15 Application Backchannel UART in Device Manager................................................................... 18
16 Isolation Jumper Block..................................................................................................... 19
17 Power Block Diagram for Default Configuration With USB Power Only ............................................ 21
18 Power Block Diagram for External 3.3-V Power Source.............................................................. 22
19 Power Block Diagram for External 5-V Power Source Without USB Connection ................................. 23
20 Power Block Diagram for External 5-V Power Source With USB Connection ..................................... 24
21 USB BSL Button............................................................................................................ 25
22 Identifying the USB BSL's HID Interface in Device Manager......................................................... 26
23 F5529 LaunchPad to BoosterPack Connector Pinout................................................................. 28
24 Browse to Demo Project for Import Function........................................................................... 31
25 When CCS Has Found the Project ...................................................................................... 31
26 F5529 LaunchPad Demo Software Organization ...................................................................... 32
27 MSP430 USB Descriptor Tool............................................................................................ 33
28 Demo Program Flow....................................................................................................... 34
29 Disable the Watchdog in Pre-Initialization .............................................................................. 35
30 Waking From LPM0........................................................................................................ 37
31 Movement of Data in simpleUsbBackchannel: CDC .................................................................. 41
32 simpleUsbBackchannel's USB Virtual COM Port, Needing a Driver ................................................ 42
33 Device Manager After Both Ports are Enumerated.................................................................... 43
34 Movement of Data in simpleUsbBackchannel: HID-Datapipe........................................................ 48
35 Start Device Manager...................................................................................................... 48
36 Device Manager............................................................................................................ 49
37 F5529 LaunchPad With DLP-7970ABP NFC BoosterPack........................................................... 50
38 USB Examples in the USB Developers Package...................................................................... 52
39 TI Resource Explorer: Create a New USB Project Wizard ........................................................... 53
40 Schematics (1 of 4) ........................................................................................................ 56
41 Schematics (2 of 4) ........................................................................................................ 57
42 Schematics (3 of 4) ........................................................................................................ 58
43 Schematics (4 of 4) ........................................................................................................ 59
3
SLAU533B–September 2013–Revised June 2014 List of Figures
Submit Documentation Feedback Copyright © 2013–2014, Texas Instruments Incorporated

www.ti.com
List of Tables
1 Files on the Storage Volume............................................................................................... 8
2 eZ-FET lite LED Feedback Behavior .................................................................................... 15
3 Isolation Block Connections............................................................................................... 19
4 Hardware Change Log..................................................................................................... 29
5 Software Examples ........................................................................................................ 30
6 Demo Project File and Directory Descriptions.......................................................................... 32
7 Backchannel Library: Constants to Configure.......................................................................... 44
8 Backchannel Library: Functions.......................................................................................... 44
9 Clock Settings .............................................................................................................. 45
10 How MSP430 Device Documentation is Organized ................................................................... 50
4List of Tables SLAU533B–September 2013–Revised June 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated

User's Guide
SLAU533B–September 2013–Revised June 2014
MSP-EXP430F5529LP LaunchPad™ Development Kit
User's Guide
1 Getting Started
The MSP430 LaunchPad™ Development Kit now has USB! The MSP-EXP430F5529LP (or the "F5529
LaunchPad") is an inexpensive and simple development kit for the MSP430F5529 USB microcontroller. It
offers an easy way to start developing on the MSP430, with on-board emulation for programming and
debugging as well as buttons and LEDs for a simple user interface.
Figure 1. MSP430F5529 LaunchPad
Rapid prototyping is simplified by the 40-pin BoosterPack™ plug-in module headers, which support a wide
range of available BoosterPacks. You can quickly add features like wireless connectivity, graphical
displays, environmental sensing, and much more. You can either design your own BoosterPack or choose
among many already available from TI and third-party developers.
LaunchPad, BoosterPack, Code Composer Studio are trademarks of Texas Instruments.
IAR Embedded Workbench is a trademark of IAR Systems.
5
SLAU533B–September 2013–Revised June 2014 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide
Submit Documentation Feedback Copyright © 2013–2014, Texas Instruments Incorporated

Getting Started www.ti.com
The MSP430F5529 16-bit MCU has 128KB flash memory, 8KB RAM, 25-MHz CPU speed, integrated
USB, and many peripherals – plenty to get you started in your development.
Custom USB functionality can be quickly added using the free open-source USB tools and examples
available in the MSP430 USB Developers Package. This includes the MSP430 USB Descriptor Tool,
which quickly customizes any combination of USB interfaces and automatically generates your USB
descriptors for those interfaces.
Free software development tools are also available - TI's Eclipse-based Code Composer Studio™ IDE
(CCS) and IAR Embedded Workbench™ IDE (IAR), and the community-driven Energia open-source code
editor. More information about the LaunchPad including documentation and design files can be found on
the tool page at www.ti.com/tool/msp-exp430f5529lp.
1.1 Key Features
• USB-enabled MSP430F5529 16-bit MCU
– Up to 25-MHz System Clock
– 1.8-V to 3.6-V operation
– 128KB of flash, 8KB of RAM
– Five timers
– Up to four serial interfaces (SPI, UART, I2C)
– 12-bit analog-to-digital converter
– Analog comparator
– Integrated USB, with a complete set of USB tools, libraries, examples, and reference guides
• The eZ-FET lite emulator, with the application ("backchannel") UART. (Now open-source!)
• Ability to emulate and develop USB applications with a single USB cable, made possible with an on-
board USB hub
• Power sourced from the USB host. The 5-V bus power is reduced to 3.3 V, using an on-board dc-dc
converter.
• Both male and female 40-pin BoosterPack headers, configured for stacking. 20-pin BoosterPacks can
also be attached.
• Compatible with the 40-pin LaunchPad BoosterPack™ development tool standard.
1.2 Kit Contents
(1) MSP-EXP430F5529LP LaunchPad development tool
(1) USB cable with "micro" connectors
(1) Quick start guide
If you intend to write code for the F5529 LaunchPad, you can complete the kit by downloading the
hardware design files (SLAR090) and software examples (SLAC623) from the MSP-EXP430F5529LP tool
page.
1.3 Out-of-Box Experience
The F5529 LaunchPad comes programmed with an out-of-box demonstration example. Let's get started!
This section only describes how to use the demo. More details about the F5529 LaunchPad are given
later.
The demo works on a Windows PC, Linux PC, or Mac. It requires that (at minimum) the power jumpers
(3.3 V and 5 V) on the isolation jumper block be connected. These supply power to the target F5529
device. As shipped from TI, these jumpers are connected.
6MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide SLAU533B–September 2013–Revised June 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated

www.ti.com Getting Started
Figure 2. Jumper Requirements Necessary for Software Demo
Step 1: Install a Software Development Platform
The development platform can be Code Composer Studio IDE (CCS), IAR Embedded Workbench IDE
(IAR), mspgcc, or Energia open-source platform. See Section 3.2 for help choosing a platform.
The out-of-box demo works without this step, but the host reports that the integrated eZ-FET lite emulator
did not enumerate.
(Be aware that the USB API does not yet fully support mspgcc development, but mspgcc does contain the
eZ-FET drivers.)
Step 2: Connect the Hardware
Connect the LaunchPad to a host PC using the USB cable included with the LaunchPad. The demo
should work on any recent version of these operating systems. If prompted, let the PC automatically install
software. The install is "silent", which means that the PC's operating system already has the drivers it
needs.
When you connect a USB device to your computer, the computer goes through the enumeration process.
During enumeration, the host asks for the device's USB descriptors to learn the device's identity,
capabilities, and more. Using the descriptors, the device presents one or more USB interfaces to the host,
where each interface is associated with either a pre-defined device class, or a custom driver. The major
operating systems already ship with drivers for most common device classes, which is why you do not
need to provide them during installation.
The F5529 LaunchPad software demo presents two USB interfaces to the host:
• A Mass Storage Class (MSC) interface, which results in a storage volume
• A Human Interface Device (HID) interface, which is configured as a keyboard
All major host operating systems already have drivers for these classes.
Note: The eZ-FET emulator, application UART, and USB hub also enumerate when the LaunchPad is
attached. These are part of the LaunchPad emulator, and so they always enumerate on Windows and
Linux PCs, no matter what software is loaded into the MSP430F5529 device. In contrast, the MSC and
HID interfaces described in this section are generated by the software demo application that is loaded
onto the LaunchPad as shipped from TI. See Section 2.2.3 for more information.
Step 3: Verify the storage volume has been loaded
When you attach the LaunchPad to the PC, a storage volume is mounted on the host. This volume can be
seen in "My Computer", with the name "F5529LP":
7
SLAU533B–September 2013–Revised June 2014 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide
Submit Documentation Feedback Copyright © 2013–2014, Texas Instruments Incorporated

Getting Started www.ti.com
Figure 3. Storage Volume, Mounted from the MSC Interface
This storage volume is stored within the MSP430F5529's on-chip flash. It is small compared to most flash
drives, but it is large enough for the demo's needs. The MSP430 software presents it to the host through
the MSC interface.
If you open the volume, you see these files:
Figure 4. Files on the Storage Volume
Table 1 describes the function of these files.
Table 1. Files on the Storage Volume
File Description
Contains the text that will be "typed" by the keyboard interface when button S1 is pressed. By default,
Button1.txt its contents are "Hello World".
Contains the text that will be "typed" by the keyboard interface when button S2 is pressed. By default,
Button2.txt it contains "ASCII art" of the LaunchPad "rocket" logo.
MSP430 USB Opening this file causes your web browser to launch the MSP-EXP430F5529LP LaunchPad web
LaunchPad.url page
README.txt A "readme" file that helps explain how to use these files.
If you place other files inside the volume, they are stored inside MSP430 flash. But keep in mind that the
volume is only approximately 60KB in size. If you later download the software demo (or any software) to
the F5529 target, any data that you have placed in the volume will be lost.
If you change the name of the Button1.txt or Button2.txt file, the pushbutton functionality no longer works.
This is because the MSP430 demo software looks for these files by name.
Step 4: Open a text editor, and press the buttons
In addition to the MSC interface, the other USB interface that is enumerated by the demo is an HID
interface, which is used to emulate a keyboard. When you press the S1 or S2 button, the text stored in the
Button1.txt or Button2.txt file, respectively, is sent to your computer as typed keystrokes.
8MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide SLAU533B–September 2013–Revised June 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated

www.ti.com Getting Started
To see the keyboard in action, open a text editor. If using Windows, the standard Notepad application is a
good choice. (To open Notepad, click the Start button, then click Run…, type "notepad" in the Open text
box, and click OK.)
Make sure the window focus is on the text editor and not on another application running on the PC. Then
press the S1 button on the LaunchPad to send the text in Figure 5 to Notepad.
Figure 5. Default Text Typed From Button S1
Then delete this text, and press the S2 button on the Launchpad to send the text in Figure 6 to Notepad.
Figure 6. ASCII-Art LaunchPad Rocket, Typed from Button S2
9
SLAU533B–September 2013–Revised June 2014 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide
Submit Documentation Feedback Copyright © 2013–2014, Texas Instruments Incorporated

Getting Started www.ti.com
The rocket can take a few seconds to type out. While the MSP430 is typing this out, be sure not to change
the PC's window focus outside of Notepad. If you change the focus, keystrokes will be sent to whatever
application has focus, and strange things might happen on your PC!
Step 5: Customize the strings
Because the strings typed out by the S1 and S2 buttons originate from the Button1.txt and Button2.txt
files, respectively, you can change these strings. Open these files in a text editor, modify their contents,
and save the files. Then press the corresponding button; your new string is typed out.
Note that there is a 2048-character limit on each string, a limit set within the software. The limit is
necessary because the software reads the files' strings into a RAM buffer before typing, and the size of
this RAM buffer is 2048 bytes.
10 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide SLAU533B–September 2013–Revised June 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated

Develop your own USB
applications and emulate,
using a single USB cable!
Integrated USB hub and
USB-based power supply
RESET button, for
the target device
Button that invokes the
USB bootstrap loader,
for firmware updates
Pushbuttons and LEDs,
for user interface
eZ-FET emulator
·Open-source
·Works with almost any
MSP430 target
40-pin BoosterPack header
·Compatible with 20-pin and
40-pin BoosterPacks
·Now allows BoosterPacks
with more functionality
Isolation Jumper Block
·Connect to other targets
·Allow more accurate power
measurement
MSP430F5529 USB Microcontroller
·128KB flash, 8KB RAM
·Full-speed USB
·ADC
·5 timers
·4 serial interfaces (SPI, UART, I C)
2
·Analog comparator
·Much more !
www.ti.com Hardware
2 Hardware
This section describes the F5529 LaunchPad hardware.
Figure 7 shows the LaunchPad, with its important features and configuration controls. These controls are
described in this section.
Figure 7. EVM Features and Controls
11
SLAU533B–September 2013–Revised June 2014 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide
Submit Documentation Feedback Copyright © 2013–2014, Texas Instruments Incorporated

32kHz
4MHz
Target Device
MSP430F5529
40-pin (4x10) Boosterpack Interface
4MHz
ESD
Protection
TUSB2046
Full-Speed
USB Hub
6MHz
USB Connector
eZ-FET lite
Emulator
MCU
TPS62237
5V-3.3V
DC-DC Converter
User LEDs and Switches
ResetUSB BSL
Isolation
Jumper Block
Spy-Bi-Wire (SBW) Emulation Application UART
Application USB
40-pin (4x10) Boosterpack Interface
USB Hub / Power
eZ-FET lite Emulator
3.3V Power 5V VBUS
3.3V
Power Header
Jumper
Power Header
USB
USB Data 5V VBUS
Emulator USB
5V VBUS
Hardware www.ti.com
2.1 Block Diagram
Figure 8 shows a functional block diagram of the board.
Figure 8. Block Diagram
12 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide SLAU533B–September 2013–Revised June 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
61 62 63
64
65
66
67
68
69
70
71 72 73 74 75 76 77 78 79 80
60
59
58
57
56
55
54
53
52
51
50
49
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
P6.4/CB4/A4
P6.5/CB5/A5
P6.6/CB6/A6
P6.7/CB7/A7
P7.0/CB8/A12
P7.1/CB9/A13
P7.2/CB10/A14
P7.3/CB11/A15
P5.0/A8/VREF+/VeREF+
P5.1/A9/VREF−/VeREF−
AVCC1
AVSS1
P5.4/XIN
P5.5/XOUT
P1.0/TA0CLK/ACLK
P1.1/TA0.0
P1.2/TA0.1
P1.3/TA0.2
DVCC2
DVSS2
VCORE
RST/NMI/SBWTDIO PJ.3/TCK
PJ.2/TMS
PJ.1/TDI/TCLK
PJ.0/TDO
TEST/SBWTCK
P5.3/XT2OUT
P5.2/XT2IN
AVSS2
V18
VUSB
VBUS
PU.1/DM
PUR
PU.0/DP
VSSU
P1.6/TA1CLK/CBOUT
P1.5/TA0.4
P1.7/TA1.0
P2.2/TA2CLK/SMCLK
P2.0/TA1.1
P2.3/TA2.0
P2.4/TA2.1
P2.5/TA2.2
P2.6/RTCCLK/DMAE0
P2.7/UCB0STE/UCA0CLK
P3.0/UCB0SIMO/UCB0SDA
P3.1/UCB0SOMI/UCB0SCL
P3.2/UCB0CLK/UCA0STE
P3.3/UCA0TXD/UCA0SIMO
P3.4/UCA0RXD/UCA0SOMI
P7.4/TB0.2
P7.5/TB0.3
DVSS1
DVCC1
P1.4/TA0.3
P2.1/TA1.2
P3.6/TB0.6
P3.7/TB0OUTH/SVMOUT
P4.2/PM_UCB1SOMI/PM_UCB1SCL
P4.1/PM_UCB1SIMO/PM_UCB1SDA
P4.0/PM_UCB1STE/PM_UCA1CLK
P4.5/PM_UCA1RXD/PM_UCA1SOMI
P4.4/PM_UCA1TXD/PM_UCA1SIMO
P4.3/PM_UCB1CLK/PM_UCA1STE
P4.6/PM_NONE
P4.7/PM_NONE
P5.6/TB0.0
P5.7/TB0.1
P7.6/TB0.4
P7.7/TB0CLK/MCLK
P6.3/CB3/A3
P6.2/CB2/A2
P6.1/CB1/A1
P6.0/CB0/A0
P3.5/TB0.5
P8.0
P8.1
P8.2
www.ti.com Hardware
2.2 Hardware Features
2.2.1 MSP430F5529
The MSP430F552x is one of several USB-equipped MSP430 derivative families. It offers:
• 1.8-V to 3.6-V operation
• Up to 25-MHz system clock
• 128KB flash memory, 8KB RAM (in addition to 2KB shared RAM with the USB module)
• Ultralow-power operation
• Full-speed USB with 14 endpoints – enough for almost any USB application
• Five timers, up to four serial interfaces (SPI, UART, or I2C), 12-bit analog-to-digital converter, analog
comparator, hardware multiplier, DMA, and more
Figure 9 shows the pinout of the MSP430F5529 in the PN package (LQFP).
Figure 9. MSP430F5529 Pinout
13
SLAU533B–September 2013–Revised June 2014 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide
Submit Documentation Feedback Copyright © 2013–2014, Texas Instruments Incorporated

Hardware www.ti.com
Other USB-equipped MSP430 families include the smaller F550x family and the larger F563x, F663x,
F565x, and F665x families.
To compare the various MSP430 derivatives, download the MSP430 Product Brochure, which is also
available from http://www.ti.com/msp430. The brochure has a table that lets you see at a glance how the
families compare and their pricing. This document is frequently updated as new MSP430 derivatives
become available.
2.2.2 eZ-FET lite Onboard Emulator
To simplify development and keep the user's costs low, TI's LaunchPad development tools integrate an
emulator for programming and debugging. The F5529 LaunchPad has the new eZ-FET lite emulator (see
Figure 10).
Figure 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 (MSP-EXP430G2), it
provides a "backchannel" UART-over-USB connection with the host, which can be very useful during
debugging. But unlike the G2's emulator, it:
• supports almost all MSP430 derivatives
• 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, you can disconnect the F5529 using the isolation jumper
block and wire your hardware to the emulator through this block.
14 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide SLAU533B–September 2013–Revised June 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated

TUSB2046
Full-Speed USB Hub
USB Connector
Target
F5529
eZ-FET lite
Emulator
www.ti.com Hardware
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-updateable firmware
• Supports almost all MSP430 devices
Hardware and software requirements
• PC with Windows or Linux
• MSP430.DLL 3.3.0.6 or higher
The eZ-FET lite's LEDs provide feedback to the user about the emulator's 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 Red LED Description
(Power) (Mode)
eZ-FET lite is not connected to the PC. eZ-FET lite is not ready (for example, after an
OFF OFF update). Disconnect the LaunchPad from the PC and reconnect it.
eZ-FET lite is connected and ready, but the. eZ-FET lite interface has not been opened by
ON OFF 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.
A severe ERROR has occurred; disconnect and reconnect the eZ-FET lite. If this does not
OFF ON resolve the error, send for repair.
A critical update is running on the eZ-FET lite. Do not interfere with it during this time.
Alternating green and red blinking Wait until it is finished.
2.2.3 Integrated Full-Speed USB Hub
The F5529 LaunchPad requires only one USB connection to the host, thanks to an integrated USB hub
(see Figure 11). The emulator and the target device share one USB cable and can be used
simultaneously. This simplifies the development setup.
Figure 11. On-Board USB Bus Path
15
SLAU533B–September 2013–Revised June 2014 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide
Submit Documentation Feedback Copyright © 2013–2014, Texas Instruments Incorporated

USB Connector
TPS62237
DC-DC Converter
Isolation
Jumper Block
eZ-FET lite
eZ-FET lite 5V
eZ-FET lite 3.3V
5V in
3.3V out
MSP430F5529 Target
5529 Target + BoosterPack 5V
5529 Target + BoosterPack 3.3V
MSP430F5529
Target Device
* 5V and 3V3
Isolation Block
Jumpers Control
Power Connection
Hardware www.ti.com
The eZ-FET lite emulator itself is a composite USB device, which means that it contains two USB
interfaces:
• A CDC interface (virtual COM port) for the emulation function
• A CDC interface (virtual COM port) for the application UART
(For an explanation of USB interfaces, see the discussion in Step 2 of Section 1.3)
These interfaces can be found on the host PC. As an example, Device Manager can be used for this
purpose on a Windows PC. (See Section 3.7 for instructions on starting Device Manager.) Look for the
emulator's interfaces under the "Ports" section (see Figure 12).
Figure 12. F5529 LaunchPad USB Interfaces
If you are using a Mac, see Section 2.2.2 for an explanation why these interfaces do not enumerate.
Although the MSP Debug Interface virtual COM port is accessible to any host application, do not try to
interface with it; it is only intended for use with supported emulation tools, like CCS and IAR.
If you load a USB-equipped software application into the target MSP430F5529 device, then additional
USB interfaces, defined by that software, will be enumerated on the host.
The TUSB2046 is a four-port hub, and two ports are unused. The unused ports are properly terminated
and inaccessible.
2.2.4 Power
Figure 13 shows the block diagram's power segment.
Figure 13. F5529 LaunchPad Power Supply
16 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide SLAU533B–September 2013–Revised June 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated

www.ti.com Hardware
USB hosts supply a 5-V power rail to USB devices, called "VBUS". This is convenient for USB devices; if
they only need to function while attached to a host (for example, mice or keyboards) then they may not
need their own power source. Even if they need to function apart from the USB host and, thus, need their
own power source, being attached to the host places power demands on that device which may not be
present when the device is not attached; the availability of VBUS can help offset these demands.
The F5529 LaunchPad has a high-efficiency dc-dc converter, a TPS62237, that derives a new power rail
of 3.3 V from VBUS. This 3.3-V rail sources the eZ-FET lite, hub, target F5529 device, and the 3.3-V pin
on the BoosterPack header.
VBUS is still made available to the target F5529 device for two reasons. One reason is that the presence
of VBUS is how a USB device determines the presence of a USB host. The other reason is that VBUS
also supplies power to the target F5529's USB module.
Note that USB-equipped MSP430's have an integrated 5-V to 3.3-V LDO. On the F5529 LaunchPad, this
LDO is only used for the MSP430F5529 USB operation. However, the integrated LDO also has an output
pin that can source a modest amount of power to external circuitry. See the device data sheet for more
details. Sometimes, this output pin can eliminate the need for external power management. But because
the current limit may be too low for some applications, the F5529 LaunchPad uses the external dc-dc
converter.
If desired, 3.3 V can be supplied from an external source to the power header pin. But to do this, the 3.3-V
jumper on the isolation jumper block must be disconnected. See Section 2.4 for more information.
2.2.5 Clocking
The F5529 LaunchPad provides two resonators on the target F5529:
• XT1: a 32-kHz crystal
• XT2: a 4-MHz ceramic resonator, within ±2500-ppm precision
The 32-kHz crystal allows for lower LPM3 sleep currents than do the other low-frequency clock sources.
Therefore, the presence of the crystal allows the full range of low-power modes to be used.
USB operation on the MSP430F5529 requires a high-frequency reference clock for the USB PLL. To meet
this need, the F5529 LaunchPad has a 4-MHz ceramic resonator on the XT2 oscillator. This particular
ceramic resonator operates within ±2500 ppm, which is important for USB operation. If the F5529
application needs a high-frequency precision clock for purposes other than USB, then this clock is
available for this as well.
For information on how clocks are configured by the software examples, see Section 3.6.5.3.
2.2.6 Application (or "Backchannel") UART
The backchannel UART allows communication with the USB host that is not part of the target application's
main functionality. This is very useful during development. For example, if, while developing a USB
interface, you want to send debug information to the host without using the USB interfaces under
development to do so.
Figure 14 shows the pathway of the backchannel UART. The backchannel UART (USCI_A1) is
independent of the UART on the 40-pin BoosterPack connector (USCI_A0).
17
SLAU533B–September 2013–Revised June 2014 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide
Submit Documentation Feedback Copyright © 2013–2014, Texas Instruments Incorporated

ESD
Protection
TUSB2046
Full-Speed
USB Hub
6MHz
USB Connector
UART
USB Hub and Power
eZ-FET lite Emulator
USB
USB
F5529 dP[
USCI_A1 Interface
4MHz
eZ-FET lite
Emulator
MCU
Isolation
Jumper Block
Hardware www.ti.com
Figure 14. Backchannel UART Pathway
On the host side, a virtual COM port for the application backchannel UART is generated when the F5529
LaunchPad enumerates on the host. You can use any PC application that interfaces with COM ports,
including terminal applications like Hyperterminal or Docklight, to open this port and communicate with the
target application.
You need to identify the COM port for the backchannel. On Windows PCs, Device Manager can assist
(see Figure 15). (See Section 3.7 for instructions on starting Device Manager.)
Figure 15. Application Backchannel UART in Device Manager
The backchannel UART is the port named "MSP Application UART1". In this example, the figure shows
COM13, but the port number varies from one host PC to the next.
After you identify the correct COM port, configure it in your host application according to its
documentation. You can then open the port and begin talking to it from the host.
On the target F5529 side, the backchannel is connected to the USCI_A1 module.
Unlike the eZ-FET on the G2 LaunchPad, this eZ-FET lite has a configurable baudrate. Therefore, it is
important that the PC application configures the baudrate to be the same as what is configured on the
USCI_A1.
18 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide SLAU533B–September 2013–Revised June 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated

www.ti.com Hardware
Also unlike the eZ-FET on the G2 LaunchPad, this eZ-FET lite supports hardware flow control, if desired.
Hardware flow control (CTS and RTS handshaking) allows the target F5529 and the emulator to tell each
other to wait before sending more data. At slow baud rates and with simple target applications, flow
control may not be necessary. An application with faster baud rates and more interrupts to service has a
higher likelihood that it cannot read the USCI_A1's RXBUF register in time, before the next byte arrives. If
this happens, the USCI_A1's UCA1STAT register will report an overrun error.
To implement the backchannel on the target F5529, a simple library is provided within the
simpleUsbBackchannel example. It supports communication with and without hardware flow control. See
Section 3.6.4 for more information.
2.2.7 Emulator and Target Isolation Jumper Block
A set of ten jumpers is placed between the emulator and the F5529 target device. This is the isolation
jumper block (see Figure 16 and Table 3). Individual functions on the isolation block are described in the
following sections.
Figure 16. Isolation Jumper Block
Table 3. Isolation Block Connections
Jumper (from Description
left to right)
GND Ground
5V 5-V VBUS, sourced from the USB host. The F5529 target needs this if attempting a USB connection with it.
3V3 3.3-V rail, derived from VBUS with a dc-dc converter
Backchannel UART: Ready-To-Send, for hardware flow control. The target can use this to indicate whether it is
RTS >> ready to receive data from the host PC. The arrows indicate the direction of the signal.
Backchannel UART: Clear-To-Send, for hardware flow control. The host PC (through the emulator) uses this to
CTS << indicate whether it is ready to receive data. The arrows indicate the direction of the signal.
Backchannel UART: the target F5529 receives data through this signal. The arrows indicate the direction of the
RXD << signal.
Backchannel UART: the target F5529 sends data through this signal. The arrows indicate the direction of the
TXD >> signal.
SBW RST Spy-Bi-Wire emulation: SBWTDIO data signal. This pin also functions as the RST signal (active low).
SBW TST Spy-Bi-Wire emulation: SBWTCK clock signal. This pin also functions as the TST signal.
N/C Not connected. Reserved.
19
SLAU533B–September 2013–Revised June 2014 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide
Submit Documentation Feedback Copyright © 2013–2014, Texas Instruments Incorporated

Hardware www.ti.com
2.2.8 Isolation Jumper Block: 3.3-V and 5-V Jumpers
The 5-V VBUS and 3.3-V power rails, which are sourced to the target from the emulator, travel through
the isolation jumper block. This routing serves these functions:
• Measurement of the target's power consumption
• Removing the emulator from the circuit when an external (non-USB) power source is used
• Removing the F5529 target from the circuit when a different external target board is attached to the
emulator
Measuring the target's power draw is as simple as removing the 3.3-V jumper and connecting an ammeter
across it. The USB hub, emulator and dc-dc converter currents are then excluded from this measurement.
However, anything that is connected on the F5529 LaunchPad headers or power pins on the target
domain below the dotted silkscreen line are included. If precise current measurement is needed, it is
important to disconnect the backchannel UART and SBW lines in the jumper block as well.
See Section 2.3 for more information about measuring power using these jumpers.
Sometimes you may want to use an external 3.3-V power source connected to the target's power header
pins. In this case, the 3.3-V jumper must be disconnected to avoid back-powering the emulator. See
Section 2.4 for more information on this procedure.
Otherwise, in normal operation, both these jumpers should be attached.
2.2.9 Isolation Jumper Block: Emulator Connection and Application UART
MSP430F5xx devices support both standard four-wire JTAG and the two-wire Spy-Bi-Wire (SBW)
standard. The eZ-FET lite emulator on the F5529 LaunchPad supports SBW only. These two signals
travel through jumpers in the isolation block, and can be disconnected if desired. They are labeled on the
block as "SBW RST" and "SBW TEST".
The backchannel UART consists of four signals: the data signals TXD and RXD, and the hardware flow
control signals RTS and CTS. All four of these signals travel through the jumper block as well and can be
disconnected.
Reasons to open these connections:
• When measuring current consumption, devices attached to I/O pins can consume power, influencing
the measurement. Removing the jumpers prevents this.
• The backchannel UART pins can be configured for other functionality instead of the backchannel
UART. If this is desired, it might be good to remove these jumpers, so that the emulator is not affected
by any activity that your application presents on these signals. If only two general I/Os are needed and
if hardware flow control is not needed, you might choose to remove only the hardware flow control
(RTS and CTS) jumpers and leave the TXD and RXD jumpers in place.
• If you want to use the on-board eZ-FET lite emulator with a different target, you can remove the
jumpers and connect your target hardware to the jumper block.
2.3 Measure MSP430 Current Draw
The following steps assume that the target F5529 is to be powered from the USB host, not from an
external power source.
1. Remove the 3V3 jumper in the isolation jumper block. Attach an ammeter across this jumper.
2. Consider the effect that the backchannel UART and any circuitry attached to the F5529 may have on
current draw. Maybe these should be disconnected, or their current sinking and sourcing capability at
least considered in the final measurement.
3. Make sure there are no floating input I/Os. These cause unnecessary extra current draw. Every I/O
should either be driven out or, if an input, should be pulled or driven to a high or low level.
4. Begin target F5529 execution.
5. Measure the current. (Keep in mind that if the current levels are fluctuating, it may be difficult to get a
stable measurement. It is easier to measure quiescent states.)
20 MSP-EXP430F5529LP LaunchPad™ Development Kit User's Guide SLAU533B–September 2013–Revised June 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated