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

App: Port application to rev 3

未关闭
#271 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 4 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

未指定任何文件、测试或入口点。首先检查 rev 2 应用层、rev 3 文件夹,以及 HW/SW 集成后的计划硬件验证例程。与列出的联系人确认架构;完成的标准是 rev 3 支持 rev 2 功能的严格超集,但明确不支持的驱动程序除外。

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

描述

enhancement

**Requester: @ETSells **

Describe the solution you'd like
Rev 3 needs to port the app layer. There are a couple of ways we can do this:

  1. Branch off of mainline and do regular pull ups from rev 2.
  2. Copy everything from rev 2 into the rev 3 folder.
  3. Add a build flag for rev 3 to the rev 2 makefile and build them out of the same source tree.

I feel like option 3 has the least dual maintenance, so that's my personal preference but as this impacts other projects we will solicit the needs of their leads before committing to that.

Describe alternatives you've considered
See above lol

Additional context
Rev 3 should have a strict SUPERSET of rev 2 features except for certain drivers. In early development though, we might not have support for everything yet.

Scheduling will place this task out after initial HW/SW integration so that we can run the hardware validation routines for each driver.

Points of Contact
This should probably be some kind of combined effort between @NArmistead and @ETSells, at least for design purposes.

主要语言
C
星标
8
派生
6
平均合并
6 天 19 小时
30 天内合并 PR
9

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

SunDevilRocketry/Flight-Computer-Firmware 的其他 Issue

查看 SunDevilRocketry/Flight-Computer-Firmware 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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