Texas Instruments LaunchPad MSP430FR4133 User manual

1
SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
User's Guide
SLAU595B–October 2014–Revised January 2017
MSP430FR4133 LaunchPad™ Development Kit
(MSP ‑‑ EXP430FR4133)
The MSP-EXP430FR4133 LaunchPad™ Development Kit is an easy-to-use evaluation module (EVM) for
the MSP430FR4133 microcontroller (see Figure 1). It contains everything needed to start developing on
the MSP430™ ultra-low-power (ULP) FRAM-based microcontroller (MCU) platform, including on-board
emulation for programming, debugging, and energy measurements. The board features on-board buttons
and LEDs for quick integration of a simple user interface and a liquid crystal display (LCD) that showcases
the integrated driver with flexible software-configurable pins.
Figure 1. MSP-EXP430FR4133

www.ti.com
2SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback
Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
Contents
1 Getting Started............................................................................................................... 3
2 Hardware...................................................................................................................... 5
3 Software Examples ........................................................................................................ 17
4 Additional Resources ...................................................................................................... 22
5 FAQ .......................................................................................................................... 24
6 Schematics.................................................................................................................. 25
List of Figures
1 MSP-EXP430FR4133....................................................................................................... 1
2 MSP-EXP430FR4133 Overview........................................................................................... 5
3 Block Diagram................................................................................................................ 6
4 MSP430FR4133 Pinout..................................................................................................... 7
5 eZ-FET Emulator ............................................................................................................ 8
6 eZ-FET Isolation Jumper Block Diagram ............................................................................... 10
7 Application Backchannel UART in Device Manager................................................................... 10
8 LCD Segment Layout...................................................................................................... 11
9 MSP-EXP430FR4133 Power Block Diagram........................................................................... 14
10 LaunchPad to BoosterPack Connector Pinout ......................................................................... 16
11 Programming the LaunchPad With Program Batch Files............................................................. 18
12 Directing the Project>Import Function to the Demo Project.......................................................... 19
13 When CCS Has Found the Project ...................................................................................... 20
14 MSP-EXP430FR4133 Software Examples in TI Resource Explorer................................................ 23
15 Schematics (1 of 6) ........................................................................................................ 25
16 Schematics (2 of 6) ........................................................................................................ 26
17 Schematics (3 of 6) ........................................................................................................ 27
18 Schematics (4 of 6) ........................................................................................................ 28
19 Schematics (5 of 6) ........................................................................................................ 29
20 Schematics (6 of 6) ........................................................................................................ 30
List of Tables
1 EnergyTrace Technology................................................................................................... 8
2 Isolation Block Connections................................................................................................ 9
3 LCD FH-1138P Segment Mapping ...................................................................................... 12
4 LCD to MSP430 Connections ............................................................................................ 13
5 Hardware Change Log .................................................................................................... 17
6 Software Examples ........................................................................................................ 17
7 IDE Minimum Requirements for MSP-EXP430FR4133............................................................... 18
8 List of Source Files and Folders ......................................................................................... 21
9 How MSP430 Device Documentation is Organized ................................................................... 22

www.ti.com Getting Started
3
SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
Trademarks
LaunchPad, MSP430, BoosterPack, Code Composer Studio, EnergyTrace, E2E are trademarks of Texas
Instruments.
IAR Embedded Workbench is a registered trademark of IAR Systems.
1 Getting Started
1.1 Introduction
The MSP-EXP430FR4133 LaunchPad™ Development Kit is an easy-to-use Evaluation Module (EVM) for
the MSP430FR4133 microcontroller (see Figure 1). It contains everything needed to start developing on
the MSP430™ ultra-low-power (ULP) FRAM-based microcontroller (MCU) platform, including on-board
emulation for programming, debugging, and energy measurements. The board features on-board buttons
and LEDs for quick integration of a simple user interface and a liquid crystal display (LCD) that showcases
the integrated driver with flexible software-configurable pins. The MSP430FR4133 device features
embedded FRAM (ferroelectric random access memory), a nonvolatile memory known for its ultra-low
power, high endurance, and high-speed write access.
Rapid prototyping is simplified by the 20-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. Design your own BoosterPack or choose among many
already available from TI and third-party developers.
Free software development tools are also available, including TI's Eclipse-based Code Composer
Studio™ (CCSTUDIO) and IAR Embedded Workbench®IAR-KICKSTART. Both of these integrated
development environments (IDEs) support EnergyTrace™ technology when paired with the
MSP430FR4133 LaunchPad. More information about the LaunchPad, the supported BoosterPacks, and
available resources can be found at TI's LaunchPad portal.
1.2 Key Features
• MSP430 ultra-low-power FRAM technology based MSP430FR4133 16-bit MCU
• 20-pin LaunchPad standard that leverages the BoosterPack ecosystem
• eZ-FET, an open-source onboard debugger that features EnergyTrace technology
• On-board segmented LCD
• Two buttons and two LEDs for user interaction
• Backchannel UART through USB to PC
1.3 What's Included
1.3.1 Kit Contents
• 1 x MSP-EXP430FR4133 LaunchPad Development Kit
• 1 x micro-USB cable
• 1 x Quick Start Guide
1.3.2 Software Examples
• Out-of-Box Software
1.4 First Steps: Out-of-Box Experience
An easy way to get familiar with the EVM is by using its preprogrammed out-of-box code. It demonstrates
some key features from a user level.

