A build infrastructure designed to simplify creating new applications, in a POSIX command-line environment supported by GNU Make, focused on the GNU toolchain (both upstream msp430-elf-gcc and legacy mspgcc) but also supporting the TI compiler from Code Composer Studio when used in command-line mode;

Value-added capabilities including a command line interface, unit test framework, and RF Evaluation Module interface

BSP430 is released as open source under the BSD-3-Clause license.

For further details, please see the Background, Philosophy, Coding Style, and Maintenance pages.

The project page is at http://github.com/pabigot/bsp430. Releases can be obtained by cloning the git repository:

git clone git://github.com/pabigot/bsp430.git

or by downloading a tar file of the latest stable source release.

Information on specific releases is available in Release Notes and API Changes.

Please file support requests and bug reports on the issue tracker.

Capabilities Currently Supported

Timers supporting both Timer_A and Timer_B supported in a common interface;

A standard clock interface supporting MCLK, SMCLK, ACLK, and LFXT1 crystal configuration in the clock systems in the 2xx, 4xx, 5xx/6xx, and FR5xx families;

A standard serial interface supporting UART, SPI, and I2C using the USCI variants in the 2xx/4xx, 5xx/6xx, and FR5xx families;

Access to the SYS and PMM modules for 5xx/6xx/FR5xx devices allowing detection of reboot cause and control of ultra-low-power LPMx.5 modes;

Pre-configured support for the RF Evaluation Module headers on many experimenter boards along with hardware presentation definitions supporting specific radios like the CC110x, CC112x, CC2500, CC2520, and CC3000.

Support for M25P-compatible SPI flash memory modules common to wireless sensor nodes;

Utilities for a bi-directional serial console with a command line interface that supports editing input;

Miscellaneous utilities including LEDs; ACLK-driven system timer and Alarm-related Timer Functionality; and demonstration 1-Wire bus

Hardware Platforms Currently Supported

Useful External Libraries

embtextf (Embedded System Text Formatting)

See also: http://pabigot.github.com/embtextf/

BSP430 was initially developed using the MSPGCC toolchain, a port of the GNU compiler collection to the MSP430. The msp430-libc library that is part of this toolchain includes a space-efficient formatting print capability compatible with C's printf(3c) functionality using a callback that allows it to output to an application-provided location (a memory buffer, a serial console, an LCD screen, etc.). Subsequently those capabilities have been extracted, refactored, and extended as the embtextf library, making the same features available to Code Composer Studio and other toolchains that do not have an efficient generic formatted print capability. These functions are used in <bsp430/utility/console.h> by defining BSP430_CONSOLE_USE_EMBTEXTF, which is enabled by the default when EMBTEXTF_ROOT is defined for use by ${BSP430_ROOT}/make/Makefile.common.

CC3000 (SimpleLink™ Wi-Fi Module)

See also: http://pabigot.github.com/cc3000/

This library provides a microcontroller API to the Texas Instruments CC3000, an 802.11 wireless network interface. The content is from TI's host driver, but has been repackaged to make it easier to share among applications and to reduce include file namespace collisions. The library as validated in BSP430 is available in a github repository.

u8glib (Graphics for Embedded Systems)

See also: http://code.google.com/p/u8glib/

This library is a general-purpose graphics library supporting liquid crystal displays (LCDs) commonly used on embedded platforms. It provides a variety of fonts as well as graphical elements. The library as validated in BSP430 is available in a github repository.

FatFs (FAT file system)

See also: http://elm-chan.org/fsw/ff/00index_e.html

This library is a generic FAT file system module for embedded systems. The library as validated in BSP430 is available in a github repository.

Provided Examples

Value-Added Utility Examples

Utilities: Unit Test demonstrates the primitive unit test capability supported by BSP430.

Utilities: Command Line Interface demonstrates the command line interface structure based on the console capability .

Peripherals: Alarms provides an interactive program for using one-shot and repeating alarms with the Alarm-related Timer Functionality.

RF Evaluation Module and ChipCon Radios demonstrates the abstraction of the RF Evaluation Module available on many MSP430 experimenter boards by displaying information about a connected ChipCon CC1101, CC2500, or compatible radio that is accessed with the SPI configuration and pins described in <bsp430/rf/cc110x.h>. Similar examples are presented for the <bsp430/rf/cc2520.h> and <bsp430/rf/cc1125.h> abstractions.

M25PE20 SPI flash memory on TrxEB or SuRF demonstrates use of a serial flash device through the <bsp430/utility/m25p.h> interface.

U8GLIB LCD Text and Graphics demonstrates use of the onboard LCD on several TI experimenter boards through the <bsp430/utility/u8glib.h> interface.

FatFs on an EXP430F5529 demonstrates use of FatFs with the BSP430 SPI serial abstraction

CC3000 SimpleLink Exploration is a fairly complex example providing interactive exploration of the Texas Instruments CC3000 SimpleLink(tm) Wi-Fi evaluation module. It demonstrates advanced use of the BSP430 command line interface as well as a SPI interface to the on most TI experimenter boards through the RFEM or CC3000BOOST capabilities of BSP430.

Sensors

Sensors: DS18B20 demonstrates temperature measurement with the DS18B20 (or similar) 1-wire temperature sensor
Sensors: TMP102 demonstrates the I2C interface with a TI TMP102 temperature sensor
Sensors: HH10D demonstrates measuring the frequency of an input signal using the Hope RF Humidity Sensor
Sensors: SkyTraq Venus 638FLPx as Time Source demonstrates the BSP430 GPS interface and synchronizing the uptime clock with a 1PPS GPS time source

Bootstrap Support Programs

The following examples lead you through the basic capabilities of BSP430, following the same path that you would use if you were adding support for a new platform.

Bootstrapping a New Platform: The Null Program confirms that your environment is prepared to build an application for a particular platform
Bootstrapping a New Platform: Blink confirms that your platform can blink LEDs
Bootstrapping a New Platform: Clock Signals brings out clock signals to test points
Bootstrapping a New Platform: Console Output prints output to and captures input from the platform serial connection
Bootstrapping a New Platform: Button validates the secondary input path using a button on the board
Bootstrapping a New Platform: Basic LPM is used to configure the board into low power mode, verifying that the numbers in the data sheet are achievable
Bootstrapping a New Platform: Application LPM is used to interactively evaluate different low power modes with and without the peripherals being disabled

Table of Contents