Neura Market
mspdebug logo

mspdebug

Free

Debugging tool for MSP430 MCUs

FreeFree tier
Type
Open Source
Visit Website GitHub (40 stars)

About mspdebug

MSPDebug is a free, open-source debugger for MSP430 microcontrollers. It supports a wide range of programmers including FET430UIF, eZ430, RF2500, Launchpad, Chronos, GoodFET, Olimex MSP430-JTAG-TINY, and MSP430-JTAG-ISO, as well as the TI flash bootloader. It can function as a GDB remote stub (replacement for msp430-gdbproxy) or as an independent debugger with capabilities for programming, disassembly, and reverse engineering. The tool operates entirely in userspace, requires no kernel modifications, and is cross-platform (Linux, BSD, macOS, Windows). It includes a simulation mode for running MSP430 code without hardware and supports multiple file formats (Intel HEX, ELF32, COFF, TI Text, SREC). Reverse-engineering features include instruction search, call-graph analysis, and symbol table editing.

Key Features

Works with RF2500, eZ430, FET430UIF (V2 and V3), Launchpad, Chronos, GoodFET, Olimex MSP430-JTAG-TINY, and MSP430-JTAG-ISO programmers
Supports TI flash bootloader
Can act as a GDB remote stub (replacement for msp430-gdbproxy) and/or a GDB client
Capable of single-stepping, programming, running to breakpoints, and inspecting memory
Supports Intel HEX, ELF32, BSD symbol table, COFF, TI Text, and SREC file formats
Disassembles code in memory, including translating addresses to symbols
Reverse-engineering features: instruction search, call-graph analysis, and symbol table editing
Simulation mode allows execution of MSP430 code without hardware
Cross-platform: compiles on Linux, *BSD, OS/X, and Windows
Userspace only: no kernel modifications required

Pros & Cons

Pros
  • Free and open-source (GPL-2.0)
  • Userspace only, no kernel driver modifications needed
  • Broad programmer support (FET, eZ430, Launchpad, Olimex, GoodFET, etc.)
  • Can serve as both GDB proxy and standalone debugger
  • Includes simulation mode for hardware-free testing
  • Cross-platform compatibility (Linux, BSD, macOS, Windows)
  • Rich reverse-engineering features beyond basic debugging
Cons
  • Limited to MSP430 MCUs only, not a general-purpose debugger
  • Requires compilation from source (no pre-built binaries provided)
  • Depends on libusb and readline libraries, which may need manual installation on some systems

Best For

Debugging MSP430 microcontroller firmwareProgramming MSP430 devices with various hardware programmersDisassembling and analyzing MSP430 codeReverse-engineering MSP430 firmware (instruction search, call-graph analysis, symbol table editing)Simulating MSP430 code execution without physical hardwareUsing as a GDB proxy for integration with other debugging tools

FAQ

What programmers does MSPDebug support?
It supports RF2500, eZ430, FET430UIF (V2 and V3), Launchpad, Chronos, GoodFET, Olimex MSP430-JTAG-TINY and MSP430-JTAG-ISO programmers, as well as the TI flash bootloader.
Can MSPDebug be used with GDB?
Yes, it can act as a GDB remote stub (replacing msp430-gdbproxy) and also as a GDB client.
Does MSPDebug support simulation without hardware?
Yes, it has a simulation mode that allows execution of MSP430 code without any hardware.
Which operating systems are supported?
MSPDebug is cross-platform: it compiles on Linux, *BSD, OS/X, and Windows.
How is MSPDebug installed?
It is compiled from source. Dependencies include libusb and optionally readline. After unpacking, run 'make' then 'make install' as root.