Getting Started www.ti.com
4SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback
Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
1.4.1 Connecting to the Computer
Connect the LaunchPad using the included USB cable to a computer. A green power LED should
illuminate. For proper operation, drivers are needed. It is recommended to get drivers by installing an IDE
such as TI's CCS or IAR EW430. Drivers are also available at www.ti.com/MSPdrivers.
1.4.2 Running the Out-of-Box Demo
When connected to the computer, the LaunchPad powers up and displays a greeting message on the
LCD. Press and hold the S1 and S2 buttons simultaneously to select a new mode. A more detailed
explanation of each mode can be found in Section 3.4.
1.4.2.1 Stopwatch Mode
This mode provides a simple stopwatch application. It supports split time, where the display freezes while
the stopwatch continues running in the background.
Timer Stopped:
S1: Start time
S2: Reset time
Timer Running:
S1: Stop time
S2: Split time (lap time)
1.4.2.2 Temperature Mode
This mode provides a simple thermometer application. Using the on-chip temperature sensor, the
temperature is displayed on the LCD.
S1: Pause current temperature
S2: Toggle temperature between °F and °C
1.5 Next Steps: Looking Into the Provided Code
After the EVM features have been explored, the fun can begin. It's time to open an integrated
development environment and start editing the code examples. Refer to Section 3.3 for more information
on IDEs and where to download them.
The out-of-box source code and more code examples are provided for download at
http://www.ti.com/tool/msp-exp430fr4133. Code is licensed under BSD, and TI encourages reuse and
modifications to fit specific needs.
Section 3 describes all of the functions in detail and describes the project structure to help familiarize you
with the code.
With the onboard eZ-FET emulator debugging and downloading new code is simple. A USB connection
between the EVM and a PC through the provided USB cable is all that is needed.

