OpenOCD Fails to Identify STM32U3 Device
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- c
- Domain
- devtools, embedded-iot
Research direction
Start by reproducing the connection failure with the NUCLEO STM32U385RG-Q and the STM32CubeMX-generated .cfg file. Trace the STM32 family auto_probe path reported in the error, focusing on why the STM32U3 device is not identified. Done means OpenOCD recognizes the STM32U3 target and establishes the debug connection without the reported auto_probe failure.
Written by the indexing model from the issue text.
Description
Hi team,
I'm currently trying to debug an STM32U3 series microcontroller using OpenOCD. Since OpenOCD does not yet include an official configuration file for the STM32U3 family, I used the config file generated by STM32CubeMX.
However, when I attempt to connect to the target, I receive the following errors:
CPU in Non-Secure state [stm32u3.cpu] halted due to debug-request, current mode: Thread xPSR: 0x69000000 pc: 0x0800066c msp: 0x2002fff8 Error: Failed to read memory at 0x40015800 Warn : Cannot identify target as an STM32C0/G0/G4/L4/L4+/L5/U0/U5/WB/WL family device. Error: auto_probe failed
Details:
MCU: NUCLEO STM32U385RG-Q
Config: Using the .cfg file auto-generated by STM32CubeMX
It seems the STM32U3 series is not recognised. Is there any ongoing work or guidance on adding support for the STM32U3 series to OpenOCD?
Thanks in advance!
- 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.
More from STMicroelectronics/OpenOCD
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug
STMicroelectronics/OpenOCD#44 · 1 comment · 1 assignee ·
All issues in STMicroelectronics/OpenOCD
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·