mipidisaster / mipidisaster/miLibrary
I2C NACK interrupt will cause de-synchronisation of data
Open
Nobody has claimed this yet.
bug
invalid
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
As the title says, currently if there is a NACK detected, the target array (if GenBuffer) will cause de-synchronisation for any Master writes (read should be alright)
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 drv/I2CDevice/I2CDevice.cpp at lines 1202-1210 and trace the NACK interrupt path for GenBuffer master writes. Reproduce or inspect the write handling, then verify that a NACK no longer desynchronizes the target array while read behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100