Sellect Button Dont Work in GPIO

lokize

Hi, I have a bartop with two GPIO controls, I managed to make both work, but in both the SELECT key does not work, the other buttons work perfectly, how to solve this problem?

mitu

Please provide the information requested in https://retropie.org.uk/forum/topic/3/read-this-first when opening a support topic.

simonster

There any number of reasons for this, please complete the information requested in the read this first and include how your GPIO is connected and what driver you are using.

lokize

Pi Model or other hardware: RPI 3 B
Power Supply used: 5V
RetroPie Version Used : 4.4
Built From: Retropie Official Image
USB Devices connected: None
Controller used: Two GPIO Devices
Error messages received: no error message
Log found in /dev/shm/runcommand.log (if relevant): none
Guide used: (Mention if you followed a guide): none
File: (File with issue - with FULL path): none
Emulator: (Name of emulator - if applicable) : ALL EMULATORS
Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS): I think is no necessary
How to replicate the problem: My Select key of all GPIO not work with retropie...

mitu

You should test if the button press is registered in Linux and it's not a wiring problem. You can use jstest from the command line to do that - https://retropie.org.uk/docs/RetroArch-Configuration/#determining-button-values.

lokize

@mitu said in Sellect Button Dont Work in GPIO:

jstest

0_1537222397912_a63cd268-bee1-4753-b776-f980f5b43361-image.png

my select button in two controllers dont work

mitu

@lokize said in Sellect Button Dont Work in GPIO:

my select button in two controllers dont work

This means that the signal doesn't get through the GPIO or the driver doesn't see it, so there's no chance it would work. How did you connect the buttons to the GPIO pins and what driver do you use for it ?

lokize

@mitu said in Sellect Button Dont Work in GPIO:

This means that the signal doesn't get through the GPIO or the driver doesn't see it, so there's no chance it would work. How did you connect the buttons to the GPIO pins and what driver do you use for it ?

thanks for the help, I already bought the bartop connected and I'm using mk_arcade_joystick_rpi but in the recalbox the commands worked perfectly and I can not understand why, I changed to retropie because I like it more, but only the select does not work and I do not know what to do ... I'm going to take a picture of the pins and put them here.

mitu

@lokize The mk_arcade_joystick_rpi module has some parameters to map the GPIO pins to buttons. Most likely it does not map your select button to an input - how did you configure the driver ? The docs over at https://github.com/recalbox/mk_arcade_joystick_rpi, see the Loading the driver section, explain how you configure the driver to match your controller.

lokize

@mitu i installed in retropie menu

lokize

I noticed a strange thing when configuring the emulation station the commands they get like this

<inputConfig type="joystick" deviceName="GPIO Controller 1" deviceGUID="15000000010000000100000000010000">
    <input name="pageup" type="button" id="6" value="1"/>
    <input name="start" type="button" id="11" value="1"/>
    <input name="select" type="button" id="14" value="1"/>
    <input name="down" type="axis" id="1" value="1"/>
    <input name="pagedown" type="button" id="7" value="1"/>
    <input name="right" type="axis" id="0" value="1"/>
    <input name="left" type="axis" id="0" value="-1"/>
    <input name="up" type="axis" id="1" value="-1"/>
    <input name="a" type="button" id="1" value="1"/>
    <input name="b" type="button" id="0" value="1"/>
    <input name="x" type="button" id="3" value="1"/>
    <input name="y" type="button" id="4" value="1"/>
  </inputConfig>

but in evtest show this:


Input driver version is 1.0.1
Input device ID: bus 0x15 vendor 0x1 product 0x1 version 0x100
Input device name: "GPIO Controller 1"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 304 (BTN_SOUTH)
    Event code 305 (BTN_EAST)
    Event code 306 (BTN_C)
    Event code 307 (BTN_NORTH)
    Event code 308 (BTN_WEST)
    Event code 309 (BTN_Z)
    Event code 310 (BTN_TL)
    Event code 311 (BTN_TR)
    Event code 312 (BTN_TL2)
    Event code 313 (BTN_TR2)
    Event code 314 (BTN_SELECT)
    Event code 315 (BTN_START)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min       -1
      Max        1
    Event code 1 (ABS_Y)
      Value      0
      Min       -1
      Max        1
Properties:

but if I set the select on button 314 and start on 315 both do not work, but in the reicast settings they work, can anyone explain to me why?

Thanks!

mitu

@lokize said in Sellect Button Dont Work in GPIO:

but if I set the select on button 314 and start on 315 both do not work, but in the reicast settings they work, can anyone explain to me why?

Where exactly are you setting those buttons values - which file ? The ES input.cfg is specific to the application and it doesn't necessarily have the same values reported by jstest or seen by the emulator. You should look in the /opt/retropie/configs/all/retroarch-joypads folder, were you should have a file called GPIO Controller 1.cfg with the button numbers as reported by evdev.
I haven't used evdev, but it seems it to just report what it was detect, but until you actually press the buttons to see the values reported (a la jstest), I'm not sure how accurate it is.

Does jstest shows something when you press Select ?

lokize

@mitu no