![]() The project builds, and debugging starts when the build succeeds. To find the new path, open a terminal, and run where arm-none-eabi-gdb (Windows) or which arm-none-eabi-gdb (macOS and Linux). Note: If you installed the GNU Arm Embedded Toolchain in a nondefault location (for example, through the Arm Mbed CLI installer), you need to update the MIDebuggerPath to the full path of your copy of arm-none-eabi-gdb. 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. 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 Tip: For most targets, you can also export to IAR or ARMCC.Ĭlick Export, and unpack at a convenient location. Under Export toolchain, select Visual Studio Code (GCC ARM). To export your project to Visual Studio Code, you can use either the Online Compiler or Arm 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. Before starting, first configure your local debug toolchain.Īlso install GNU Make or Mbed CLI to build the project. This document explains how to build and debug Arm Mbed OS applications using Visual Studio Code.
0 Comments
Leave a Reply. |