BMA456 accelerometer (U43) has no firmware, so the part on the board has no use yet

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
28/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
arduino, cpp
领域
embedded-iot

调研方向

Read the existing LIS3DH implementation in Apis_Library, especially getPitch() and getRoll(), and the library design rule on sharing code. Then consult the BMA456 datasheet to determine whether plain acceleration reads require Bosch’s feature-engine configuration blob. The work is complete when the driver, shared orientation reduction, data-row and status-snapshot fields are implemented and a hardware test passes.

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

描述

bug

The Okapi redesign (Project-Okapi v0.6.0, the KiCad board) carries a BMA456 accelerometer, U43, on the on-board I2C segment at 0x18, powered from 3V3_AUX. Nothing in this library or anywhere else in the workspace talks to it, so a built board would have a part that does nothing.

What it is for (Andy, 2026-11-05): the board's orientation when desired, read at a wake. Not continuous sampling and not motion or impulse events, which is why its INT pin is a no-connect on the board.

What the firmware needs:

  1. A BMA456 driver from its datasheet: power mode, the acceleration registers, and whether Bosch's feature-engine configuration blob is needed for plain acceleration reads (to confirm before writing to the part; the plain registers may not need it).
  2. The orientation reduction, pitch and roll against a stored zero, which Apis_Library already does for its LIS3DH (getPitch(), getRoll()) and which should be shared rather than copied, per the library design's rule on copies.
  3. The reading's place in the data row and in the status snapshot.

A hardware test on a board closes it. No milestone here; the hardware side is Project-Okapi v0.7.0.

🤖 Generated with Claude Code

https://claude.ai/code/session_017F2gr2axqf8HWh46zhsQyY

主要语言
C++
星标
1
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

NorthernWidget/Okapi_Library 的其他 Issue

查看 NorthernWidget/Okapi_Library 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

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