I just wanted to update this post as I fixed the issue. I had installed the Adafruit-Retrogame manually and forgot to add the rules (see end of this guide https://github.com/adafruit/Adafruit-Retrogame)

now it's working, hope this helps fix similar issues.

This should help:

https://www.reddit.com/r/raspberry_pi/comments/2wgty6/how_do_i_connect_a_ps2_controller_directly_to_the/

You need to reverse that. Most fans are going to need 5v to run. You can also use the 3.3v pin (pin escapes me right now), to run fans quieter, but those are the pins to run fans on for the pi. Also recommended are heatsinks for all of the sensitive chips (including the one on the bottom of the board). Use pins 2 and 9 for the power switch but not recommended for corrupting the sd card. I got one of the push button switches that connect to the micro usb port in between the pi and the power supply. It will also clean up your power feed.

Actually looking at the Mausberry, it says it uses pins 23 and 24. Im no genius with schematics, but those pins above look to be dead considering they are X'ed out. Worth looking into, but even still you better be comfortable with soldering because the vga666 doesn't have exposed pins so you'll probably have to solder the mausberry wires to the pin bases on top of the vga hat

@Capt_MorganCreek Hey!
Thank you very much for the file and the Help!
I had to change a little bit in the Script and use now uinput from uinput.
I ran into Problems with Dependencies... basically I haven't read thoroughly enough...
Everything else in the Script is the same.
Software works and the Buttons also... but! I have to make a new Plan on the Hardware itself.
It turned out that the Way I wantet to build the entire Thing does not work. It just does not fit...
Will have to see when I will have enough Time again to make a new Plan...

Big Thanks for the Help!

it's ok, actualy the fact it's a single c file makes it easier to read
and is a good start for me if I want to tweak or so

I just found ridiculous to use bluetooth while the controller and the pi are in the same box
like most people do (and writing python cos they are too lazy)

you gave a great option to dig in :-)

It was a network problem. I got it to run the commands, but on reboot it doesn't display to the screen.

@Jofo well, being that I now have several versions of the PSX bus reader, I can talk about my results with all versions.

The original version of the driver, even with the Select button filtered, definitely had sporadic issues with input glitches. My updated version was nearly perfect after filtering the Select button. I'm pretty sure the Acknowledgement line implementation is what did it. I'm pretty confident in that one.

However, the Arduino reader is 100% perfect. So far I've needed no filtering, it all just works. I need to work on the CPU usage of the driver though, still, but for what it's worth, it should work on the Pi. Just plug the Arduino in with USB.

https://www.adafruit.com/products/2223

I think you could use that and just not use the extra pins.

From the RetroPie-Setup I uninstalled unnecessary components -- remove WolfRam, SonicPi, etc. Nothing more than a boot to emulator, so I figured I would get some clutter out of the way.

I then went back to trying to different gamepad configurations through the driver config file. I enabled all four ports and through sheer dumb luck GPIO7 (gamepad4) started reading. I still cannot get GPIO2 / GPIO3 to read the data from the controller, but I have two working NES controllers right now!

I also tweaked the /opt/retroarch/configs/all/retroarch.cfg

There is a setting for joypad input scan cycle -- something along those lines -- that I opted to put at a value of 0 (I am trying to recall this from memory as the NES is now wrapped under the tree for dad) so that it would update controller state on demand. It was defaulted to 2 and the notes in the file were about adjustments for latency issues.

I also had to copy the configuration for player1_input* and update it for player2 within /opt/retroarch/configs/all/retroarch.cfg.

Also removed the override line from /opt/retroarch/configs/nes/retroarch.cfg

Still no idea why I cannot access GPIO3 / GPIO2 -- if anyone has any troubleshooting ideas I would be happy to jump through the hoops. I have the other SD card and another Pi3 at home I can run through.

You could adapt the driver according to your needs. As far as I understand you would need to adapt the classes DigitalIn and/or DigitalOut, see https://github.com/petrockblog/ControlBlockService2/tree/master/src/controlblock/hal.

Well this is what happens when you realize Retropie doesn't yet support direct I2C connections.

Re-attached half of a nunchuck cable, going the Bluetooth route as it seems that's the only way to connect a Wii controller+accessory to Retropie.

alt text

Thank you. Very interesting. Let me consolidate and see which best method to take.