I think I screwed something up on the pre-made retroie image. Because I re-flashed the pi and set I2C to be loaded through sudo raspi-config, now when I reboot it does detect my I2C. One step closer to my mobile retropie!

@krullbeast said in can udev read i2c and hardwired GPIO buttons simultaneously?:

do you think it is possible to read the i2c data and also the A and B buttons inside of retroarch?

Not an expert on this, but I think RetroArch doesn't read directly from GPIO (I2C or otherwise), instead it uses an established input driver (udev/sdl/etc.) - https://github.com/libretro/RetroArch/tree/master/input/drivers.

Revision 1.1 of the PowerBlock (introduced last year) provides break out pins for all needed signals. There is a brief blog post about it at https://blog.petrockblock.com/2016/05/20/new-revision-of-the-powerblock-increased-flexibility/. Maybe that gives some more insights.

Ok so I didn't give up so to speak but I did take a different route, I now have a ATXraspi sorting out my power button which leaves my i2c pins freed up. I have connected my 16x2 display as per the guide I've been following but when I check the i2c address there is no assigned address can anyone help me? Thanks. (there is power to the display but no text)
0_1500238054014_bc.JPG

Awesome build. Always was a fan of the fat ps2. Mine still works!

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