MRI is a debug monitor which allows the GNU debugger, GDB, to be used with the mbed 1768 device. This makes it possible to debug applications running on the mbed device using a full featured source level debugger. MRI is able to communicate with GDB through the convenient USB based serial port on the mbed or any of the device's other 3 available serial ports (incase the application requires exclusive access to the USB based serial port.)
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.
- 6 hardware breakpoints
- 4 data watchpoints
- single stepping
- runs over any of the serial ports on the mbed 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
- minimal 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)
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.
Limitations: Lists the known limitations of the MRI debug monitor. Especially noted are those limitations that it has when compared to a typical JTAG based debugger.
Issues: Contains information about the currently known issues with the MRI debugging solution.
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