Wire seems to be working fine, but Wire1 doesn't even show up on a scanner. #3040
Replies: 2 comments 3 replies
-
Do you have test points on both I2C busses? Can you capture them and see? That'd probably be the only way to really see what's going on with a custom PCB. I just ran the |
Beta Was this translation helpful? Give feedback.
-
Update: It would appear that there's an electronic problem — pullups are 5V, which is making 3.3v LOW insufficiently low. Thank you for helping me reason this out! (Why does it work on the other bus? Unlcear! But it's further away on the PCB and may have juuuust enough resistance on the line that the pullups are reduced?) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've got a PCB here with a RasPi Pico2350 running my firmware. Things seem to be ok, optmiziation notwithstanding.
I am using 8x MCP4725 DACs. The first four are on i2c bus0 with both the A and B versions, so with ground/Vcc pins set they cover 0x060, 061, 062, and 063. The second four are on Wire1, i2c bus 1, with the same set of DACs and pin settings.
Continuity is correct between pins GP10 (SDA) and GP11 (SCL).
I'm ignoring my main code because I fell back to an i2c scanner firmware (at the bottom) and the results were:
(Note that the missing addresses are due to a hardware configuration error. Given that error, this is correct, and bus1 should list the same addresses.
That's where the other ones should show up, pins GP10 and GP11
The code, which I just downloaded and haven't modified:
Beta Was this translation helpful? Give feedback.
All reactions