Troubleshooting • Re: Busy GPIO's Raspberry PI5

Seems 'gpioinfo' reports the same before and after for the pins being used - all unused inputs, but 'pinctrl' before, immediately after boot -

Code:

 5: no    pu | -- // PIN29/GPIO5 = none 6: no    pu | -- // PIN31/GPIO6 = none13: no    pd | -- // PIN33/GPIO13 = none19: no    pd | -- // PIN35/GPIO19 = none26: no    pd | -- // PIN37/GPIO26 = none

Has changed after -

Code:

 5: ip    pn | lo // PIN29/GPIO5 = input 6: ip    pn | lo // PIN31/GPIO6 = input13: ip    pn | lo // PIN33/GPIO13 = input19: ip    pn | lo // PIN35/GPIO19 = input26: ip    pn | lo // PIN37/GPIO26 = input

It has been noted elsewhere that the Pi 5 seems to be "none" after boot, while a Pi 4B running Bookworm reports "input", so there is some anomaly there. But it's not clear what the cause of 'GPIO Busy' is. If that's the case for VS Code and command line it would suggest it's not an issue with VS Code per se. But then it's odd that your earlier 'red = OutputDevice(5)' test doesn't report Busy.

I don't have a Pi 5 so I can't really help further on that.

But I did note that you have multiple imports of 'shift_register'. Maybe one of those is trying to claim the GPIO which another one of those has already claimed ?

Code:

./webserver/main.py:8                           from shift_register import SRoutput./disposable_heroes/Menu/tab_menu_gui.py:7      import shift_register as SR./ctrl_hardware/teste.py:1                      import shift_register as SR

Statistics: Posted by Eddygrinder — Sun Dec 24, 2023 8:21 pm