bound doStepStartGdbServer Failed: Failed to list bundles

wang_jingbo · ‎2026-03-15

reason: Error: Failed to get full list of project bundles to install. Command failed w

Steps I've already tried

Windows11

Verified the project path contains no Chinese characters, spaces, or special symbols.
Cleaned and rebuilt the project (CMake/Make workflow).
Reloaded the VSCode window
Confirmed the executable file was generated successfully, and the program path in launch.json points to the correct file.

Questions

What exactly causes this "Failed to list bundles" error during debugging?
Is there a standard, correct launch.json template for this scenario on Windows?
Do I need to configure additional GDB paths or environment variables?
Are there any other troubleshooting steps I should try?

Thanks a lot for any help or suggestions! :folded_hands:

Cartu38 OpenDev · ‎2026-03-15

@wang_jingbo
Nothing to do should start out of the box just asking for debug session launch.
See possibly antivirus pain https://community.st.com/t5/stm32cubeide-for-visual-studio/unable-to-install-stlink-gdbserver-with-bundles-manager/td-p/885884

dqsh06 · ‎2026-03-16

@wang_jingbo

@Cartu38 OpenDev

Hello, last week, I updated my VScode to version V1.111.0, and today morinong, I came to the office and try to use RUN AND DEBUG to do my job. I got some errors that the st-link gdb cannot work. I think it is maybe my environment issue on my PC, so I uninstalled VScode, deleted all the ./vscode and extensions. and I re-installed the VScode and the stm32cubeide externsion for VScode.

then I used stm32CubeMX to generate a very simple project with CMake, and I import the project to VScode. it can be build successfully, the build log as below

