Thanks. As soon as I posted here, I found this topic and with a bit of modification I was able to get it working. :)

Appreciated, thank you. I've merged those 2 PRs and tagged other users that might be interested Pi 4 compatibility/support.

@fraggle200 said in Cabinet Control Panel not detected on new clean image, via Pi2Jamma.: @mitu I installed Uinput by following a few links for the install but this method ultimately got me installed, just as a precaution it wasn't already there. https://www.raspberrypi.org/forums/viewtopic.php?t=221622 That's not needed, since PikeyD doesn't look like it uses python. There's - similarly - a Linux kernel module named uinput, that I think it's used, but it's loaded by default on a RetroPIe image (you can check /etc/modules).

It seems you do need to install something - see the manual: Once connected and booted up, you can navigate to the terminal to install the required gpio drivers. In RetroPie, you can do this by pressing the Ctrl-Alt and F4 key; this changes view to a virtual terminal window, which you can run ‘emulationstation’ to go back to RetroPie. ... It looks like you need to install GPIONext, a GPIO user driver to make the gamepad(s) work.

It's not python code but.. maybe could be useful for you. While ago - Using gpio and PWM - I did add some flash effects to every buttons on my bartop build. check out this video and you can find source code here. https://github.com/losernator/rainbowLED FYI My friend 'sana2dang' made original code for me and I just add little bit. Although I am not using this any more and moved to RGB effect using Aruino :) but worth trying

I see my problem now. When I first read the instructions on the link, I did not understand what he meant by "switching to hardware mode". At the time I did not have the joysticks and did not understand what that meant. Now I do. I'm going to do some more reading and then give it a try. Just a little nervous because this is a one-way ticket and I really don't feel like shelling out more for another control board if I screw it up. Thanks to those who read and responded. I love how active this forum is.

@gogangdong said in RPI4+GPIO acting strange: 4.5.13 The hardware was wired to the GPIO for the wiring of the mk_arcade_joystick_rpi and the mountains and joysticks, Sanwabuttons a,b,x,y,l,r,start, and select buttons to fit the GPIO and install 4.5.13 (https://files.retropie.org.uk/images/weekly/).B,Y,Other buttons on joystick did not work. mkarcadejoyystick 0.1.7 version(https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/supplementary/mkarcadejoystick.shSetup/blob/master/scriptmodules/supplementary/mkarcadejoystick.sh In the input setting of the retropie, say you found the GPIO controller and enter the keystroke (if you press Y, GPIO).They say they found the controller and enter the keystrokes. The joystick and other buttons do not work and the key setting sets the joystick to the top and B buttons, and the other buttons do not work.)

@mitu said in GPIO problem.: DL2 underneath to detect the joysticks Hi mitu and thank for your reply. I have installed also the latest retropie release but I have the same issue. I'll give a try to install SDL_jstest to see what it says. Thank you. Bye, Cri

@monkeybus I remember when Compute! published Turbotape, it was unbelievably fast. Here are the technical details for those interested. https://www.atarimagazines.com/compute/issue57/turbotape.html

@mitu There is no modification needed at all you can use multi-switch --generic command to offer an easy setup. @MaMikee Please install raspi-gpio at first with sudo apt install raspi-gpio command. There are tons of other possibilities available ;)

I would think you would want male to female, something like the below though not sure if there is anything specific to this cables pinout, as long as they are matched 1 to 1 then I assume it would work. Also the male end will hopefully fit over the Retrotink board pins. https://www.amazon.com/UCTRONICS-Breadboard-Connection-Raspberry-Display/dp/B07D991KMR The c64 was the greatest computer ever!

You can use a simple python script to catch GPIO input presses and translate them to volume change commands. Here is an example on how to do that - https://www.raspberrypi.org/forums/viewtopic.php?t=222763.

@kfleischmann This seems like a custom build - not something standard in a RetroPie installation. Check the onstart/onend script, they might have something to do with it - https://retropie.org.uk/docs/Runcommand/#runcommand-onstart-and-runcommand-onend-scripts.

@naughtjosh How did you connect the controller to the GPIOs ? Did you install any of the additional drivers needed for such setup - https://retropie.org.uk/docs/GPIO-Modules - ? Simply connecting a few wires to the GPIO pins is not enough. Ideas that don't require any downloads? Set-up your PI on a location where you have internet, just in case you'll need a driver to be downloaded or use your phone as a WiFi access point.

Sounds like retrogame isn't installed, or it isn't loading when booting, or isn't configured properly. If you open the terminal (press F4) and push your buttons and see if the corresponding letters appear. If you see no letters when moving the joystick or pushing buttons, then retrogame isn't working

As with the old controller, there's no 1:1 mapping between the cables/wires and the actual buttons - you can't wire it directly to the GPIO and expect it to automatically work, you'll need a driver. When you're talking about the 'new' NES controller, do you mean the one for the NES Classic Mini or the one for the Switch ? The controller for the NES Classic Mini has the same port type as a Wii (U) Classic controller - see here and here for details.

@pengu1n said in GPIO Controls Not Registering After Launching Games: [WARN] Input device ID 3 is unknown to this libretro implementation. Using RETRO _DEVICE_JOYPAD. That's because of the RA's configuration - try resetting the configuration to default by copying the retroarch.cfg.rp-dist files over the retroarch.cfg in the /opt/retropie/configs/all/ folder.