Great job replacing the kernel driver with the device tree counterpart !

@Fenderus said in The mk-arcade-joystick-rpi in Raspberry Pi 3b 1.2 with 64-bit problem.:

Is there another way of installing both box-86 and wine in my current 32-bit configuration?

both box86 and wine can be installed with RetroPie-Extras

here are a few other post of what people have gotten to work and just other posts about box86
https://retropie.org.uk/forum/topic/29241/the-which-games-works-with-box86-wine-topic-on-the-retropie-rpi4-400?_=1726839031621

https://retropie.org.uk/forum/topic/28528/box86-and-wine-on-rpi4?_=1726839031629

https://retropie.org.uk/forum/topic/29388/guide-diy-wine-and-retropie-legacy-driver-raspberry-pi-3b?_=1726839031633

i personally cant help with box86 or wine, i have not used it at all other then booting it up once long ago. but hopefully this can help in someway

@Folly ouch, right: 6V is the maximum rating of the chip. 4.75 to 5.25 is the safe operating voltage (which is 5V +- 5%)

@Thorr69 could you elaborate on what file that would be? When I had used a 16gb USB, the romset I had totalled almost 16GB and it seemed to have been causing issues until I swapped to a larger capacity USB so I doubt it would have been a log file issue?

Got it working without the GPIO expander,

I used GPIO19 for the status pin, which really needs a 'regular' GPIO, not an I2C pin.

Then I used a gpio= statement in config.txt to set GPIO3 (which is an I2C pin) to low on bootup. GPIO3's then used as the shutdown pin for the PowerBlock.

This arrangement works fine.

@petrockblog -- perhaps the documentation could be updated to make clear that GPIOs with hardwired pullup resistors (such as the I2C pins) cannot be used as the status pin?

Thanks,
Chris

@lindsay said in GPIO Module Error - only runs on raspberry pi:

It may well be the case that I installed something outdated by accident, Python you think? I mean, the version of Python really shouldn't matter as long as it's 2.7 for python 2 and 3.5+ for python 3.

It's a bit more difficult to install Python itself and overwrite the system's installed one, I was thinking you might have installed an older version of the GPIO Python module, which might explain the error message.

@mitu Thanks! I will give it a go and get back to you :-)

Just tested if this project can be combined with LEDSpicer like this over here :
Syncing button leds with gameplay

It works !
But be aware of the danger, do not use the GPIO 24 and 25 in LEDSpicer when using both projects together.

You can't connect the joystick directly to the PI's GPIOs, you need an ADC chip in-between.
Take a look at https://grantwinney.com/connecting-an-analog-joystick-to-the-raspberry-pi-and-using-it-with-an-rgb-led-to-simulate-a-color-wheel/, which uses an MCP 3008 to connect a joystick to the PI.

Should be possible, why not ?
Use the GPIO inputs for simulating keyboard keys input and map them to the emulator's controls. For this bit you may need some additional configuration or scripts to interpret the GPIO pins state, but other than that there's just configuring the emulators' input for the actions you need.

Thanks guys, this was very helpful. I just ordered the
I-PAC2. =)

@douga Glad to hear that things are working for you now!

@mitu that was crazy fast, thank you! Just uncommented it and it actually worked. I thought it was being overriden by the one in [all] but I'm happy to be wrong.
Again, thank you!

Thank you. Now it's working!!!

I add this rule to

/etc/udev/rules.d/99-input.rules

SUBSYSTEM=="input", ATTRS{name}=="button*", MODE="0660", ENV{ID_INPUT_KEY}="1", ENV{ID_INPUT_KEYBOARD}="1"

And now have GPIO key ID_INPUT_KEYBOARD parameter too.

pi@retropie:~ $ udevadm info --query all /dev/input/event1 P: /devices/platform/button@1a/input/input1/event1 N: input/event1 L: 0 S: input/by-path/platform-button@1a-event E: DEVPATH=/devices/platform/button@1a/input/input1/event1 E: DEVNAME=/dev/input/event1 E: MAJOR=13 E: MINOR=65 E: SUBSYSTEM=input E: USEC_INITIALIZED=28281822 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=platform-button@1a E: ID_PATH_TAG=platform-button_1a E: LIBINPUT_DEVICE_GROUP=19/1/1:gpio-keys E: ID_INPUT_KEYBOARD=1 E: DEVLINKS=/dev/input/by-path/platform-button@1a-event E: TAGS=:power-switch:

Bidding hotkey to GPIO key is now working.

@buzz thank you for your response and sorry for posting on wrong forum. Cheers !

@craggus2000 Thanks for reporting back. Have fun. Please edit your first post and add in the something like [solved], so it is more likely to be picked up by search engines.

Your question made me updating my hint from last year on that topic.