Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add support for CH32H417

未关闭
#1,023 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
32/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
zig
领域
embedded-iot

调研方向

The issue names no MicroZig files, tests, or entry points. Start by reading the existing CH32V support and comparing it with the CH32H417’s two-core MountRiver Studio workflow, which builds separate firmware binaries and merges them into one .bin. The issue leaves the project structure and port design undecided, so clarify those before implementation.

由索引模型根据 Issue 内容生成。

描述

support

CH32H417 is a heterogeneous dual-core RISC-V MCU from WCH (Nanjing Qinheng Microelectronics), featuring one QingKe V3F core and one QingKe V5F core. I'm opening a separate issue rather than commenting on the tracking issue because this heterogeneity raises questions beyond a typical single-core port.
MicroZig already supports the CH32V family, but the official MountRiver Studio workflow for the CH32H417 is quite different: you write two separate firmware binaries, one for each core, and then merge them into a single .bin file that can be flashed to the chip. I'm not sure how MicroZig should organize this kind of multi-core project — that is, how the two cores' firmware should be structured.
I recently bought a nanoCH32H417 board and would be happy to contribute the port.

主要语言
Zig
星标
2.3k
派生
198
平均合并
1 天 17 小时
30 天内合并 PR
25

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ZigEmbeddedGroup/microzig 的其他 Issue

查看 ZigEmbeddedGroup/microzig 的全部 Issue

相似的 Issue

更多 Embedded & IoT Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。