STM32F767ZG says "Cortex-M PARTNO 0x0 is unrecognized"

Open

#21 opened on Jun 25, 2023 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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

Research direction

Start by reproducing the reported connection to the STM32F767ZG with the OpenOCD 0.12.0 build and compare the target-examination log, especially the "Cortex-M PARTNO 0x0" error. Investigate the STM32F7 target-detection path; done means the target is examined successfully and the GDB server can be used without these errors.

Written by the indexing model from the issue text.

Description

I am unable to connect to STM32F767ZG

Open On-Chip Debugger 0.12.0-00017-gb153daa14 (2023-02-03-14:58) [https://github.com/STMicroelectronics/OpenOCD]
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
none separate

Info : clock speed 4000 kHz
Info : STLINK V2J34S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.254183
Error: [stm32f7x.cpu] Cortex-M PARTNO 0x0 is unrecognized
Warn : target stm32f7x.cpu examination failed
Info : starting gdb server for stm32f7x.cpu on 3333
Info : Listening on port 3333 for gdb connections
Error: [stm32f7x.cpu] Cortex-M PARTNO 0x0 is unrecognized
Error: Target not examined yet

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.