STM32CubeIDE for Visual Studio Code Documentation

Table Of Contents

- STM32CubeIDE for Visual Studio Code
- Introduction
  - Overview
  - System requirements
  - Release note
- Basic Concepts
  - User interface
  - Command-line tools
  - Visual Studio Code extension packs
  - Bundles
  - CMake
  - Toolchains
  - STMicroelectronics Arm Clang Toolchain for STM32
- Getting Started
  - Installation
  - First project creation
- Workspace and extension workflow
  - Workspace overview
  - Extension commands
  - Project files
  - Multi-project workspaces
- Tutorials
  - Migrating from STM32CubeIDE for Visual Studio Code extension 2.x to 3.x
  - Dual-core STM32 projects
  - Power management
  - RTOS-based STM32 projects
  - Firmware security and integrity
- Development
  - Projects
  - Editing
  - Build
  - Debug
  - API manual
  - Integration with external tools
  - Testing and validation
- Troubleshooting
  - Frequently asked questions
  - Known issues
  - Support

### On this page

- Potential duplications
- Potential conflicting extensions

# Migrating from STM32CubeIDE for Visual Studio Code extension 2.x to 3.x

ST recommends uninstalling any previous 2.x versions of STM32 for Visual Studio Code extension before installing a newer release version. This step ensures a clean installation and prevents duplication of functionality between the old and new versions.

The 3.x and newer versions eliminates the need for the CLT, streamlining the setup process.

Internal testing indicates that migrating from version 2.x to 3.x and newer versions does not lead to any known issues. However, performing a clean installation is recommended as an additional precaution to avoid potential conflicts.

## Potential duplications

- Cortex-debug from marus25

- Debug-tracker-vscode from mcu-debug

- Memory view from mcu-debug

- Peripheral viewer from mcu-debug

- RTOS view from mcu-debug

## Potential conflicting extensions

- C/C++ extension pack from Microsoft

- C/C++ from Microsoft