[main] Building folder: D:/work/vscode/test_ymodem2/build/Debug 
[main] The folder containing the CMake cache is missing. The cache will be regenerated.
[main] Configuring project: test_ymodem2 
[driver] NOTE: You are configuring with preset Debug, but there are some overrides being applied from your VS Code settings.
[proc] Executing command: cube-cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_TOOLCHAIN_FILE=D:/work/vscode/test_ymodem2/cmake/gcc-arm-none-eabi.cmake -DCMAKE_COMMAND=cube-cmake -S D:/work/vscode/test_ymodem2 -B D:/work/vscode/test_ymodem2/build/Debug -G Ninja
[cmake] -- The C compiler identification is GNU 12.3.1
[cmake] -- The CXX compiler identification is GNU 12.3.1
[cmake] -- Detecting C compiler ABI info
[cmake] -- Detecting C compiler ABI info - done
[cmake] -- Check for working C compiler: D:/ST/STM32CubeCLT_1.16.0/GNU-tools-for-STM32/bin/arm-none-eabi-gcc.exe - skipped
[cmake] -- Detecting C compile features
[cmake] -- Detecting C compile features - done
[cmake] -- Detecting CXX compiler ABI info
[cmake] -- Detecting CXX compiler ABI info - done
[cmake] -- Check for working CXX compiler: D:/ST/STM32CubeCLT_1.16.0/GNU-tools-for-STM32/bin/arm-none-eabi-g++.exe - skipped
[cmake] -- Detecting CXX compile features
[cmake] -- Detecting CXX compile features - done
[cmake] Build type: Debug
[cmake] -- The ASM compiler identification is GNU
[cmake] -- Found assembler: D:/ST/STM32CubeCLT_1.16.0/GNU-tools-for-STM32/bin/arm-none-eabi-gcc.exe
[cmake] -- Configuring done (2.2s)
[cmake] -- Generating done (0.1s)
[cmake] CMake Warning:
[cmake]   Manually-specified variables were not used by the project:
[cmake] 
[cmake]     CMAKE_COMMAND
[cmake] 
[cmake] 
[cmake] -- Build files have been written to: D:/work/vscode/test_ymodem2/build/Debug
[build] Starting build
[driver] NOTE: You are building with preset Debug, but there are some overrides being applied from your VS Code settings.
[proc] Executing command: cube-cmake --build D:/work/vscode/test_ymodem2/build/Debug --
[build] [1/23] Building ASM object CMakeFiles/test_ymodem2.dir/startup_stm32g474xx.s.obj
[build] [2/23] Building C object CMakeFiles/test_ymodem2.dir/Core/Src/sysmem.c.obj
[build] [3/23] Building C object CMakeFiles/test_ymodem2.dir/Core/Src/syscalls.c.obj
[build] [4/23] Building C object CMakeFiles/test_ymodem2.dir/Core/Src/stm32g4xx_it.c.obj
[build] [5/23] Building C object CMakeFiles/test_ymodem2.dir/Core/Src/main.c.obj
[build] [6/23] Building C object CMakeFiles/test_ymodem2.dir/Core/Src/stm32g4xx_hal_msp.c.obj
[build] [7/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Core/Src/system_stm32g4xx.c.obj
[build] [8/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_pwr_ex.c.obj
[build] [9/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_rcc.c.obj
[build] [10/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_flash.c.obj
[build] [11/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal.c.obj
[build] [12/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_uart_ex.c.obj
[build] [13/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_rcc_ex.c.obj
[build] [14/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_flash_ramfunc.c.obj
[build] [15/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_pwr.c.obj
[build] [16/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_dma_ex.c.obj
[build] [17/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_gpio.c.obj
[build] [18/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_dma.c.obj
[build] [19/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_flash_ex.c.obj
[build] [20/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_cortex.c.obj
[build] [21/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_exti.c.obj
[build] [22/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_uart.c.obj
[build] [23/23] Linking C executable test_ymodem2.elf
[build] Memory region         Used Size  Region Size  %age Used
[build]              RAM:        1728 B       128 KB      1.32%
[build]            FLASH:       11516 B       512 KB      2.20%
[driver] Build completed: 00:00:01.107
[build] Build finished with exit code 0

but when I click Run and Debug, and choose st-link gdb, the result is as below

a small box shows" gdb is not running.

so what is the matter?

Thanks,

dqsh06

Cartu38 OpenDev · ‎2026-03-16

@dqsh06
what the following is reporting from a VS Code integrated terminal ? (https://community.st.com/t5/stm32cubeide-for-visual-studio/unable-to-install-stlink-gdbserver-with-bundles-manager/td-p/885884)

cube stlink-gdbserver --version

what about ? (https://community.st.com/t5/stm32cubeide-for-visual-studio/bundles-manager-takes-very-long-time-to-load/td-p/885601)

cube bundle list-online
cube bundle list

dqsh06 · ‎2026-03-16

@Cartu38 OpenDev

as below:

but, did you check my build log? as the build log,

D:/ST/STM32CubeCLT_1.16.0/GNU-tools-for-STM32/bin/arm-none-eabi-gcc.exe

the build did not use bundle, the build use STM32CubeCLT. I installed STM32CubeCLT 2years ago, now ST changed to bundle, but I did not know how to use bundle instead of STM32CubeCLT. I click build, the build procedure using STM32CubeCLT automatically.

how to slove this?

Thanks.

Cartu38 OpenDev · ‎2026-03-16

@dqsh06
To get bundles acting instead CLT - CLT is coming because CLT installer is hijacking your system, environment adding stuff to PATH variable - you need to get your project set properly in sync. new way of working.

Way to check if done ok is to check if .settings folder is added to your project root. x3 files have to be into.
If not let's invoke setup project feature.

Once done invoking back CMake build should rely on bundles rqther thqn CLT (you can keep CLT install if you wish).

Not having this setup kind is reason why GDB server is not found.
You have to get

dqsh06 · ‎2026-03-16

@Cartu38 OpenDev

@wang_jingbo

hello, I have uninstalled stm32cubeCLT, and made a path to stm32cube\bundles with the PC environment variables, then when I click build, I can get the gcc using bundles as below

[cmake] -- The C compiler identification is GNU 14.3.1
[cmake] -- The CXX compiler identification is GNU 14.3.1
[cmake] -- Detecting C compiler ABI info
[cmake] -- Detecting C compiler ABI info - done
[cmake] -- Check for working C compiler: C:/Users/Lenovo/AppData/Local/stm32cube/bundles/gnu-tools-for-stm32/14.3.1+st.2/bin/arm-none-eabi-gcc.exe - skipped

the problem is every time I openned the vscode i got a popup box as below

it said installing CMake step failed. but actually, I have installed the stm32cube/bundles/cmake/4.2.3+st.1

and the logs as

2026-03-17 09:19:21.525 [Info]  Adding cube-cmake path to environment: c:/Users/Lenovo/.vscode/extensions/stmicroelectronics.stm32cube-ide-build-cmake-1.44.0-win32-x64/resources/cube-cmake/win32/x86_64
2026-03-17 09:19:24.053 [Error]  Failed to list bundles, reason: Error: Failed to get full list of project bundles to install. Command failed with 
2026-03-17 09:19:24.927 [Info]  Activating STM32Cube configurations for the code indexing feature...
2026-03-17 09:19:24.936 [Info]  Configuring code indexing for 'd:/work/vscode/test_ymodem2'
2026-03-17 09:19:25.024 [Warn]  Active project is not STM32Cube ready, not applying STM32Cube configuration

it said "Failed to list bundles", I don't know what is this means.

so what is wrong?

Thanks.

Cartu38 OpenDev · ‎2026-03-17

@dqsh06
Are you able to reach remote bundles server ?

cube bundle list-online

You need to be online to get the stuff works see https://community.st.com/t5/stm32cubeide-for-visual-studio/connectivity-issues-of-stm32cubeide-for-vscode/m-p/862035#M1583

Any trace as part of STM32Cube core output channel ? Any spurious stuff looking at devtools console ?

dqsh06 · ‎2026-03-17

@Cartu38 OpenDev

yes, I can reach remote bundles server. as below, but still indicated "installing CMake" step failed.

the log is

I don't know why it is, maybe this is a bug of stm32cubeide for vscode. it is very diffcult to use this version of stm32cubeide for vscode.

Thanks.

Julien D · ‎2026-03-18

Hi @dqsh06,

In order to investigate your problem more deeply, may I request you to clean up your project by removing the .settings/bundles* files, the .vscode/ folder, and the build/ folders?

Then, please try to perform the Setup Project from the CLI by following these steps in the VSCode integrated terminal:

$ cube bundle init --project
Initialized new project in xxxxx
$ cube bundle install cmake --project
Added cmake@^4.2.3+st.1
$ cube bundle install ninja --project
Added ninja@^1.13.2+st.1
$ cube bundle install gnu-tools-for-stm32 --project
Added gnu-tools-for-stm32@^14.3.1+st.2
$ cube bundle install stlink-gdbserver --project
Added stlink-gdbserver@^7.13.0+st.3

Your error message suggests that the second command is failing. Running it separately might provide a clearer explanation of the cause.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.