[FEATURE] MCUmgr support

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

该 issue 未指定任何 NuttX 文件、测试或入口点。首先比较 Apache Mynewt 和 Zephyr 的 mcumgr 实现,包括它们的管理命令和传输支持。要视为完成,必须确定源代码与维护方式,并定义 NuttX 集成范围。

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

描述

Type: Enhancement
Is your feature request related to a problem? Please describe.

Hi, does anyone have mcumgr ported on NuttX?

If not, I think it's a project worth porting, as it would provide a tool for managing remote devices and, most importantly, DFU over the Simple Management Protocol (e.g., over BLE). An out-of-the-box tool for managing remote devices is something I feel is missing in NuttX.

If no one has implemented this yet, I might look into it one day. However, I have a few concerns about this task.

Describe the solution you'd like

Currently there are 2 implementations of mcumgr:

  1. The original project from Mynwet - https://github.com/apache/mynewt-mcumgr/
  2. Zephyr version, developed in parallel - https://github.com/zephyrproject-rtos/zephyr/tree/main/subsys/mgmt/mcumgr
    Initially, Zephyr used the Mynewt version directly, but they decided to incorporate
    the code directly into Zephyr. Details can be found here:

Currently Zephyr version has more functionalities (such as mcumgr client and additional
management commands).

So my questions are:

  1. Which code should we port: the Mynewt version or the Zephyr version ?
    Both have Apache licenses, so the license is not an issue. Zephyr has more
    functionalities, but the porting requires more effort.

  2. Should we adopt an approach similar to Zephyr, where we maintain our own version of the
    code, or should we clone active project ?
    If we choose the second approach (git clone), the Zephyr version is probably out of
    the question - cloning the entire Zephyr project is a bad idea.

    Keeping its entire code in our repo could offer benefits, such as implementing NuttX-specific commands,
    transports and optimizations. All the arguments from the discussion in Zephyr issue above also apply here.

Describe alternatives you've considered

No response

Verification
  • I have verified before submitting the report.
主要语言
C
星标
475
派生
811
平均合并
1 天 11 小时
30 天内合并 PR
181

环境准备

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

从这里开始

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

apache/nuttx-apps 的其他 Issue

查看 apache/nuttx-apps 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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