2025-06-16 3:46 PM
We have a custom loader from one of our boards. It is working in STM32 Cube MX Prog V2.16 but when I launch V2.19 and try to connect to a unrelated boards I get this error:
The error is understandable because the path to the loaders is incorrect. The issue is I never told V2.19 to use this external loader and it doesn't even show up in the list of available loaders. It some how figured out that I have used this loader in the past (but it didn't quite figure out the correct location of the loader) and for some reason it is trying to access it. I mess with loaders so infrequently I have no idea how to fix this issue.
The custom loader does show up in V2.16 and doesn't produce this error:
Suggestions?
Jacob
2025-06-17 11:47 PM - edited 2025-06-17 11:51 PM
Hello @J.Christ ,
What is your hardware board ? Is it a Nucleo or custom board?
Does have any protections enabled? If yes, try disable the read protection.
Maybe you have the same issue as this thread: Solved: STM32CubeProgrammer cannot connect to MCU
2025-10-14 3:57 AM
There is a similar thread on https://community.st.com/t5/stm32cubeprogrammer-mcus/unable-to-flash-with-stm32cubeprogrammer/td-p/702988
2025-10-14 8:36 AM - edited 2025-10-14 8:41 AM
Hello,
That's because the loader value is cached (For all versions). To workaround this:
1- Close CubeProgrammer
2- Go to "C:\Users\[YOUR_USER_NAME]\STMicroelectronics\STM32CubeProgrammer" and delete "config.properties" file
3- Reopen STM32CubeProgrammer.
PS: If you're on Linux, the path is "/home/[YOUR_USER_NAME]/.STM32CubeProgrammer"
You should no longer have the pop-up.
Hope this helps,
Aziz
2025-10-14 8:53 AM
Thanks Aziz. Unfortunately deleting this file does not help (on Linux it is located at /home/[user]/.STM32CubeProgrammer/config.properties)