I have to say that as I was completely unfamiliar with JAVA and Maven and when I reached that point, Maven wasn’t even installed on my system, but only the VS Code Plugin for Maven. I’ve have already been at a point where Fiji was opened by VS Code. vscode/tasks.json and create a 2.0.I tried to build my own Fiji-Plugin according to the official tutorial. Visual Studio Code uses make to build your application by default. 'miDebuggerPath': 'arm-none-eabi-gdb.exe', Set it to something like build_debug.Ĭhange $

Set preLaunchTask to the task name that needs to run before starting the debug session.

Set serverStarted to target halted due to debug-request, current mode: Thread.

For more info, read our toolchain document.

Change debugServerArgs to include your OpenOCD arguments.

Change debugServerPath to point to the location of openocd.

If you're using OpenOCD as your debug server: If you're using pyOCD as your debug server, verify that debugServerPath is set to the location of pyocd-gdbserver. Remove the entire linux, osx and windows blocks from the file as these are not supported in the latest VSCode configuration.Īdd the MIMode, miDebuggerPath, and debugServerPath at the end of configurations block. To configure the debugger for your project: $ mbed export -i vscode_gcc_arm -m K64F -profile debug In your project folder, run: # alternatively, use -i vscode_armc5 for ARMCC, or -i vscode_iar for IAR To export your project to Visual Studio Code, you can use Mbed CLI. Installing the C/C++ plugin in Visual Studio Code

Search for the C/C++ plugin (by Microsoft) and click Install.

Open Visual Studio Code, and click on the Extensions button. You need to install Visual Studio Code with the C/C++ extensions to begin. You also need to install GNU Make or Mbed CLI to build the project. Before starting, first configure your local debug toolchain. This document explains how to build and debug Arm Mbed OS applications using Visual Studio Code.

Compile in visual studio code