GPIO Controls causing Pi to lock up
Posted: Sun Aug 25, 2019 11:19 am
.
man, i hope someone else has had this happen. i haven't been able to find anything online anywhere around it. (always fun to try researching something, only to find that you seem to be the only person this is happening to...)
In short.. when using GPIO-based controls (Retrogame overlay), pressing certain buttons causes the Pi to stutter and/or lock up. If no button is pressed, everything seems to just keep running fine, but pressing (certain) buttons causes the stutter, and mashing the buttons enough, and holding them, can cause it to just lock up completely until the buttons are released, then its back to normal.
This is driving me a little crazy... This is the third GBZ this has happened on, and I can't for the life of me figure out what is causing this issue. The first two times I finally just gave up and put a microcontroller and usb hub in the build to do the controls, but i'd really like to figure out what is causing this and fix it.
It seems to be the face buttons on the common ground button board that typically cause it. I don't think it's happened with L1/R1 or a hotkey. But, at least a couple directions on the D-pad as well as at least two or so of the A/B/X/Y buttons do seem to do it. It doesn't seem like all of them do it though.
things that didn't work...
I've tried moving the button inputs that seem to be causing it to different GPIO pins. I've tried using different, or thicker, wires on those inputs from the board, and/or the ground connection. I've cleaned the pads and board with alcohol. I've swapped out the silicone pads with different ones, and "premium" ones. I've swapped out the button board completely with a totally different one - even one from a completely different manufacturer / design.
i have had plenty of success doing GPIO controls, so (i think) i know the basics at least. it seems like a hardware issue, but i'm not really doing anything different from when i've had it working, and i don't know what else to test/try/check. nothing seems to be bridged. i've also tried other software like GPIONext and OneForAll in the past, but when i am able to get that other software working it didn't solve it. i haven't tried different software yet on this latest one.
other build notes...
the first one this happened on was using an SPI ili9341 screen, but the two more recent ones were using composite screens, so that does not seem to be related (the first time, i thought it might have been messing with the SPI bus).
For audio, they are all over the map - one was PWM, one was i2C, and one was USB audio.
They all had an ADS-1x15 hooked up to SDA/SCL, running something like hoolyhoo's battery monitor script, but disabling it has no effect.
software-wise, i think that i've tried Retropie 4.3, 4.4, and 4.5 and they all seem to have the issue. i usually do most of my testing with super mario bros (nes) and super mario kart (snes). there isn't any other software loaded, and i'm not doing anything unusual in any other settings anywhere.
any suggestions on other things to try are welcome. if someone wants to see it happening, i can upload a video too.
thanks
.
.
man, i hope someone else has had this happen. i haven't been able to find anything online anywhere around it. (always fun to try researching something, only to find that you seem to be the only person this is happening to...)
In short.. when using GPIO-based controls (Retrogame overlay), pressing certain buttons causes the Pi to stutter and/or lock up. If no button is pressed, everything seems to just keep running fine, but pressing (certain) buttons causes the stutter, and mashing the buttons enough, and holding them, can cause it to just lock up completely until the buttons are released, then its back to normal.
This is driving me a little crazy... This is the third GBZ this has happened on, and I can't for the life of me figure out what is causing this issue. The first two times I finally just gave up and put a microcontroller and usb hub in the build to do the controls, but i'd really like to figure out what is causing this and fix it.
It seems to be the face buttons on the common ground button board that typically cause it. I don't think it's happened with L1/R1 or a hotkey. But, at least a couple directions on the D-pad as well as at least two or so of the A/B/X/Y buttons do seem to do it. It doesn't seem like all of them do it though.
things that didn't work...
I've tried moving the button inputs that seem to be causing it to different GPIO pins. I've tried using different, or thicker, wires on those inputs from the board, and/or the ground connection. I've cleaned the pads and board with alcohol. I've swapped out the silicone pads with different ones, and "premium" ones. I've swapped out the button board completely with a totally different one - even one from a completely different manufacturer / design.
i have had plenty of success doing GPIO controls, so (i think) i know the basics at least. it seems like a hardware issue, but i'm not really doing anything different from when i've had it working, and i don't know what else to test/try/check. nothing seems to be bridged. i've also tried other software like GPIONext and OneForAll in the past, but when i am able to get that other software working it didn't solve it. i haven't tried different software yet on this latest one.
other build notes...
the first one this happened on was using an SPI ili9341 screen, but the two more recent ones were using composite screens, so that does not seem to be related (the first time, i thought it might have been messing with the SPI bus).
For audio, they are all over the map - one was PWM, one was i2C, and one was USB audio.
They all had an ADS-1x15 hooked up to SDA/SCL, running something like hoolyhoo's battery monitor script, but disabling it has no effect.
software-wise, i think that i've tried Retropie 4.3, 4.4, and 4.5 and they all seem to have the issue. i usually do most of my testing with super mario bros (nes) and super mario kart (snes). there isn't any other software loaded, and i'm not doing anything unusual in any other settings anywhere.
any suggestions on other things to try are welcome. if someone wants to see it happening, i can upload a video too.
thanks
.
.