Skip to content
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

Open
DBY29681 opened this issue May 31, 2024 · 4 comments
Open

STM32H5 Error: The selected transport doesn't support this target #27

DBY29681 opened this issue May 31, 2024 · 4 comments

Comments

@DBY29681
Copy link

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

@MartinPoupa
Copy link

Hello, i have similar problem. I am training flesh stm32H503 via STM32CubeMX and VSCode on ubuntu 22. Thanks you for help.

Open On-Chip Debugger 0.12.0-00024-g34afaa939 (2024-08-29-13:52) [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 <transport>'.
Error: The selected transport doesn't support this target
/usr/local/bin/../share/openocd/scripts/target/stm32h5x.cfg:55: Error: 
in procedure 'script' 
at file "embedded:startup.tcl", line 28
at file "./openocd.cfg", line 8
at file "/usr/local/bin/../share/openocd/scripts/target/stm32h5x.cfg", line 55

@cosmikwolf
Copy link

Having this same problem, with the STM32H563 Nucleo 144 board

@cosmikwolf
Copy link

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

@DBY29681
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants