-
Notifications
You must be signed in to change notification settings - Fork 261
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
Jetapck 6 with libgpiod broken #110
Comments
Okay it is actually working but the pin state reverts to default when the script exits. In Jetpack 5 the pin stays in the state its in when the script exits. In Jetpack 6, the pin reverts back to the default pinmux state. |
This is what I found for gpioset. https://manpages.debian.org/testing/gpiod/gpioset.1.en.html Modes:¶ |
we clean up the pin state when python code exit. We dont support different mode like this for the library. I dont think we have the functionality to set the drive mode like gpioset also. |
I'm not concerned with the behavior of gpioset but this python library. If you don't call cleanup, it should leave the pin in the state you set it to. |
Okay so this comes back to the fundamental change over to libgpiod. I changed my pinmux on this pin to output drive high by default. But even in the python script that only ever drives the pin high, when the script exits, it goes back to low. Any interaction with the pin will cause it to reset to low. |
Coming from everything working in Jetpack 5, I am unable to get pin 32 working in Jetpack 6. Pin 33 works, Pin 32 doesn't. It does work through gpioset but not through jetson-gpio.
https://forums.developer.nvidia.com/t/gpio07-pg-06-not-working-in-jetpack-6/293013
The text was updated successfully, but these errors were encountered: