-
Notifications
You must be signed in to change notification settings - Fork 137
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
linuxgpio issues #932
Comments
I have never tried this option but it seems to me from various website that -P is not required. |
Do you think moving to libgpiod will help to sort out this issue? |
I will try out set up the test setup using linuxspi/linuxgpio as well since I have quite a few Raspberry Pi boards (Raspberry Pi 3B+ and 400) as well as Orange Pi boards. |
I have followed the follow two guides to get linuxspi working and I will test out linuxgpio as well. Ref: @MCUdude |
Somehow I could not even be able to get linuxgpio working, probably because I ran linuxspi first which I used GPIO25 for the reset pin as well.
@MCUdude
|
Rebooting the Raspberry Pi 3B+ sorted out the issue.
Pull request #917 should help as well. |
With the above setup, I can confirm issue #455 is a bug and it applies to both linuxgpio and linuxspi. |
I agree,
This is a real pain. I think we have to move away from sysfs to libgpiod. |
#1299 have been created to add libgpiod support. |
Absolutely! |
I've just stepped into the linuxspi/linuxgpio land, and the process hasn't been as straightforward as with other programmers.
First, it requires a port passed as a
-P
argument. I can't find any documentation on what this port is supposed to be, but-P GPIO
seems to do the trick. A default option should be present IMO.The other issue I've had is that when a session is force-terminated using ctrl+c, the GPIOs remain "occupied", which is a real bummer...
The text was updated successfully, but these errors were encountered: