Generate VSCode intellisense for Mbed OS
The Visual Studio Code exporter in Mbed OS is buggy. This project generates correct
launch.json files for Mbed OS projects. The tool is non-destructive, and will only overwrite relevant sections of your VSCode configuration.
Note: This tool invokes the
make_gcc_arm exporter through Mbed CLI, which overwrites the
GettingStarted.html files in your project. Remove these files to run the tool.
Enforces method signatures:
Shows correct include paths:
Inline function documentation:
Aware of the current target:
Sets up debugging for both PyOCD and STLink targets:
Install Node.js 10 or higher.
Install this tool:
$ npm install mbed-vscode-generator -g
Run the tool from an Mbed OS project:
$ mbed-vscode-generator -m DISCO_L475VG_IOT01A
You can set the input and output directories through
You'll need to re-run this tool every time a change might occur in your include path list or in your define list. For example:
- When adding a new library.
- When changing values in
- When updating Mbed OS.
Only the parts of your
c_cpp_properties.json file that need to change will be overwritten.
pyOCD is used as default. To use STLink instead:
$ mbed-vscode-generator -m DISCO_L475VG_IOT01A --debugger stlink
Exporting to make_gcc_arm failed
This tool relies on the
make_gcc_arm exporter, which can be broken for Mbed 2 projects. Report a bug in the Mbed OS project. Switching to an Mbed OS 5 project (e.g. mbed-os-example-blinky) typically helps.