Mistake on this page?
Report an issue in GitHub or email us

Debugging methods for Arm Mbed OS applications

At the heart of Arm Mbed is the Online Compiler. While that is incredibly convenient for getting a project started or while prototyping, chances are that at some point you'll miss a debugger, or you'll want to develop while not having an active internet connection. Through debugging, you can do things such as set breakpoints, set watchpoints, view registers, view disassembly, browse memory and examine the callstack. These docs will help you debug your applications.

The simplest way to debug your code is to augment your code with printf statements, which you can observe from your PC using a serial terminal.

Debugging from an IDE

Keil uVision natively supports debugging Mbed OS applications. To set up uVision, read Debugging with Keil uVision.

Mbed also supports debugging using any IDE that supports GDB. To set up the debugger, first read Setting up your local debug toolchain. Then read the section for your specific IDE. The same principles apply to any unlisted IDEs that supports GDB:

  1. Producing debug builds with Arm Mbed CLI.
  2. Debugging with Eclipse.
  3. Debugging with Visual Studio Code.
  4. Debugging with other IDEs that support GDB.
Important Information for this Arm website

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies. If you are not happy with the use of these cookies, please review our Cookie Policy to learn how they can be disabled. By disabling cookies, some features of the site will not work.