This post was originally published on Mbed Developer Blog.

Update (June 2019): I’ve given up on using the Mbed exporters. They’re breaking very often, and are inflexible. Instead I’ve put together mbed-vscode-generator which should work for both pyOCD and STLink targets.

Visual Studio Code, Microsoft’s new cross-platform IDE, is gaining a lot of momentum. In the 2017 Stack Overflow Developer Survey it ranked in the top five for most popular developer environment for both web and desktop developers. Unfortunately, the survey did not have numbers on embedded developers - but its popularity is definitely on the rise in the Mbed offices, thanks to the excellent C/C++ support and the built-in support for visual debugging through GDB.

It’s now easier to develop Mbed OS applications in Visual Studio Code: Mbed OS 5.6 includes an exporter for both our online compiler and Mbed CLI. The exporter is available for every target that supports building through a Makefile, and can build using GCC ARM, ARMCC and IAR. Not only does the exporter set the IDE up so you have context-aware language analysis, it also configures the debugger, so you can debug most targets by simply pressing F5.

Debugging an Mbed OS 5 application in Visual Studio Code

Debugging an Mbed OS 5 application in Visual Studio Code

For information on how to export your applications, and the prerequisites for debugging, see the docs: Debugging Mbed OS applications with Visual Studio Code.

Happy debugging!


Jan Jongboom is Developer Evangelist IoT at Arm