{
eZ-FET on-board emulator
Enables debugging/programming as
well as communication back to the
PC. The eZ-FET can also provide
power to the target MCU.
Introducing EnergyTrace Technology
TM
Real-time power consumption readings and
state updates from the MSP430FR4133
MCU, including CPU and peripheral state
are viewable through the EnergyTrace GUI
Jumpers to isolate emulator
from target MCU (J101)
- Back-channel UART to PC
(RTS, CTS, RXD, TXD)
- Spy-Bi -Wire debug (SBWTDIO/SBWTCK)
- Power (5V, 3V3, and GND)
20-pin BoosterPack
plug-in module connector
(J1 and J2) {
Button/Switch
S2
User LEDs
LED1, LED2
Button/Switch
S1
Segmented LCD Display
- 6 alphanumeric characters
- 6 symbols for various applications
- Ultra-low power display
MSP430FR4133 Microcontroller
MSP1
Reset
{
www.ti.com Hardware
5
SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
2 Hardware
Figure 2 shows an overview of the MSP-EXP430FR4133 hardware.
Figure 2. MSP-EXP430FR4133 Overview

Target Device
MSP430FR4133
Crystal
32.768 kHz
Micro-B
USB
3.3-VLDO
ESD
Protection
Debug
MCU
LEDs
Red, Green
Crystal
4 MHz
UART/SBW to Target
User Interface
2 Buttons and 2 LEDs
20-pin LaunchPad
standard headers
Power to Target
Reset
button Segmented LCD
EnergyTrace
Hardware www.ti.com
6SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback
Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
2.1 Block Diagram
Figure 3 shows the block diagram.
Figure 3. Block Diagram
2.2 Hardware Features
2.2.1 MSP430FR4133
The MSP430FR4133 is the next device in TI's new ULP FRAM technology platform. FRAM is a cutting
edge memory technology, combining the best features of flash and RAM into one nonvolatile memory.
Device features include:
• 1.8-V to 3.6-V operation
• Up to 16-MHz system clock and 8-MHz FRAM access
• 16KB of nonvolatile FRAM
• Industry's lowest-power LCD controller
• IR modulation logic
• Two timer blocks and up to three serial interfaces (SPI, UART, or I2C)
• Analog: 10-channel 10-bit differential ADC
• Digital: RTC, CRC

P4.7/R13
P4.6/R23
P4.5/R33
P4.4/LCDCAP1
P4.3/LCDCAP0
P4.2/XOUT
P4.1/XIN
DVSS
DVCC
RST/NMI/SBWTDIO
TEST/SBWTCK
P4.0/TA1.1
P8.3/TA1.2
P8.2/TA1CLK
P8.1/ACLK/A9
P8.0/SMCLK/A8
P1.7/TA0.1/TDO/A7
P1.6/TA0.2/TDI/TCLK/A6
P1.5/TA0CLK/TMS/A5
P1.4/MCLK/TCK/A4/VREF+
P1.3/UCA0STE/A3
P1.2/UCA0CLK/A2
P1.1/ /A1/UCA0RXD/UCA0SOMI Veref+
P1.0/ /A0/Veref–UCA0TXD/UCA0SIMO
P5.7/L39
P5.6/L38
P5.5/L37
P5.4/L36
P5.3/UCB0SOMI/UCB0SCL/L35
P5.2/UCB0SIMO/UCB0SDA/L34
P5.1/UCB0CLK/L33
P5.0/UCB0STE/L32
P2.7/L31
P2.6/L30
P2.5/L29
P2.4/L28
P2.3/L27
P2.2/L26
P2.1/L25
P2.0/L24
P6.7/L23
P6.6/L22
P6.5/L21
P6.4/L20
P6.3/L19
P6.2/L18
P6.1/L17
P6.0/L16
P3.7/L15
P3.6/L14
P3.5/L13
P3.4/L12
P3.3/L11
P3.2/L10
P3.1/L9
P3.0/L8
P7.7/L7
P7.6/L6
P7.5/L5
P7.4/L4
P7.3/L3
P7.2/L2
P7.1/L1
P7.0/L0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
www.ti.com Hardware
7
SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
Figure 4. MSP430FR4133 Pinout

Hardware www.ti.com
8SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback
Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
2.2.2 eZ-FET Onboard Emulator With EnergyTrace™ Technology
To keep development easy and cost effective, TI's LaunchPad Development Kits integrate an onboard
emulator, which eliminates the need for expensive programmers. The MSP-EXP430FR4133 has the eZ-
FET emulator (see Figure 5), which is a simple and low-cost debugger that supports all MSP430 device
derivatives.
Figure 5. eZ-FET Emulator
The MSP-EXP430FR4133 LaunchPad features EnergyTrace technology but does not have support for
EnergyTrace++™ technology. The EnergyTrace functionality varies across the MSP portfolio (see
Table 1).
Table 1. EnergyTrace Technology
Feature EnergyTrace™ Technology EnergyTrace++™ Technology
Current Monitoring ✓ ✓
CPU State ✓
Peripheral and System State ✓
Devices Supported All MSP430 MCUs MSP430FR59xx and
MSP430FR69xx MCUs
Development Tool Required MSP-FET or eZ-FET MSP-FET or eZ-FET
The eZ-FET also provides a "backchannel" UART-over-USB connection with the host, which can be very
useful during debugging and for easy communication with a PC. The provided UART supports hardware
flow control (RTS and CTS), although by default these signals are not connected to the target.
The dotted line through J101 shown in Figure 5 divides the eZ-FET emulator from the target area. The
signals that cross this line can be disconnected by jumpers on J101, the isolation jumper block. More
details on the isolation jumper block are in Section 2.2.3.
The eZ-FET hardware can be found in the schematics in Section 6 and in the accompanying MSP-
EXP430FR4133 Hardware Design Files. The software and more information about the debugger can be
found on the eZ-FET lite wiki.

www.ti.com Hardware
9
SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
2.2.3 Emulator Connection: Isolation Jumper Block
The isolation jumper block at jumper J101 allows the user to connect or disconnect signals that cross from
the eZ-FET domain into the MSP430FR4133 target domain. This includes eZ-FET Spy-Bi-Wire signals,
application UART signals, and 3.3-V and 5-V power (see Table 2 and Figure 6).
Reasons to open these connections:
• To remove any and all influence from the eZ-FET emulator for high accuracy target power
measurements
• To control 3-V and 5-V power flow between the eZ-FET and target domains
• To expose the target MCU pins for other use than onboard debugging and application UART
communication
• To expose the programming and UART interface of the eZ-FET so that it can be used for devices other
than the onboard MCU.
Table 2. Isolation Block Connections
Jumper Description
GND Ground
5V 5-V VBUS from USB
3V3 3.3-V rail, derived from VBUS by an LDO in the eZ-FET domain
RTS >> Backchannel UART: Ready-To-Send, for hardware flow control. The target can use this to indicate whether it
is ready to receive data from the host PC. The arrows indicate the direction of the signal.
CTS << Backchannel UART: Clear-To-Send, for hardware flow control. The host PC (through the emulator) uses this
to indicate whether it is ready to receive data. The arrows indicate the direction of the signal.
RXD << Backchannel UART: The target FR4133 receives data through this signal. The arrows indicate the direction
of the signal.
TXD >> Backchannel UART: The target FR4133 sends data through this signal. The arrows indicate the direction of
the 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.

eZ-FET
Emulator
MCU
Isolation
Jumper Block
Spy-Bi-Wire (SBW) Emulation Application UART
3.3V Power
5V Power
Target MSP430
MCU
eZ-FETMSP430 Target
USB Connector
in out
LDO
BoosterPack Header
BoosterPack Header
USB
EnergyTrace
Hardware www.ti.com
10 SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback
Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
Figure 6. eZ-FET Isolation Jumper Block Diagram
2.2.4 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 useful during development and also provides a communication channel to the
PC host side. This can be used to create graphical user interfaces (GUIs) and other programs on the PC
that communicate with the LaunchPad.
The pathway of the backchannel UART is shown in Figure 6. The backchannel UART is the UART on
eUSCI_A0. Because of USCI limitations, this UART channel is shared with the UART on the 20-pin
BoosterPack connector (eUSCI_A0). This UART channel is also shared with the red LED on P1.0. This is
a lot of sharing, but all 64 pins of the device are used and this was done out of necessity. The P1.0 pin
serves more functions than any other.
On the host side, a virtual COM port for the application backchannel UART is generated when the
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 7).
Figure 7. Application Backchannel UART in Device Manager

www.ti.com Hardware
11
SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
The backchannel UART is the "MSP Application UART1" port. In this case, Figure 7 shows COM13, but
this port can vary 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
communication to it from the host.
On the target MSP430FR4133 side, the backchannel is connected to the eUSCI_A0 module. The eZ-FET
has a configurable baud rate; therefore, it is important that the PC application configures the baud rate to
be the same as what is configured on the eUSCI_A0.
The eZ-FET also supports hardware flow control, if desired. Hardware flow control (CTS and RTS
handshaking) allows the target MSP430FR4133 and the emulator to tell each other to wait before sending
more data. At low baud rates and with simple target applications, flow control may not be necessary.
Applications with higher baud rates and more interrupts to service have a higher likelihood that the will not
be able to read the eUSCI_A0 RXBUF register in time, before the next byte arrives. If this happens, the
eUSCI_A0 UCA0STATW register reports an overrun error.
2.2.5 Special Features
2.2.5.1 Liquid Crystal Display (LCD)
The MSP430FR4133 LaunchPad features an on-board LCD (see Figure 8). This LCD is driven by the
internal LCD driver on the MSP430FR4133 device.
Figure 8. LCD Segment Layout

Hardware www.ti.com
12 SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback
Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
There are many available LCD segments, including six full alpha-numeric numbers and letters in addition
to several symbols at the top for various modes or applications. Table 3 shows the mapping of these
segments.
Table 3. LCD FH-1138P Segment Mapping
Pin COM3 COM2 COM1 COM0
1 A1E A1F A1G A1M
2 A1A A1B A1C A1D
3 A1Q NEG A1N A1DP
4 A1H A1J A1K A1P
5 A2E A2F A2G A2M
6 A2A A2B A2C A2D
7 A2Q A2COL A2N A2DP
8 A2H A2J A2K A2P
9 A3R A3F A3G A3M
10 A3A A3B A3C A3D
11 A3Q ANT A3N A3DP
12 A3H A3J A3K A3P
13 A4R A4F A4G A4M
14 A4A A4B A4C A4D
15 A4Q A4COL A4N A4DP
16 A4H A4J A4K A4P
17 A5E A5F A5G A5M
18 A5A A5B A5C A5D
19 A5Q DEG A5N A5DP
20 A5H A5J A5K A5P
21 COM3 - - -
22 - COM2 - -
23 - - COM1 -
24 - - - COM0
25 - - - -
26 - - - -
27 - - - -
28 - - - -
29 - - - -
30 - - - -
31 - - - -
32 TMR HRT REC !
33 B6 B4 B2 BATT
34 B5 B3 B1 []
35 A6E A6F A6G A6M
36 A6A A6B A6C A6D
37 A6Q TX A6N RX
38 A6H A6J A6K A6P

www.ti.com Hardware
13
SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
The MSP430FR4133 device has flexible LCD pins allowing any pin to be a SEG or a COM. This simplifies
layout for the user. The LCD connections are typically a tradeoff between easy layout and optimal memory
settings for cleaner user software, among other considerations. The flexibility of the MSP430FR4133
allowed an optimal memory setting for easy software, along with a simple layout on the PCB (see
Table 4).
Each LCDMEM register is eight bits, controlling up to eight segments. The FH-1138P is a 4-mux LCD, so
four COM pins are needed from the MSP430FR4133. With four COM pins, each segment pin controls four
bits or segments. This means that each LCDMEM register controls two segment pins, as shown in
Table 4. Note that LCDMEM14 to LCDMEM17 and LCDMEM20 and higher are not used due to layout
considerations.
Each alphanumeric character A1 to A6 is controlled by two adjacent LCDMEM registers for efficiency and
ease of use in software. This allows for a single 16-bit memory access to control the whole character, as
opposed to split memory regions requiring separate memory accesses.
Table 4. LCD to MSP430 Connections
LCDMEM
Port Pin
FR4133 Pin
LCD Pin
COM3 COM2 COM1 COM0
Port Pin
FR4133 Pin
LCD Pin
COM3 COM2 COM1 COM0
LCDM19 P5.7 L39 38 A6H A6J A6K A6P P5.6 L38 37 A6Q TX A6N RX
LCDM18 P5.5 L37 36 A6A A6B A6C A6D P5.4 L36 35 A6E A6F A6G A6M
LCDM17 P5.3 L35 P5.2 L34
LCDM16 P5.1 L33 P5.0 L32
LCDM15 P2.7 L31 P2.6 L30
LCDM14 P2.5 L29 P2.4 L28
LCDM13 P2.3 L27 P2.2 L26 34 B5 B3 B1 []
LCDM12 P2.1 L25 33 B6 B4 B2 BATT P2.0 L24 32 TMR HRT REC !
LCDM11 P6.7 L23 16 A4H A4J A4K A4P P6.6 L22 15 A4Q A4COL A4N A4DP
LCDM10 P6.5 L21 14 A4A A4B A4C A4D P6.4 L20 13 A4R A4F A4G A4M
LCDM9 P6.3 L19 12 A3H A3J A3K A3P P6.2 L18 11 A3Q ANT A3N A3DP
LCDM8 P6.1 L17 10 A3A A3B A3C A3D P6.0 L16 9 A3R A3F A3G A3M
LCDM7 P3.7 L15 8 A2H A2J A2K A2P P3.6 L14 7 A2Q A2COL A2N A2DP
LCDM6 P3.5 L13 6 A2A A2B A2C A2D P3.4 L12 5 A2E A2F A2G A2M
LCDM5 P3.3 L11 4 A1H A1J A1K A1P P3.2 L10 3 A1Q NEG A1N A1DP
LCDM4 P3.1 L9 2 A1A A1B A1C A1D P3.0 L8 1 A1E A1F A1G A1M
LCDM3 P7.7 L7 20 A5H A5J A5K A5P P7.6 L6 19 A5Q DEG A5N A5DP
LCDM2 P7.5 L5 18 A5A A5B A5C A5D P7.4 L4 17 A5E A5F A5G A5M
LCDM1 P7.3 L3 21 COM3 - - - P7.2 L2 22 - COM2 - -
LCDM0 P7.1 L1 23 - - COM1 - P7.0 L0 24 - - - COM0

Debug
Power
Domain
Target and
BoosterPack
Power
Domain
Legend
J101
3V3
eZ-FET
J1 J2
MSP430FR4133
target and
BoosterPack
VCC
GND
GND
J6
Target
MSP430FR4133
Device
LCD
USB (eZ-FET) Power
Configuration
Place
Jumper
BoosterPack and External
Power Configuration
J101
3V3
eZ-FET
J1 J2
MSP430FR4133
target and
BoosterPack
VCC
GND
GND
J6
Target
MSP430FR4133
Device
LCD
No
Jumper
Hardware www.ti.com
14 SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback
Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
2.3 Power
The board was designed to accommodate various powering methods, including through the on-board eZ-
FET and from external or BoosterPack power (see Figure 9).
Figure 9. MSP-EXP430FR4133 Power Block Diagram
2.3.1 eZ-FET USB Power
The most common power-supply scenario is from USB through the eZ-FET debugger. This provides 5-V
power from the USB and also regulates this power rail to 3.3 V for eZ-FET operation and 3.3 V to the
target side of the LaunchPad. Power from the eZ-FET is controlled by jumper J101. For 3.3 V, make sure
that a jumper is connected across the J101 3V3 terminal.
2.3.2 BoosterPack and External Power Supply
Header J6 is present on the board to supply external power directly. It is important to comply with the
device voltage operation specifications when supplying external power. The MSP430FR4133 has an
operating range of 1.8 V to 3.6 V. More information can be found in the MSP430FR4133 data sheet
(SLAS865).

www.ti.com Hardware
15
SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
2.4 Measure MSP430 Current Draw
To measure the current draw of the MSP430FR4133 using a multi-meter, use the 3V3 jumper on the
jumper isolation block. The current measured includes the target device and any current drawn through
the BoosterPack headers.
To measure ultra-low power, follow these steps:
1. Remove the 3V3 jumper in the isolation block, and attach an ammeter across this jumper.
2. Consider the effect that the backchannel UART and any circuitry attached to the MSP430FR4133 may
have on current draw. Consider disconnecting these at the isolation jumper block, or at least consider
their current sinking and sourcing capability in the final measurement.
3. Make sure there are no floating input/output (I/Os). These cause unnecessary extra current draw.
Every I/O should either be driven out or, if it is an input, should be pulled or driven to a high or low
level.
4. Begin target 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.
Alternatively, EnergyTrace technology can be used to measure the same current, and see energy profiles
through integrated GUI in CCS and IAR. EnergyTrace allows you to compare various current profiles and
better optimize your energy performance!
2.5 Clocking
The MSP-EXP430FR4133 provides an external clock in addition to the internal clocks in the device.
• Y1: a 32-kHz crystal
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.
The internal clocks in the device default to the following configuration:
• MCLK: DCO, 2 MHz
• SMCLK: DCO, 2 MHz
• ACLK: REFO, 32.768 kHz
For more information about configuring internal clocks and using the external oscillators, see the
MSP430FR4xx and MSP430FR2xx Family User's Guide (SLAU445).
2.6 Using the eZ-FET Emulator With a Different Target
The eZ-FET emulator on the LaunchPad can interface to most MSP430 derivative devices, not just the on-
board MSP430FR4133 target device.
To do this, disconnect every jumper in the isolation jumper block. This is necessary, because the emulator
cannot connect to more than one target at a time over the Spy-Bi-Wire (SBW) connection.
Next, make sure the target board has proper connections for SBW. Note that to be compatible with SBW,
the capacitor on RST/SBWTDIO cannot be greater than 2.2 nF. The documentation for designing MSP430
JTAG interface circuitry is the MSP430 Hardware Tools User's Guide (SLAU278).
Finally, wire together these signals from the emulator side of the isolation jumper block to the target
hardware:
• 5 V (if 5 V is needed)
• 3.3 V
• GND
• SBWTDIO
• SBWTCK
• TXD (if the UART backchannel is used)
• RXD (if the UART backchannel is used)
• CTS (if hardware flow control is used)
• RTS (if hardware flow control is used)
This wiring can be done either with jumper wires or by designing the board with a connector that plugs
into the isolation jumper block.

The following pins are exposed at the BoosterPack connector.
+3.3V
P8.1
P2.7
P1.1
P8.0
P5.1
P2.5
P8.2
P8.3
P1.0
UART RX
TX
Analog In
Analog In
SPI CLK
I2C* SCL
SDA
A9
A1
UCA0RXD
UCA0SOMI
A0
UCA0TXD
UCA0SIMO
L31
SMCLK A8
L33
UCB0CLK
L29
TA1CLK
TA1.2
BoosterPack
Standard MSP-EXP430FR4133 Pin Map
+3.3V
GPIO (!)
GPIO (!)
(!)
(!)
(!)
(!)
AC LK
GND
P1.7
P1.6
RST
P5.2
P1.3
P1.4
P1.5
P5.3
A7
TA0.1 TDO
L34 UCB0SDA
L35 UCB0SCL
UCB0SOMI
A4
MCLK TCK
A5
TMS TA0CLK
A6
TA0.2 TDI TCLK
A3
UCB0STE
UCB0SIMO SPI MOSI
MISO
SPI CS Wireless
SPI CS Display
SPI CS Other
BoosterPack Standard
MSP-EXP430FR4133 Pin Map
GND
RST
PWM Out GPIO (!)
GPIO (!)
GPIO (!)
GPIO (!)
GPIO (!)
(!)
(!)
(!)
(!)
(!)
UCA0STE
P5.0 L32 GPIO**
Also shown are functions that map with the BoosterPack standard.
* Note that to comply with the I C channels of the BoosterPack standard, a software-emulated I C must be used.
** Some LaunchPads do not 100% comply with the standard, please check your LaunchPad to ensure compatability
(!) Denotes I/O pins that are interrupt-capable.
2 2
Hardware www.ti.com
16 SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback
Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
2.7 BoosterPack Pinout
The LaunchPad adheres to the 20-pin LaunchPad pinout standard. A standard was created to aid
compatibility between LaunchPad and BoosterPack tools across the TI ecosystem.
The 20-pin standard is compatible with the 40-pin standard that is used by other LaunchPads like the
MSP‑EXP430F5529LP. This allows some subset of functionality of 40-pin BoosterPacks to be used with
20-pin LaunchPads.
While most BoosterPacks are compliant with the standard, some are not. The MSP-EXP430FR4133
LaunchPad is compatible with all 20-pin BoosterPacks that are compliant with the standard. If the reseller
or owner of the BoosterPack does not explicitly indicate compatibility with the MSP-EXP430FR4133
LaunchPad, compare the schematic of the candidate BoosterPack with the LaunchPad to ensure
compatibility. Keep in mind that sometimes conflicts can be resolved by changing the MSP430FR4133
device pin function configuration in software. More information about compatibility can also be found at
http://www.ti.com/launchpad.
Figure 10 shows the 20-pin pinout of the MSP430FR4133 LaunchPad.
Note that software's configuration of the pin functions plays a role in compatibility. The LaunchPad side of
the dashed line in Figure 10 shows all of the functions for which the MSP430FR4133 device's pins can be
configured. This can also be seen in the MSP430FR4133 data sheet. The BoosterPack side of the dashed
line shows the standard. The LaunchPad function whose color matches the BoosterPack function shows
the specific software-configurable function by which the MSP430FR4133 LaunchPad adheres to the
standard.
Figure 10. LaunchPad to BoosterPack Connector Pinout

www.ti.com Hardware
17
SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
2.8 Design Files
2.8.1 Hardware
Schematics can be found in Section 6. All design files including schematics, layout, bill of materials
(BOM), Gerber files, and documentation are available in the MSP-EXP430FR4133 Hardware Design Files.
2.8.2 Software
All design files including TI-TXT object-code firmware images, software example projects, and
documentation are available in the MSP-EXP430FR4133 Software Examples.
2.9 Hardware Change Log
Table 5. Hardware Change Log
PCB Revision Description
Rev 1.0 Initial release
Rev 1.1 Added CE marking to silkscreen for compliance. No functional or layout change.
3 Software Examples
The software examples included with the MSP430FR4133 LaunchPad can be found in the MSP-
EXP430FR4133 Software Examples.
Table 6. Software Examples
Demo Name BoosterPack
Required Description Details
OutOfBox_FR4133 None The out-of-box demo pre-programmed on the LaunchPad from
the factory. Demonstrates features of MSP430FR4133 device Section 3.4
3.1 Precompiled Binary
The /Binary/ folder inside the MSP-EXP430FR4133 Software Examples includes precompiled TI-TXT
binary files for each of the projects in Table 6 that are ready to be flashed onto the LaunchPad. A copy of
the MSP430Flasher tool is also shipped to interface with the eZ-FET Emulator.
To quickly program a demo onto the LaunchPad, simply navigate into the corresponding demo project's
directory and double click the "Program <Example>.bat" file.

Software Examples www.ti.com
18 SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback
Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
Figure 11. Programming the LaunchPad With Program Batch Files
If desired, the "Program <Example>.bat" file can be modified to point to your own projects' binary file.
NOTE: After importing and compiling the software source code in an IDE such as CCS or IAR, the
TI-TXT binary files located in the /Binary/ folder are not updated automatically. Copy the
newly compiled binary from your IDE's /Workspace/Project/ directory and replace the
"<Example>.txt" in /Binary/ for the batch file to program your own binary file.
3.2 MSP430Ware Library
The examples are built upon MSP430 libraries shown below that are available from TI. All libraries are
available as part of MSP430Ware. Downloading CCS includes MSP430Ware along with TI Resource
Explorer.
• Driver library (MSP430DRIVERLIB): a foundational MSP430 software library that is useful for
interfacing with all MSP430 core functions and peripherals, especially clocks and power.
• Graphics library (MSP430-GRLIB): a library for interfacing MSP430 devices to dot-matrix LCD displays.
Contains primitives for simple drawing as well as images and more.
• Capacitive Touch Library (CAPSENSELIBRARY): a library for capacitive touch sensing applications.
This library supports the use of buttons, sliders, wheels and more. Highly configurable for each
application.
When you begin your own development, you will need more information about these libraries than can be
included in this user's guide. All of the information that you need is in MSP430Ware or the specific library
documentation linked above.
3.3 Development Environment Requirements
To use any of the software examples with the LaunchPad, you must have an IDE that supports the
MSP430FR4133 device (see Table 7). For more details on where to download the latest IDE, see
Section 4.3.
Table 7. IDE Minimum Requirements for MSP-EXP430FR4133
Code Composer Studio™ IDE IAR Embedded Workbench™ IDE
CCS v6.0 or later IAR EW430 v6.10 or later

www.ti.com Software Examples
19
SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
3.3.1 CCS
CCS v6.0 or later is required. When CCS has been launched, and a workspace directory chosen, use
Project>Import Existing CCS Eclipse Project. Direct it to the desired demo project directory that contains
main.c (see Figure 12). Selecting the \CCS subdirectory also works. The CCS-specific files are located
there.
Figure 12. Directing the Project>Import Function to the Demo Project
When you click OK, CCS should recognize the project and allow you to import it. The indication that CCS
has found the project is that it appears in "Discovered projects" and is checked (see Figure 13).

Software Examples www.ti.com
20 SLAU595B–October 2014–Revised January 2017
Submit Documentation Feedback
Copyright © 2014–2017, Texas Instruments Incorporated
MSP430FR4133 LaunchPad™ Development Kit (MSP ‑ EXP430FR4133)
Figure 13. When CCS Has Found the Project
Sometimes CCS finds the project but does not show a checkmark; this might mean that your workspace
already has a project by that name. You can resolve this by renaming or deleting that project. (Even if you
do not see it in the CCS workspace, be sure to check the workspace directory on the file system.)
3.3.2 IAR
IAR 6.10 or higher is required. To open the demo in IAR, click File>Open>Workspace…, and browse to
the *.eww workspace file inside the \IAR subdirectory of the desired demo. All workspace information is
contained within this file.
The subdirectory also has an *.ewp project file. This file can be opened into an existing workspace by
clicking Project>Add-Existing-Project….
Although the software examples have all of the code required to run them, IAR users may download and
install MSP430Ware, which contains MSP430 libraries and the TI Resource Explorer. These are already
included in a CCS installation (unless the user selected otherwise).
3.4 Out-of-Box Software Example
This section describes the functionality and structure of the out-of-box software that is preloaded on the
EVM.
There are two modes in the out-of-box software, stopwatch mode and temperature sensor mode, which
can be controlled with S1 and S2 push buttons on the LaunchPad. This demo shows how to utilize the
LCD_E module (active in low power mode 3.5), combined with the RTC counter, ADC, and internal
temperature sensor, to implement simple stopwatch and thermometer.