Skip to content

Stm32cubeide and stlink v2 #32

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

Open
peterscottie opened this issue Jul 18, 2024 · 1 comment
Open

Stm32cubeide and stlink v2 #32

peterscottie opened this issue Jul 18, 2024 · 1 comment

Comments

@peterscottie
Copy link

When I try to debug
STM32Cube IDE pops up a dialog box saying could not verify ST device. Ive tried updating the firmware and it still does the same.
.
However Openocd -d2 says this

    http://openocd.org/doc/doxygen/bugs.html

Info : auto-selecting first available session transport "hla_swd". To override use 'transport select '.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : DEPRECATED target event trace-config; use TPIU events {pre,post}-{enable,disable}
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 1000 kHz
Info : STLINK V2J45S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.126316
Info : [stm32f1x.cpu] Cortex-M3 r1p1 processor detected
Info : [stm32f1x.cpu] target has 6 breakpoints, 4 watchpoints
Info : starting gdb server for stm32f1x.cpu on 3333
Info : Listening on port 3333 for gdb connections
[stm32f1x.cpu] halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x08008278 psp: 0x20000678
Info : accepting 'gdb' connection on tcp/3333
Info : device id = 0x10036414
Info : flash size = 256 KiB
Error: Invalid AP#0x0
Info : dropped 'gdb' connection

Many Thanks
Any Ideas?

@lprobsth
Copy link

lprobsth commented Mar 6, 2025

Same here. I tried using the STM version of OpenOCD after the verification of the board failed with the OpenOCD version supplied with ubuntu.

Most of the posts regarding this topic suggest that the board might be counterfeit. But we are pretty sure that the STM32 nucleo board is an original one.

I have seen reports of the validation error in CubeIDE versions 1.14+ (I'm currently trying 1.17). So this might be a bug in CubeIDE.
A possible workaround might be using the OpenOCD debug interface of Eclipse as shown in this post: https://electronics.stackexchange.com/a/708499

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

2 participants