Skip to content

/mri

MRI - Monitor for Remote Inspection. The gdb compatible debug monitor for Cortex-M devices.
  1. C 86.9%
  2. C++ 10.6%
  3. Assembly 1.7%
  4. Other 0.8%
C C++ Assembly Other
Find file
Download ZIP
Latest commit 4018f35 Apr 9, 2016 @adamgreen Remove extra slash from deploy script
Failed to load latest commit information.
CppUTest @ dbdf4f1 Add blank line at end of code coverage summary Dec 23, 2014
architectures/armv7-m Cleanup recent LPC4330 updates Feb 1, 2015
boards board: clarify the descriptions about STM32F429 Dec 8, 2015
cmsis drop intermediate file Dec 8, 2015
core Provide Posix signal values to MRI Dec 22, 2014
devices Add NOPs around UART usage Mar 15, 2016
include Updating master branch version to 0.10 Apr 9, 2016
memory/native New build system Apr 13, 2014
notes Update supported device list Dec 4, 2015
semihost Initial LPC4330 support Jan 28, 2015
tests Connecting to STM32F429i-Discovery devices successfully! Nov 25, 2015
.gitignore Ignore stray editor files Dec 8, 2015
.gitmodules CppUTest now exists on github Mar 5, 2014
COPYING.LESSER New build system Apr 14, 2014
README.creole Update supported device list Dec 5, 2015
deploy Remove extra slash from deploy script Apr 9, 2016
makefile Fix issue #8 Jan 25, 2016

README.creole

MRI - Monitor for Remote Inspection

MRI is a debug monitor which allows the GNU debugger, GDB, to debug Cortex-M3/M4 processors. This makes it possible to debug applications running on Cortex-M devices using a full featured source level debugger with no extra hardware other than a serial connection.

Please Note: This project just contains the sources to build the MRI debug monitor library but doesn't show how to link it into your program and make use of it. Such an example is provided by the GCC4MBED project.

MRI Features

  • 6+ hardware breakpoints (actual number depends on device)
  • 4+ data watchpoints (actual number depends on device)
  • single stepping
  • runs over any of the UART ports on the device (selected when user compiles their code)
  • baud rate is determined at runtime (through GDB command line)
  • semi-host functionality:
    • stdout/stderr/stdin are redirected to/from the GDB console
    • mbed LocalFileSystem semi-host support (fopen, fwrite, fread, fseek, and fclose)
    • maintains access to mbed device's unique ethernet address
  • works with free GNU Tools for ARM Embedded Processors
  • no program binary size limitations
  • open source (LGPL)

Devices Supported

Device Sample Boards
NXP LPC17xx mbed-1768
LPC1769 LPCXpresso Board
NXP LPC43xx Micromint Bambino 210
STM32F429XX STM32F429 Discovery kit

How to Clone

This project uses submodules (CppUTest for unit testing). Cloning requires a few more steps to get all of the necessary code.

git clone git@github.com:adamgreen/mri.git
cd mri
git submodule init
git submodule update

- or -

git clone --recursive git@github.com:adamgreen/mri.git

More MRI Information

Getting started with MRI in GCC4MBED: Documents how to setup the mbed device and GCC4MBED project to use MRI for debugging binaries. Also provides a walk through of a debugging session with one of the GCC4MBED samples.

Supported Host Platforms: Which platforms has GDB been run on while connected to MRI.

Supported Devices: Which devices can currently be debugged with MRI.

Why use MRI: Documents the advantages of using a debug monitor like MRI and its known limitations.

Porting MRI: Notes on how to port MRI to new devices.

Reporting a Problem: How to extract information from your PC to show what was happening at the time a problem occurs in a MRI debugging session.

Frequently Asked Questions

Something went wrong with that request. Please try again.