Glad I could help!

Was wondering what wire size it was on your board. Looked thin and neat.

Hi. I use wire wrapping wire or 30awg insulated for this sort of board. Great for packing a lot of connections into a small space.

@@BytesNBits Thanks a lot. I love your work!

Glad I could help!

Great! I hope you get it all working OK.

Hi. Great to hear you got it working.

Thanks. Have fun playing all those games!

Glad it was helpful!

Hi. Getting there with all the parts. Sound and battery management to come.

Hi Richard. Thanks for the solution on getting the code working with the latest versions of Retropie.

@@BytesNBits Thank you. If I can help with anything else, please let me know.

@@rdean1972 Great. Will do!

@@rdean1972 It says Failed to add edge detection when I open the config-manager

You're welcome!

@@BytesNBits Hi! There is a way to install raspberry pi OS AND retropie inside, that could be controlled by gpio controller with GpioNext?

Great. Glad it helped.

Thank you very much.

This is just a standard SPI screen, but not using a parallel interface (multiple data lines).

Glad you enjoyed it!

Happy to help

You're welcome!

Glad it was helpful!

Hi. The GPIONext package does support a good range of inputs but you'll need to look at expanding your IO pin count to get what you're after. Have a look at the cocumentation as I think it covers using I2C IO expanders.

I used an ESP32 as a bluetooth keyboard in this video - kzfaq.info/get/bejne/eNGWoKWcm7XJgYE.html. The basic principle is the same. You just need to find the bluetooth definitions for the game controller interface. The library I use in the video has a game controller library by the same developer.

Yes, you are right.

Try this one - kzfaq.info/get/bejne/q-BkpsRjmamYl58.htmlsi=hmvQJaFXi8hARQR4

I'd start by disconnecting the gamepad and starting up the RPi. If the scrolling continues you've got a software setup issue. If the scrolling only happens when the controller is wired in it's probably a wiring error. Try connecting the inputs one at a time to find when the error happens. Good luck.

I think I used ground and set the GPIO input to use the inbuilt pull up resistor.

no problem!

I don't think gpionext supports two gamepads. I guess there aren't enough io pins.

It's worth clearing any special functions for these pins just to make sure. If GPIONext still can't use them check for other drivers taking control of the pins.

The setup should work with any Raspberry Pi model. Good luck with the arcade cabinet.

Hi. Yes. 0V and ground are the same on the Pi.

@@BytesNBits thank you so much!

Can you remap those functions to other GPIO pins?

You'd need to break down the circuit yourself. It's basically some buttons connecting the GPIO pins to ground.

GPIO next allows you to map gpio pins to pretty much any input button on the computer. in the list you pointed out I think you map buttons to mimic keyboard keys. I haven't looked in the commands menu but just select it and it will give you some options. So yes, you can wire in extra buttons and map those to keys or other buttons. Then in Retropie set those as your hotkeys.

Great. Have fun. I'll have to do a sound video at some point.

Hi. The prototype board I use is matrix board where every hole/pin has a single solder pad. I simply wire from pin to pin with very fine solid core wire (or use wire wrapping wire). It's very old school but easy to get things up and running quickly and in a small space.

The GPIO setup I use is purely digital inputs.

It should do. I'm not sure how the GPIONext identifies itself to the OS so that you can reliably map your 2 controllers. You'd need to have a play around with the game controller settings.

Hi. I'm using a fairly generic ILI9341 driver based SPI lcd panel. It's using the standard SPI interface rather than an extended parallel data line version.

You'd need to check the driver documentation to see how many inputs it supports. It should be a matter of connecting up the extra buttons and mapping them into the code.

Hi. Yes, not all the through hole components fit directly onto the proto board. You might need to drill out a few holes. I use double sided protoboard with solder pads both sides and through hole plating. This lets me solder top side if the component doesn't fit. It's really a matter of doing the best you can to get the circuit complete.

@@BytesNBits thanks! So as long as things are connected properly, the "condition" of the existing or new holes doesnt matter as i understand :)

Hi. I'm not sure what the problem might be, I haven't seen that one before. It might be that something else on the Pi is conflicting with the packages. Is this a fresh install of RetroPie. Have you added any other packages?

@@BytesNBits Ah I see, okay no worries. I formatted the memory card and redid all the steps and this time it works! Not sure what changed :-S Thanks very much for the help though!

I haven't checked it the driver supports haptic outputs. You'd need to have a look in the documentation. If it does I guess you'd just need to connect the motor to a GPIO pin, maybe with a simple current amplifier.

Yes. The joystick is simply 4 micro switches in a neat little unit.

Hi. You need to design an printed circuit board to connect all the bits together in a small package. It's another project on the list of videos I want to make.

It is very thin solid core. The label has come off the reels so I don't know the actual guage. It's basically wire wrapping wire but with a thin plastic covering.

