Stm32cubeide and stlink v2

Open

#32 opened on Jul 18, 2024 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 25/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: c
Domain: devtools, embedded-iot

Research direction

Start by reproducing the STM32CubeIDE/ST-Link V2 debug session and compare it with the OpenOCD output in the report. Focus on the Invalid AP#0x0 failure after the GDB connection is accepted; done means the ST device is verified and the debug session remains connected without that error.

Written by the indexing model from the issue text.

Description

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?

Dominant language: C
Stars: 202
Forks: 57
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.