Texas Instruments Texas Instruments

MSP430 DriverLib

Release Notes 

Document Revision: 022720.1837


This is the MSP430 Peripheral Driver Library. This peripheral driver library's intent is to allow application development at an API level instead at the device register level. Allowing developers to concentrate on their applications instead of the nuances of the particular MSP430 device they are using.

This document is divided into the following sections:


What's New

Revision History

Installation and Usage

DriverLib is one of many libraries included into MSP430Ware.

  1. It is recommended to install MSP430Ware into your CCS to prepare for DriverLib usage.
  2. If you wish to update only DriverLib in an existing MSP430Ware install, unzip msp430_driverlib_x_xx_xx_xx.zip into your MSP430Ware installation.
  3. Although not as recommended, you may also install DriverLib separately and into CCS apart from MSP430Ware.

The installation contains the driver library core APIs as well as peripheral examples and API documentation.


After installing MSP430Ware or Driver Library restart Code Composer Studio. When opening CCS you will be greeted with a window like that shown below:
Accept the new product and approve the content. You will now be able to use the RTSC features of driver library.
For more information about these features visit the Driver Library User's Guide.


If you are not able to create an empty DriverLib project or add DriverLib to an existing project because the options do not exist via following a family's DriverLib User's Guide, verify that you have properly installed DriverLib and/or MSP430Ware into your CCS workspace.
To verify if you have properly installed the DriverLib and/or MSP430Ware product, go to Windows (at the top of CCS) -> Preferences -> Code Composer Studio -> Products.

Make sure you have an entry for MSP430 DriverLib in the "Installed Products" list. If you do not see it, then you may need to add the path to it in "Product discovery path" and then press the "Rediscover..." button to have CCS search in the newly added path. CCS will then provide a list of all discovered products (as seen in the "NEW INSTALL OR UPDATE" section above). Select the option for driverlib, press install, and agree to restart CCS. After that, it should be installed.

The MSP430 peripheral driver library contains the following components:

doc MSP430 Peripheral Driver Library documentation
driverlib MSP430 Peripheral Driver Library source code
examples MSP430 Peripheral Driver Library examples

Device Support

The following families of devices are support in this release of MSP430 Driver Library:

Peripheral Support

This is the release of MSP430 Peripheral Driver Library.  The following peripherals are supported in this release:


MSP4305xx_6xx devices MSP430FR57xx devices MSP430FR5xx_6xx devices MSP430FR2xx_4xx devices MSP430i2xx devices

Validation Information

This release is a GA version.

Upgrade and Compatibility Information

Steps to upgrade from Driverlib 1.90 to Driverlib 1.95
1. All projects that use driverlib should work as is when you replace the existing driverlib by Driverlib 1.95.
2. Some of the source and header file names have changed to be in line with the new Texas Instruments coding guidelines. However as long as the user     includes "driverlib.h" instead of individual peripheral header files, the user will have no issues upgrading.

Steps to upgrade from Driverlib 1.60 to Driverlib 1.70
  1. Add compiler define DRIVERLIB_LEGACY_MODE
  2. Include "driverlib.h" instead of individual module header files ( eg. fram.h, wdt_a.h etc.)
Removal of baseaddress removes support of Grace Users that rely on Grace should not update Driver Library at this time until a new Grace is released.

As part of our continued process of optimizing MSP430 driverlib and standardizing the MSP430 driverlib APIs we have segregated the MSP430 modules into

This would reflect as the baseaddress of module being absent/present in the module driverlib API based on if the module is a core/peripheral. This change increases performance in some APIs and allows greater software standardization across MCU platforms in TI’s portfolio. We believe this also increases readability by removing an extra parameter in APIs for peripherals that will only have one instance.

Based on this rule, we had to change some of the existing driverlib APIs to remove the baseaddress parameter. This would break compatibility for existing customers.

To provide backward compatibility 

  1. We will provide a compiler define DRIVERLIB_LEGACY_MODE. If this is predefined in the compiler settings, the older APIs will work (Pre 1.70 Release).
  2. The user must also include the "driverlib.h" header file released in 1.60 driverlib onwards instead of the individual header files.

If DRIVERLIB_LEGACY_MODE compiler define is absent, then the newer APIs take effect (Post 1.70 Release).

Without making the above change, most existing projects that rely on driverlib 1.60 or below will fail to compile by default. Adding the compiler define DRIVERLIB_LEGACY_MODE and including “driverlib.h” instead of individual header files is necessary to get the projects to compile in legacy mode(using the older APIs).

We advise newer projects that are in the process of development to adopt the newer APIs. The older APIs are still available in the deprecated section. Here is the affected peripheral list.





The examples may be built with either IAR, CCS or GCC. To build the examples navigate to examples/<family>/<peripheral>/<ide> and double click the .eww project files for IAR, import the .projectSpec file for CCS or run a "make -f " for the GCC makefile.

Current supported families are found in the Device Support section of the release notes.

Current supported peripherals are found in the Peripheral Support section of the release notes.

Known Issues


This is build of MSP430 driver library.

Technical Support and Product Updates

Additional Resources

For more information, visit www.ti.com.