Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Request to upstream STM32 support (e.g. STM32H5) or provide pre-built binaries of the ST fork

Open
#42 9 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, github-actions

Research direction

Review the STM32H5 and other recent-device support in this fork, then compare it with official OpenOCD to determine what upstreaming would require. If upstreaming is not feasible, inspect the proposed GitHub Actions build path and Releases workflow; done means either the support is upstreamed or binaries are published for Windows, Linux, and macOS.

Written by the indexing model from the issue text.

Description

Hello!

You have lots of changes and support for new devices in your OpenOCD fork that are not yet included in the official OpenOCD repository. For example, STM32H5 support and other recent STM32 series are only available in the fork.

With the OpenOCD 1.0 release approaching, it would be very valuable if these changes could be upstreamed.

If upstreaming is not possible in the short term, could you please provide pre-built binaries of your forked OpenOCD for Windows, Linux, and macOS so that the community can use the new device support more easily? This could be relatively straightforward to implement using GitHub Actions for building, and the resulting binaries could be published via the repository’s Releases.

Thank you for the great work you have done so far!

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from STMicroelectronics/OpenOCD

All issues in STMicroelectronics/OpenOCD

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.