Hi. Try connecting these non working buttons to two of the working GPIO pins. This will confirm if it's the wiring or the software. If they work you can try mapping the buttons to different GPIO pins. There might be some other setup in your RPi that's interfering with these IO pins.

make sure you've added the button in GPIONext and then remap the controller in RetroPie

Thank you, that really helps. I had another question though. The thing is that retro pie does not occupy my entire display (5inch lcd), and I was wondering how I could fix that. I tried changing the resolution but it didn’t work.

nvm i figured it out, you type gpionext config in the terminal. This vid is super helpful its perfect for what im working on!

Hi. Great to hear you got it sorted. Glad the video is useful.

Hi. You'll not be able to connect this sort of controller layout directly to the Raspberry Pi. You'll need to make/buy a game controller circuit which you can connect via the USB port. Have a look at create.arduino.cc/projecthub/361085/arduino-game-controller-f3ffec.

Yes. It should work fine without changing anything.

Hi. Each switch is simply used to connect the GPIO pin to ground. I use the internal pull up resistors on the Raspberry Pi so we don't need external components. On the actual board I simply connect one side of each switch to a common ground from the RPi, and then take the other side of each switch to the GPIO pins. I hope this helps.

@@BytesNBits Yes! After thinking about it I thought that’s what you did but thanks for confirming.

It sounds like you've got it all designed correctly. I'd start by checking the pin voltages when you move in a single direction and then in a diagonal. It might be some sort of short circuit that's pulling the pins low when more than one switch is closed.

@@BytesNBits Hmm, I haven't thought about that. Thanks for your help, I'll go check it out.

This is just a basic controller setup. You can get into and out of games to play your collection. You need to map hotkeys

To the buttons on the controller, or combinations.

Hi. I've seen a few virtual gamepad projects which might do what you want. Have a look on Google. Otherwise you'll have to code something yourself. Hope this helps.

Yes. It should work on all Pi models.

@@BytesNBits thanks for the reply, can you please help me more by providing few info 1. I am getting raspberry pi zero 2w for cheap hence I want to make a bartop arcade machine where most of my games will be neogeo ,mame, snes ,sega Saturn . How will it perform on a 15 inch 768p reso screen. 2. Can we use remaining gpio fo player 2 configuration? If not then I have a gamepad made from raspberry pi pico will it be detected as a controller for retropie for 2nd player configuration?

I don't remember seeing that function but do check the documentation. It's a while since I've used it now.

