Does the IDE support debugging of the STM32VLDISCOVERY board? How do I configure the debugger for this board?

[Roger.ch]

..

[A�?ah]

I get this error "This debug configuration is associated to a target which is not promoting any debug device (or debug device not supported)".

Did you find any solution?

[Ozone]

The error message does not really sound comprehensible.

However, the VL Discovery is quite old, with a totally messed-up ST-Link implementation V1.0.

Not sure if it is properly supported by your PC/IDE.

Can you see the device in the host OS (Hardware manager under Windows, or lsusb command under Linux) ?

[A�?ah]

Yes device is connected and i can see it in the list.

[Markus GIRDLAND]

You can't really configure the debugger for that board.

This is because STM32VLDISCOVERY uses ST-LINK v1 which is not supported in STM32CubeIDE. The reason for this is that v1 is a deprecated design with limited support for the advanced debug features available in STM32CubeIDE. Ideally, the device should not be available in MCUFinder when using STM32CubeIDE. We will consider this as an improvement for future releases.

What IDE did you use previously? To the best of my knowledge that board isn't able to be used with SW4STM32 or newer versions of TrueSTUDIO either. You could use TrueSTUDIO 9.0.1 version, it's before we integrated CubeProgrammer which is also integrated into STM32CubeIDE. CubeProgrammer doesn't support v1 either.

You can download TrueSTUDIO here:

https://atollic.com/resources/download/windows/windows-archive/

[A�?ah]

Thank you for the answer.

I used keil uvision but unfortunately i switched my system to mac a while ago. And any of these various IDEs doesn't support mac. So i think i should use parallel or bootcamp until cube support st-link v1

[Roger.ch]

Thank you for your answer, Markus. A colleague of mine has to debug an ancient design. The application is not from Him. He wanted to start from scratch on the Discovery Board. But that doesn't seem to be the best idea. ;) 

[Georgy Moshkin]

If you found this thread and want just to flash and run simple projects to your STM32VLDISCOVERY without debug, use can configure CubeIDE to use ST-LINK_CLI.EXE for flash and run:

1. Install st-link utilites

2. in stm32cubeide open Project→ Properties→ C/C++ Build→ Settings→ tab "Tool Settings" → MCU Post build outputs check "Convert to Intel Hex file"

3. in Run → Debug Configurations double-click on first line "C/C++ Application" to create new configuration. Under the tab "Main" set "C/C++ Application" to C:\Program Files (x86)\STMicroelectronics\STM32 ST-LINK Utility\ST-LINK Utility\ST-LINK_CLI.exe, under the tab "Arguments" set "Program arguments" to -c SWD -P ${project_loc}\${config_name:${project_name}}\${project_name}.hex -Rst, under the tab "Common" check "Display in favorites menu" – "Run"

4. in Window → Preferences → General → Keys set Command "Run" Binding to Ctrl+F11

Now you can write simple code and quickly flash it to your STM32VLDISCOVERY by pressing Ctrl+B and then Ctrl+F11. Although debugger is not working, you can still find some bugs and solve problems by manually sending debug information over UART using TTL to USB converter.

[APorkSandwich]

Georgy,

I really appreciate that you made this comment. I thought I was out of luck getting the CubeIDE to program my VLDiscovery Board. I followed your steps and can confirm that they work!

Thanks again.

[Steniweb]

Dear community,

thanks for knowledgeable answers, and specific thanks to Georgy whose advise I used for years to operate STM32VLDISCOVERY. Now recently I bought an ST-Link/V2-isol device and operated the MCU on VL DISCOVERY BOard directly. However I still get the error message that the STM32VLDOSCOVERY Board is not supported by IDE Cube for debugging (same error message like first A�?ah). The ST-Link/V2 seems to be recognized well because I could register in the debug configuration

. Does any body have an idea, what to do?

[SithZavv]

Kinda late to the party (it's now March 2025) and struggled through the same things with my recent purchase of two discovery boards:

board 1: STM32F100RB (aka STM32VLDISCOVERY) STM32VLDISCOVERY - Discovery kit with STM32F100RB MCU - STMicroelectronics
--> this F1 board has ST-LINK (V1), full of trouble with all STM32Cube software tools; Windows 10 only recognized it as mass storage device, no ST-Link showed up as USB device.
board 2: STM32F411VET6 https://www.st.com/en/evaluation-tools/32f411ediscovery.html
--> this F4 board has ST-LINK (V2), working fine so far with all STM32Cube software tools; and Windows 10 showed ST-Link as USB device only, no mass storage device whatsoever.

Here are my footsteps:

1. Read few chapter of "Discovering the STM32 Microcontroller" by Geoffrey Brown listed on
https://www.st.com/content/st_com/en/support/learning/stm32-education/text-books.html
and purchased the STM32VLDISCOVERY as recommended...
bad choice I guess as it's a legacy product; should be removed from board selector (and create an up-to-date F1 discovery board) imo.

2. Followed the tutorial at https://wiki.st.com/stm32mcu/wiki/STM32StepByStep:Step1_Tools_installation
and struggled with the build/run/debug step because ST-LINK (V1) is incompatible with STM32Cube tools (this was not mentioned anywhere until I see this post).

3. Followed Georgy Moshkin's steps above which enabled me to build & run onto the STM32VLDISCOVERY via STM32CubeIDE.

For now, I'll personally abandon the F1 board and focus on the F4 board since my goal is to learn the basics and quickly create a small demo application for Cortex M (via ST's board).