AFCv4 - no I2C success verification
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 46
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
When writing to MCP23016 there is no verification if write process was successfully finished (e.g. [here](https://github.com/lnls-dig/openMMC/blob/e95e8d40947b9a3998c1cb4954b8de422d6b8531/port/board/afc-v4/payload.c#L257)).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in port/board/afc-v4/payload.c at the MCP23016 write referenced around line 257, then trace the I2C write path and its existing status reporting. Determine how completion or failure is exposed there; the issue is done when unsuccessful writes are detected and handled, with the relevant firmware checks or tests passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100