Hi. If you're using the Libretro cores through Retroarch you probably need to map the buttons in there. Launch a game and press Select + X. This should bring up the RetroArch menu. Find the input settings and there should be an option for mapping the controllers (I can't remember exactly where it is). If you go through that it should let you tally up Retroarch with the controller buttons. Then in Mame you need to press the Tab key on the keyboard (there's probably a key combination as well) to get to the Mame key mappings. If you set the general inputs this will be the default for most games. You can the modify individual ones from there. I hope this helps.

@@BytesNBits thank you for your detailed advice and fast reply! I will follow your suggestions, it's so close to working now 😃

I haven't tried it but I think it should work. The GPIO software seems to create a virtual controller that should be picked up by the OS. Only one way to find out!

Does your display use an SPI connection? Quite often the connector covers a large block of pins but is only using a few of the GPIO connections. The others are just not connected but covered by the header. If you get the pinout for the screen connector you can use jump wires to connect it to the RPi and then gain access to the unused pins.

@@BytesNBits Yes my display uses a SPI connection. According to its documentation there are some free pins. I'll those. Thanks for the help!

@@BytesNBits I just tried it out using jumper wire. The display powers up but doesn't show anything. It's just a white screen. I'm using the fbcp-ili9341 driver on my display. Do I need to tweak any of the driver settings?

@@safwansadad6488 If you've used jump wires for all the connections you should be fine. Don't forget the power connections! All you are doing is extending the pins. Make sure the connections are good and that you've not missed any pins. Try not to use overly long wires. If all else fails try reducing the connection data speed. If that fixes it you've got some sort of noise issue. Again check connections and wire length. Just to check - was it all working when connected directly to the Pi?

Should do. Although the video is now a bit old so not sure if the drivers are still compatible.

@@BytesNBits thanks and respect for still answering questions 2 years later

It definitely works with RetroArch and should work with any other software.

Hi. gpionext has some options to tell it what buttons it's allowed to use. Usually it assumes it can use everything but it might be getting overridden somewhere. Have a look at this video kzfaq.info/get/bejne/j9d2Zr1hpqfSeY0.html. I was getting the sound output messing with the gpionext functions. Hope it helps.

@@BytesNBits that could be it. I have an awful set up using pwm audio from one of the gpio pins and and the spi display connection. I ended up writing my own script to simulate keyboard presses when buttons are pressed and that works for me

I think you can configure as many pins as are available. Unfortuately just one button per pin.

@@BytesNBitsUpdate. It ended up working, and all my buttons are working. But for some reason when I try and hook up my thumbstick, it only detects "up", and "right". (This is for my arudino thumbstick, and a custom one I wired myself)

Hi. The controller is just a number of pushbuttons soldered on to a piece of veroboard. I've wired in a common connection to one side of every switch and then taken the other side of every switch to a flying lead. This lets me connect either 5V or 0V to the common side so I can either pull up or pull down an input pin on the Raspberry Pi. For this project I used a 0V common to pull down the RPi GPIO pins. I hope this helps you out.

I 3D printed it.

@@BytesNBits That’s awesome! Would you mind sharing the stl file? I am making a controller for my high school engineering project.

@@graceb5539 I don't think I bothered to save the design. It's simply a sphere. Cut off the bottom section. Then cut out a cuboid on the flattened surface to fit your joystick stub.

I think the gpionext library only supports one button per input

@@BytesNBits that's sad its hard to put all buttons and display at the same time using gpio pins

Hi. Yes. You could create a full X box style controller that way. Use the Pico to read all the joysticks and buttons and then use the USB connection to the RPi to set it up as a standard game controller. I'm sure there's a tutorial out there on how to do it.

have you tried booting the RPi with a clean OS to verify if the GPIO is really damaged. the software shouldn't be able to damage the circuitry.

@@BytesNBits yes i did it and reinstalled the gpionext software but it still can't recognise the buttons attached to the gpio

@@BytesNBits how can i know if the gpio is broken?

They work like any other button.

Hi. It should show up as a standard game controller. It's not specific to RetroPie.

There will always be some delay as the button presses are picked up by one block of code before being passed to the main OS. I wasn't able to detect it when using it for games.

@@BytesNBits right the answer i was waiting for. thanks!

I haven't tried it but I don't see why they wouldn't work. Give it a go!

@@BytesNBits :D thanks!

You can use whatever works best for you. As long as the connections are all correct it doesn't matter.

@@BytesNBits Thank you sir for your information.

Hi. I'm not sure what that might be. Make sure you've run a full update on your Pi and RetroArch installations and then try re installing the GPIONext code.

@@BytesNBits Ok i found the error :) My LCD-Display took some GPIO pins. But now I have another error. When I type in gpionext start and reboot, retropie says that it found no Game-Pads.

@@BytesNBits You mentioned RetroArch. I haven't istalled RetroArch.

@@dark_phoenix_9537 RetroPie is a front end package that uses RetroArch in the background to do the actual emulation. Can you run the GPIONext config routine and does it recognise your buttons? If you then run RetroPie without a reboot does it see the controller?

@@BytesNBits The problem is the LCD-Display, because when I run the RP whitout tftdisplay installed, it recognises the GPIOnext controller.

Try running install.sh again. If it's still not working, execute the command: "sudo pip3 install evdev (If you open install.sh in a text editor such as "nano", you can find that exact command)

Hi @Zeitiah Thanks for the tips on fixing this issue.

In my comment, I shared the solution for this exact problem. I ran updates for everything in the retropie_setup.sh. After I did this, I was able to install the GPIOnext and run the configurator without that error. Hope this helps.

You can use an I2C IO expander. I think GPIONext supports these but do check. I'll be using some on a future video to build a bluetooth game controller but that's a couple of months away.

@@BytesNBits okay :D

I think GPIONext supports I2C IO expanders. You'd need to use these to get that many inputs.

@@BytesNBits Do you know any pcb that has 20 buttons for 12C

Hi. Sound should be ready this weekend!

@@BytesNBits omg that makes me so happy to hear. Im doing this project and i really really need your tutorial ❤️❤️❤️

Hi. It took a bit of time to get it put together but the sound tutorial is now online. Let me know how you get on.

It looks like the evdev library (I don't know what it is) is missing a module or something. Try updating your Python. It might also be that that module has been taken out of the library. Try a search on Google.

@@BytesNBits Thank you. I looked around for a while and didn’t find anything. I ended up just reimaging my SD card and starting from scratch. Worked fine after reinstalling everything. Thank you for the help 🙏

Hi. I had a quick look and found this possible issue. www.raspberrypi.org/forums/viewtopic.php?t=205327 Check your pin assignments to make sure GPIONext isn't interfering, or being blocked by some other software. I also added a GPIONext fix video as I found it was interfering with my sound setup. Have a look at, kzfaq.info/get/bejne/j9d2Zr1hpqfSeY0.html You can limit the GPIO pins GPIONext has access to. I hope this helps.

@@BytesNBits thank you that helped me a lot