-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STM32H5 Error: The selected transport doesn't support this target #27
Comments
Hello, i have similar problem. I am training flesh stm32H503 via STM32CubeMX and VSCode on ubuntu 22. Thanks you for help.
|
Having this same problem, with the STM32H563 Nucleo 144 board |
I found that if I set the CHIPNAME to something that wasn't stm32h5x, it diddn't like it. I had it set to STM32H563 before. I just removed the chipname setting all together, since it is set in the stm32h5x.cfg and it works now |
Can you share your configuration? I remember configuring the target as stm32h5x and encountering this error where the linking script cannot find the target under the openocd target |
First I had the same problem... However it works with stlink-dap.cfg interface file. |
Open On-Chip Debugger 0.12.0-00024-g34afaa939 (2024-05-31-15:10) [https://github.com/STMicroelectronics/OpenOCD]
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select '.
Error: The selected transport doesn't support this target
D:/Environment/MSYS64/mingw64/bin/../share/openocd/scripts/target/stm32h5x.cfg:55: Error:
in procedure 'script'
at file "embedded:startup.tcl", line 28
at file "D:/Environment/MSYS64/mingw64/bin/../share/openocd/scripts/target/stm32h5x.cfg", line 55
The text was updated successfully, but these errors were encountered: