Visual Studio Code (with Embedded Extensions)

Overview

Cross-platform editor that has become the de-facto embedded IDE through extensions: Cortex-Debug for ARM debugging, the official Embedded Tools and Serial Monitor extensions, vendor-specific extensions from Espressif, NXP, Nordic, ST, and the Microsoft Embedded Tools pack. Replaces vendor-locked IDEs (Atmel Studio, Code Composer Studio, MPLAB X) with a single consistent environment across MCU families.

Benefits

• Single editor across every MCU family on the team's portfolio
• Mature debugging via Cortex-Debug, probe-rs, and vendor-specific extensions
• First-class integration with CMake, west, Conan, and Docker-based build environments
• Best-in-class AI/agent support (Copilot, Claude Code, Cursor fork) compared to legacy vendor IDEs

Limitations & Risks

• Some vendor-specific tooling (configuration generators, peripheral register views) lags behind dedicated IDEs and ships in extensions of varying quality
• Real-time/live debug features still trail Lauterbach and SEGGER Embedded Studio for hardcore work
• Telemetry / Microsoft-account dependence is a non-starter for some regulated environments — use VSCodium or fork as needed

Recommended Actions

Standardize on VS Code as the team's primary editor; pair with Cortex-Debug or probe-rs for debugging, vendor extensions for code generation, and Docker-based build images for reproducibility. Move new projects off Atmel Studio, Code Composer Studio, and MPLAB X — the vendor extensions for VS Code now cover the same ground with fewer ecosystem lock-ins.

Additional Notes

Replaces three legacy vendor IDEs that were previously listed separately (Atmel Studio, Code Composer Studio, MPLAB X). For regulated industries that prohibit Microsoft account usage, VSCodium is the open-build equivalent.

References & Links

• https://code.visualstudio.com/
• https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug
• https://github.com/microsoft/vscode-embedded-tools