Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I2C GPIOs are hardcoded #222

Closed
lurch opened this issue Feb 22, 2016 · 2 comments
Closed

I2C GPIOs are hardcoded #222

lurch opened this issue Feb 22, 2016 · 2 comments
Assignees
Labels
Milestone

Comments

@lurch
Copy link
Contributor

lurch commented Feb 22, 2016

Something I just noticed, is that there's several places where you specify that GPIOs 2 & 3 (i.e physical pins 3 & 5) have fixed hardware pullups. However for very early Rev1.0 Pis, the physical pins 3 & 5 with hardware pullups are actually connected to GPIOs 0 & 1 - see http://elinux.org/RPi_Low-level_peripherals for more info.

GpioZero ought to check the board's Revision (as found in /proc/cpuinfo - see http://elinux.org/RPi_HardwareHistory) and use that to determine which GPIOs have the hardware-pullups.

And of course the ComputeModule doesn't have hardware pullups on any GPIO, although the intersection of ComputeModule users and GpioZero users is likely to be very small ;-)

@waveform80
Copy link
Member

Good point

@waveform80 waveform80 self-assigned this Feb 22, 2016
@waveform80 waveform80 added the bug label Feb 22, 2016
@waveform80 waveform80 added this to the v1.2 milestone Feb 22, 2016
@waveform80
Copy link
Member

Fixed in #246 (including for compute module users :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants