Status of the fork and upstreaming changes

Open

#20 opened on May 31, 2023 1 comment 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 15/100

Issue type: Documentation
Clarity: Needs clarification
Activity status: Stale
Tech stack: c
Domain: devtools

Research direction

Start by reviewing the repository description and its relationship to the original OpenOCD project. Done means documenting the intended role of this fork, whether changes should be upstreamed, and whether individual commits may be cherry-picked upstream.

Written by the indexing model from the issue text.

Description

Hi,

since this is a fork of the original OpenOCD, I would like to know what the intended role of this fork is. Especially I would really like to have the support for newer STM32 chips upstream back into the original project, since that one is installed via the package manager.

Do you plan to upstream your work? If not, is there any problem is cherry picking any commit back to upstream?

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

Flash algorithm double-faults into lockup when programming after halting a running application — armv7m runner does not sanitize MPU/stack-limit state (STM32H503, deterministic repro, bisected minimal fix) Open

Difficulty 4/5 3-5 days Newbie friendliness 55/100

STMicroelectronics/OpenOCD#52 · Opened Aug 27, 2026
Compilation failure on gcc-15.2.0 Open

Difficulty 3/5 1-2 days Newbie friendliness 67/100

STMicroelectronics/OpenOCD#51 · Opened Jul 8, 2026
stmqspi: OCTOSPI DR 8-bit access is unreliable on STM32H7R7/XSPI, and unconditional ABORT may wedge BUSY Open

Difficulty 3/5 1-2 days Newbie friendliness 68/100

STMicroelectronics/OpenOCD#50 · Opened Apr 8, 2026
STM32H7x option_write reads incorrect address in flash Open

Difficulty 4/5 3-5 days Newbie friendliness 45/100

STMicroelectronics/OpenOCD#45 · Opened Jan 13, 2026
STM32N647: OpenOCD halt/debug fails with UNDEFINED while CubeIDE works Open

bug

STMicroelectronics/OpenOCD#44 · 1 comment · 1 assignee · Opened Dec 25, 2025

All issues in STMicroelectronics/OpenOCD

Similar issues

Remove `--disable-sandbox` workaround from the CodeQL workflow Open

task

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

vsanthanam/JBird#429 · Opened Sep 24, 2026
deprecate (and remove) qasm3.load_experimental Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

Qiskit/qiskit#17045 · Opened Sep 24, 2026
cleanup: small correctness and doc nits found during #152 Open

bug documentation

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

es-ude/OnDeviceTraining#459 · Opened Sep 24, 2026
Extend unnecessary_null_check to g_object_unref Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

bilelmoussaoui/gobject-linter#199 · 1 comment · Opened Sep 24, 2026
plum build . without -o names the binary "." and fails to link Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

bradcypert/plum#53 · Opened Sep 24, 2026

A short digest of beginner-friendly GitHub issues.