proveskit / proveskit/flight_controller_board

[BUG] I2C Pull Ups Too Strong on V5c

Open
#40 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
HTML
Stars
6
Forks
5
Avg merge
49m
Merged PRs (30d)
1

Description

Summary

I understand now why Adafruit use 10k resistors on all their stuff
Because so many of their boards have their own pull ups or level shifters or whatever
Let's say you connect two I2C buses with 10k's on each side together
In parallel you end up at 5K which is really close to the recommended 4.7k
But because we switched everything to 4.7k
When two sides get connected now you end up at 2.35k which is dangerously close to the minimum allowable for I2C
Actually some of the stuff might not even work at all because it will end up being too strong of a pullup
So yeah, rough
I added a buffer in front of the TCA on the Flight Controller Board TCA I2C Multiplexer
Basically worst case, I think we would be looking at 4.7k / 3 which is 1.57k
When the RP2350 is connecting all the way through to a sensor on a solar face I think the combined pull ups on the I2C bus will be too strong to allow it to operate correctly
I need to test this experimentally

Possible Remedy

But I think the easiest thing for us to do to remedy this will be to yeet the TCA I2C buffer on the FC board

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by experimentally testing the combined I2C pull-ups described for the Flight Controller Board TCA I2C Multiplexer and connected solar-face sensor path. Confirm whether the bus operates correctly with the existing buffer arrangement; done means the pull-up strength is within an acceptable range and the chosen remedy is validated.

Written by the indexing model from the issue text.

Assessment

Tech stack
embedded-iot
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.