cancel
Showing results for 
Search instead for 
Did you mean: 

Problems using latest standard openocd build with STM32U5A9J-DK (SOLVED)

TerryFogg
Associate

Hopefully someone can help.

Below I get some connection and identification proceeding, but it fails at the end with

"Cannot identify target as an STM32G0/G4/L4/L4+/L5/U5/WB/WL family device."

 

 

UPDATE!: I copied the openocd.exe from my installation of stm32CubeIde and it works.

Although there is a STM32U5x.cfg added to the latest openocd on the official build, there must be something missing from the binary, which I can fix by using the STM32CubeIde openocd.exe

 

 

 

 

 

Original Problem

Open On-Chip Debugger 0.12.0 (2023-01-14-23:37)
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>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Warn : The selected adapter does not support debugging this device in secure mode
Info : clock speed 500 kHz
Info : STLINK V3J10M3 (API v3) VID:PID 0483:374E
Info : Target voltage: 1.796388
Info : [stm32u5x.cpu] Cortex-M33 r0p4 processor detected
Info : [stm32u5x.cpu] target has 8 breakpoints, 4 watchpoints
Info : starting gdb server for stm32u5x.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : Unable to match requested speed 480 kHz, using 200 kHz
Info : Unable to match requested speed 480 kHz, using 200 kHz
CPU in Non-Secure state
[stm32u5x.cpu] halted due to debug-request, current mode: Thread
xPSR: 0xf9000000 pc: 0x0808a8ac msp: 0x20043250
Info : Unable to match requested speed 4000 kHz, using 3300 kHz
Info : Unable to match requested speed 4000 kHz, using 3300 kHz
** Programming Started **
Warn : Cannot identify target as an STM32G0/G4/L4/L4+/L5/U5/WB/WL family device.
C:\nf-interpreter\EXEC : error : auto_probe failed
embedded:startup.tcl:1516: Error: ** Programming Failed **
in procedure 'program'
in procedure 'program_error' called at file "embedded:startup.tcl", line 1581
at file "embedded:startup.tcl", line 1516

 

1 REPLY 1
Amel NASRI
ST Employee

Hi @TerryFogg ,

Thanks for coming back with the solution you found. I suggest you repeat the solution in a new reply that you mark as a solution. 

-Amel

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.