I2C transactions errors
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
In certain configurations, I2C transactions fail. E.g. when on running in a VM on a laptop with a direct network connection to an FMC+Enclustra, or timing app monitoring software running on np04-srv-002 communication with PROD_MASTER_VDC (direct connection, no issue if connection is done through the control hub on np04-srv-012).
Issue suspected to be related "mid-level" I2C bus control over network and/or PC CPU.
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
No files or tests are identified. Start by reproducing the failing I2C transactions in the VM/laptop and np04-srv-002 direct-connection configurations, then compare them with the working control-hub path through np04-srv-012. Done means the mid-level I2C, network, or CPU-related cause is identified and the affected configurations communicate reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100