bound doStepStartGdbServer Failed: Failed to list bundles

[wang_jingbo]

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

 

Steps I've already tried

Windows11

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

 

Questions

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

 

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

[Cartu38 OpenDev]

@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]

@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]

@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]

@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.