Programmers generally run VS Code on their local systems, but in the cloud era, you'll sometimes want to debug applications in the Kubernetes or Red Hat OpenShift environment where you're deploying them. pioenvs/nucleo_f303k8/firmware.Visual Studio Code (VS Code) is the integrated development environment (IDE) used by most. Note: Change the paths in “target”, “gdbpath”, and “autorun” to the correct locations. Create a GDB configuration in launch.json and add the following. Open the Debug panel ( CTRL + SHIFT + D) and select “Add Configuration > GDB” through the top left dropdown arrow. The Nucleo F030R8 was also tested and confirmed working with this setup. Note: The following was set up on Windows 10 for STM32 Nucleo F303K8. PlatformIO - A one-stop shop for setting up common hardware kits.

STM32CubeMX - For setting up projects.

Fortunately, with VS Code’s debugging capability and my sunk-cost pain of figuring this out, getting this workflow going is fairly straightforward! The only thing that was keeping me away was the lack of out-of-the-box debugging compatibility. Enter VS Code and someone wanting to use the latest and greatest in code editors. I was following the steps outlined in Mastering STM32 by Carmine Noviello (which is an excellent resource) until it said to use Eclipse, because life’s too short to use software with unnecessary bloat. As such, I was set on making it work with embedded development since I was getting started with the STM32 line of microcontrollers.

Visual Studio Code’s combination of functionality, customizability, and aesthetics makes it one of my favourite code editors.

Visual studio code debugger step one