1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in

MSPGCC Wiki

From mspgcc

Jump to: navigation, search


NOTICE

Texas Instruments and Red Hat have teamed to develop a new back-end for GCC. This is expected to replace mspgcc, which cannot be upstreamed due to inability to obtain copyright releases from all the developers who have contributed to it over its many year history. Limited support for mspgcc will continue until nobody can be found to take on this responsibility.

Overview

The mspgcc tool chain provides binutils, gcc, gdb and a lot of other tools for the MSP430 processor. Note that the tool chain itself consists of command line tools. Users who prefer an IDE need to install one separately.

Edit permissions for this wiki can be acquired by filing a support request. You must have a SourceForge account, and use it to create an account on the wiki (see link in upper right corner). Provide your sourceforge account name in the request.

This wiki describes the current maintained version of gcc, which evolved under the name Uniarch. The original mspgcc3-based version of this wiki and original project home page are still available for reference. Interested parties can read the history of mspgcc.


Supported Processors

All released MSP430 microcontrollers are supported. The msp430mcu package must be installed to provide header and linker support.

Support for 20-bit addresses is available in the current development series. For documentation on using 20-bit support, see Gcc47:20-Bit_Design and the mailing list archive.

Installation

mspgcc is formed from patches to upstream tools like binutils, gcc, and gdb, combined with a minimal libc and information describing the characteristics of the current set of MSP430 microcontrollers. Most users should obtain a working installation from a downstream packager. If you wish to build from source, it is recommended that you download the latest mspgcc release, which includes the patches and information on corresponding versions of msp430-libc and msp430mcu.


Downstream packagers may want to track the patches branch of the mspgcc git repository; this branch will include patches to long-term support versions of mspgcc. Developers will need to clone and use the git repositories.

Debugger

There are several debugging tools for JTAG debugging with mspgcc:

  • mspdebug is a great tool for debugging with the MSP430 toolchain. It can be used as a standalone tool or can function as a gdb remote allowing debugging using the msp430-gdb source debugger. It works on Linux and Windows, but only supports limited hardware breakpoints. Download the Source files if your distro doesn't have a pre-packaged version available.
  • msp430-gdbproxy++ is an open-source debug GDB stub (allows debugging with GDB using the "target remote" command). It works on Windows only, but supports hardware breakpoints, unlimited software breakpoints and data breakpoints. It uses the MSP430.DLL provided by TI.

Examples

Community

mspgcc

Most discussions take part on mspgcc-users mailing list. A searchable archive is also available. Note that you must be subscribed to this list in order to post to it.

All enhancements, bug fixes, and other changes to revision-controlled material related to mspgcc are driven by issues recorded in the mspgcc tracker.

Other Resources

Personal tools