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:

[dqsh06]

Hi @Julien D ,

I have done the procedures as you instructed as below

the results said "No bundles are detected as required to install", just added all the tools.

then I clicked [Run and Debug], below is the log 

[bookmarks] Loaded 0 bookmarks
[proc] Executing command: C:\Users\Lenovo\AppData\Local\stm32cube\bundles\cmake\4.2.3+st.1\bin\cmake.EXE --version
[proc] Executing command: C:\Users\Lenovo\AppData\Local\stm32cube\bundles\cmake\4.2.3+st.1\bin\cmake.EXE -E capabilities
[presetController] Reading and validating the presets file "D:\work\vscode\test_ymodem2\CMakePresets.json"
[presetController] Successfully validated D:\work\vscode\test_ymodem2\CMakePresets.json against presets schema
[presetController] Expanding presets file D:\work\vscode\test_ymodem2\CMakePresets.json
[presetController] Successfully expanded presets file D:\work\vscode\test_ymodem2\CMakePresets.json
[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: C:\Users\Lenovo\AppData\Local\stm32cube\bundles\cmake\4.2.3+st.1\bin\cmake.EXE -DCMAKE_BUILD_TYPE=Debug -DCMAKE_TOOLCHAIN_FILE=D:/work/vscode/test_ymodem2/cmake/gcc-arm-none-eabi.cmake -S D:/work/vscode/test_ymodem2 -B D:/work/vscode/test_ymodem2/build/Debug -G Ninja
[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
[cmake] -- Detecting C compile features
[cmake] -- Detecting C compile features - done
[cmake] -- Detecting CXX compiler ABI info
[proc] Executing command: cube-cmake --version
[proc] Executing command: cube-cmake --version
[cmake] -- Detecting CXX compiler ABI info - done
[cmake] -- Check for working CXX compiler: C:/Users/Lenovo/AppData/Local/stm32cube/bundles/gnu-tools-for-stm32/14.3.1+st.2/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
[proc] Executing command: cube-cmake -E capabilities
[cmake] -- Found assembler: C:/Users/Lenovo/AppData/Local/stm32cube/bundles/gnu-tools-for-stm32/14.3.1+st.2/bin/arm-none-eabi-gcc.exe
[cmake] -- Configuring done (3.9s)
[cmake] -- Generating done (0.2s)
[cmake] -- Build files have been written to: D:/work/vscode/test_ymodem2/build/Debug
[proc] Executing command: cube-cmake -E capabilities
[main] Building folder: D:/work/vscode/test_ymodem2/build/Debug 
[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: C:\Users\Lenovo\AppData\Local\stm32cube\bundles\cmake\4.2.3+st.1\bin\cmake.EXE -DCMAKE_BUILD_TYPE=Debug -DCMAKE_TOOLCHAIN_FILE=D:/work/vscode/test_ymodem2/cmake/gcc-arm-none-eabi.cmake -S D:/work/vscode/test_ymodem2 -B D:/work/vscode/test_ymodem2/build/Debug -G Ninja
[cmake] Build type: Debug
[cmake] -- Configuring done (0.1s)
[cmake] -- Generating done (0.1s)
[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: chcp
[proc] Executing command: C:\Users\Lenovo\AppData\Local\stm32cube\bundles\cmake\4.2.3+st.1\bin\cmake.EXE --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 cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_flash_ramfunc.c.obj
[build] [4/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_dma_ex.c.obj
[build] [5/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal.c.obj
[build] [6/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Core/Src/system_stm32g4xx.c.obj
[build] [7/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_exti.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_flash.c.obj
[build] [10/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_cortex.c.obj
[build] [11/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_rcc.c.obj
[build] [12/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_flash_ex.c.obj
[build] [13/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_pwr.c.obj
[build] [14/23] Building C object CMakeFiles/test_ymodem2.dir/Core/Src/syscalls.c.obj
[build] [15/23] Building C object CMakeFiles/test_ymodem2.dir/Core/Src/stm32g4xx_it.c.obj
[build] [16/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_rcc_ex.c.obj
[build] [17/23] Building C object CMakeFiles/test_ymodem2.dir/Core/Src/main.c.obj
[build] [18/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_gpio.c.obj
[build] [19/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_dma.c.obj
[build] [20/23] Building C object CMakeFiles/test_ymodem2.dir/Core/Src/stm32g4xx_hal_msp.c.obj
[build] [21/23] Building C object cmake/stm32cubemx/CMakeFiles/STM32_Drivers.dir/__/__/Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_uart_ex.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:       11580 B       512 KB      2.21%
[driver] Build completed: 00:00:01.260
[build] Build finished with exit code 0

but when I choose the [STM32Cube: STM32 Launch STLink GDB Server, still I got the error

Thanks.

dqsh06 

[Julien D]

I wonder if you removed .settings/ide.store.json as well.

Can you try to setup the project again?

[dqsh06]

Hi @Julien D ,

Yes I have removed .settings/ide.store.json, after excuted the cube bundle commands, I only got 2 json files under .settings. as below

my setup STM32Cube project(s) is gray, it is not active, cannot setup as below.

 

Thanks. 

[Julien D]

Create it with this minimal content and restart VSCode:

{
  "toolchain": "GCC"
}

BTW I assume you are using the latest STM32Cube extensions versions?

[dqsh06]

@Julien D 

Hi, yes I created the file and input the minimal content, and restart VSCode, choose device and click setup STM32Cube projects(s), save it. now the file is as below.

and I click [Run and Debug], get a result like:

open launch.json, as below

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "stlinkgdbtarget",
            "request": "launch",
            "name": "STM32Cube: Launch ST-Link GDB Server",
            "origin": "snippet",
            "cwd": "${workspaceFolder}",
            "preBuild": "${command:st-stm32-ide-debug-launch.build}",
            "runEntry": "main",
            "imagesAndSymbols": [
                {
                    "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}"
                }
            ]
        }
    ]
}

I still cannot get the debug.

Yes, I am using the the latest STM32Cube extensions versions. because 2 days ago after vscode update to version1.111.0, my STM32CubeIDE for vscode became unavailable as mensionned before, I uninstalled all the vscode and extensions and re-install all the latest versions.

Thanks.

[Florent V]

Hi @dqsh06,

I see in the debug console that the ST-Link firmware is not up to date.

Please update the firmware using:

Kind Regards,

/Flo

[dqsh06]

@Florent V @Julien D 

Hi All,

I am using stlinkv2, so I have download the latest ST-LinkUpgrade tool and upgrade my st-link tool to the latest firmwire as below

I will try vscode + run&debug, let's see what will happen. 

Thanks.

[dqsh06]

Hello @Florent V , @Julien D ,

After I updated the stlinkv2 firmware to V2.J47.S7, click [run and debug], it really can download the image and do the debug.

Thanks you all!

Another question is I want to use cortex-debug to do the [run and debug], because before this vscode updated, I used cortex-debug and stm32cubeCLT, then how to config the launch.json to use cortex-debug?

Thanks. 

[Florent V]

Hi @dqsh06,

I am glad you are now able to flash and debug.
Regarding cortex-debug, it is not the solution we provided in our latest deliveries. We now offer a complete solution with our own debug adapters and bundles.
Of course, you can still use the cortex-debug adapter if you want. You can find information about its debug configuration on the GitHub page.

Best Regards,
/Flo

[dqsh06]

@Florent V 

Hi, thanks for your reply. 

I will try to config cortex-debug by myself, because cortex-debug can watch local variables and global variables etc. I am familiar with it.

Best Regards,

dqsh06