-
Notifications
You must be signed in to change notification settings - Fork 303
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
Pi internal LEDs (47) no longer accessible with gpiozero v2.0 #1092
Comments
As a workaround, I'm shoehorning GPIO47 into PLUS_J8 before having a pin factory set:
or 29 for the zero2w https://forums.raspberrypi.com/viewtopic.php?t=324132 |
I'm afraid this is a casualty of the new means of accessing GPIO pins. It is possible to address non-physical GPIOs via the gpiochip devices but most that users would be interested in are already marked "in use" by the kernel, and so cannot be allocated. For instance, output from
The
Option 1 horrifically complicates the internal APIs, so that was out. Options 2 and 3 are both "nasty", but if the future is "everything goes via the kernel" and "GPIOs shall not be shared among processes" then only option 3 is realistic. That said, I have noticed that I failed to remember to remove the section on controlling internal LEDs from the docs. That needs to be dealt with, so I'm assigning this to me. |
By "non-physical GPIOs" do you mean any GPIO that isn't present on the Pi's 40-way GPIO header? |
Yes, sorry -- should've made that clear. It's a clunky turn of phrase, but then so is "GPIO not exposed on the header". Suggestions welcome for anything similarly brief, but more comprehensible! |
Operating system: Raspbian Bookworm
Python version: 3.11
Pi model: Pi Zero W
GPIO Zero version: 2.0
Pin factory used: RPiGPIO
The text was updated successfully, but these errors were encountered: