Make microzig_main automatically call `init` for board
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 18/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- embedded-iot, zig
- 领域
- embedded-iot
调研方向
The hook point is microzig_main in core/src/start.zig, which already calls the app and HAL init. Read how the board module is referenced there and how the nordic and wch example apps call board.init() today. The open question is ordering: whether the board init replaces or runs alongside chip/cpu init, and this needs a maintainer decision before any code. Done means a settled ordering rule, with examples updated to stop calling board.init() manually.
由索引模型根据 Issue 内容生成。
描述
From this comment from @tact1m4n3.
In the nordic and wch hals (maybe others) we have the example apps explicitly call board.init().
Maybe we should add logic to microzig_main to call it if its present. It already does this for the app and for the hal.
Makes sense to me, my only real concern is whether this call should supercede an init for the chip/cpu, or be called in addition to it.
- If its the former, then the board init should probably call the chip init, which should probably call the cpu init.
- This grants extra flexibility (A board might opt not to call a chip init, for the reason below)
- But it's also extra boilerplate (more boards should call chip init, which should call cpu init) and duplicated code (they might opt to manually do some work, which is more places to make sure to update)
- If it's the latter, I think we run the risk of some configs doing extra work (best case) or trashing each other.
- For example, a chip setting up RCC to set up the clocks, only for a board, with an external clock, to immediately set them up again with an external clock.
- 主要语言
- Zig
- 星标
- 2.3k
- 派生
- 198
- 平均合并
- 1 天 8 小时
- 30 天内合并 PR
- 37
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ZigEmbeddedGroup/microzig 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 88/100
ZigEmbeddedGroup/microzig#1086 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 69/100
ZigEmbeddedGroup/microzig#1085 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
ZigEmbeddedGroup/microzig#1061 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
ZigEmbeddedGroup/microzig#1059 · 1 条评论 ·
维护者通常 1 天内回复
-
regz: AVR peripherals generated at address 0 when the register-group name matches the module (ATDF)未关闭
难度 4/5 3-5 天 新手友好度 48/100
ZigEmbeddedGroup/microzig#1072 ·
维护者通常 1 天内回复
查看 ZigEmbeddedGroup/microzig 的全部 Issue
相似的 Issue
-
[BUG] OTA Requestor accepts reserved provider endpoint 0xFFFF可能已有人在做 @Chapoly1305 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
project-chip/connectedhomeip#74742 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 63/100
Xinyuan-LilyGO/T-Display-S3#352 · 3 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 79/100
lsongdev/node-bluetooth#62 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
-
`espup update` fails with `File exists (os error 17)` when `~/.espup/esp-clang` is a dangling symlink可能已有人在做 @SergioGasquez 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100