STM32F769 Not reading from D-Cache
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 STM32F769 D-Cache read problem on Cortex-M7 with the latest build, then compare the result with mainstream OpenOCD 0.11.0. The issue is done when the customized OpenOCD build reads the expected cached values consistently.
Written by the indexing model from the issue text.
Description
The latest build does not appear to be reading values from the D-Cache on Cortex-M7
The mainstream OpenOCD 0.11.0 works
- Dominant language
- C
- Stars
- 205
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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
-
STM32N647: OpenOCD halt/debug fails with UNDEFINED while CubeIDE worksMay be free again @tarek-bochkati claimed this 271 days ago, and no pull request is open. Openbug
STMicroelectronics/OpenOCD#44 · 1 comment · 1 assignee ·
All issues in STMicroelectronics/OpenOCD
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libsdl-org/SDL#16444 ·
Maintainers usually reply within 1 day
-
bug Component component: net
Difficulty 1/5 Under an hour Newbie friendliness 90/100
RT-Thread/rt-thread#11852 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MiSTer-devel/ao486_MiSTer#243 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
siderolabs/pkgs#1710 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
qmk/qmk_firmware#26498 ·
Maintainers usually reply within 1 day