Skip to content

I can't access the target in OpenOCD nor in ST32CubeProgrammer? #59

@otterly41

Description

@otterly41

Error in ST32CubeProgrammer:
: UR connection mode is defined with the HWrst reset mode
: ST-LINK SN : 38FF6F06304E4B3020141243
: ST-LINK FW : V2J42S7
: Board : --
: Voltage : 3.23V
: Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

I also tried Visual Studio Code, I get this error message:
xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2022-09-01-17:58)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
CDRTOSConfigure
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 : Listening on port 50001 for tcl connections
Info : Listening on port 50002 for telnet connections
Info : clock speed 2000 kHz
Info : STLINK V2J42S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.230406
Error: init mode failed (unable to connect to the target)

[2023-06-26T19:37:37.428Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session closed

I double-checked the connections and all the STM32 pins are connected in the right place, also including the ground pin too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions