keyboard config OK button not working

auditor

Each time I boot the picade I am asked to map the buttons & keys. I go through all buttons and once at the end "OK" is highlighted, but no matter what button I push it doesn't save or go to the next step.
I can only go to F4 and enter cli.
I have updated retropie last night, and stil the same issue.
I can't find the file to map the keys manually.
Strangely enough, when I push the buttons on the picade one button registers as "Esc", another as "Alt".
Regardless, ENTER doesn't work when I get to the OK step.

My picade's specs:

pi 4 model B Rev 1.1
USB connected Device 001 Linux Foundation 3.0 root hub
device 003 Primax keyboard
device 002 VIA Labs, Inc HUB
device 001 Linux Foundation 2.0 root hub
bluetoothctl devices: none
Retropie version: 4.8.2, Last commit 1 year and 4 months ago (9dc632ae)
System rpi4 (armu71)running on raspbian Linux 10 buster

mitu

@auditor said in keyboard config OK button not working:

Each time I boot the picade I am asked to map the buttons & keys. I go through all buttons and once at the end "OK" is highlighted, but no matter what button I push it doesn't save or go to the next step.

Did you try pressing the button you've mapped as A ?

auditor

@mitu does nothing. I can only scroll up & down once I have set all key bindings. OK does not save

AwesomeKingClem

@auditor It probably isn't an issue with your button mapping, but rather retropie can't save the button mapping layout. Random guess. Can you change any mappings with A after you finish?

PiBoyyy

This post is deleted!

mitu

@PiBoyyy please don't copy/paste garbage from ChatGPT here.

mitu

@mitu does nothing. I can only scroll up & down once I have set all key bindings. OK does not save

Can you post the Picade configuration file from /boot/config.txt ? Which image did you use to install RetroPie ?

auditor

@mitu
sure, here is boot/config.txt

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details
 
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1
 
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1
 
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
 
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
 
# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1
 
# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1
 
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2
 
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4
 
# uncomment for composite PAL
#sdtv_mode=2
 
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
 
# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
 
# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18
 
# Additional overlays and parameters are documented /boot/overlays/README
 
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
 
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
 
[all]
#dtoverlay=vc4-fkms-v3d
overscan_scale=1
 
dtoverlay=picade
dtparam=audio=off

mitu

Try to 're-map' the picade buttons so no Esc/Alt and just regular keys are used. See this forum post for how to do that, modifying the same config.txt file (take a backup of the file before modifying it).

auditor

@mitu let me see if I understood you correctly:
I added it like this at the end of the file

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
overscan_scale=1

dtoverlay=picade
dtparam=button1=31
dtparam=button2=32
dtparam=button3=33
dtparam=button4=36
dtparam=button5=37
dtparam=button6=38
dtparam=enter=30
dtparam=escape=48
dtparam=audio=off

I tried it and it gave same error

I am inclined to re-install. I simply don't get what is causing it.
Can I just backup all my ROMS and do clean install, or will I be in for a real struggle?

mitu

I tried it and it gave same error

Ok.

I am inclined to re-install. I simply don't get what is causing it.

Don't see how that would help, but I'm not familiar with Picade's driver installation, so sure, why not ?

Can I just backup all my ROMS and do clean install, or will I be in for a real struggle?

Yes.

auditor

@mitu before I do the open-heart surgery, is this a Picade issue? Or a retropie issue you think?

mitu

@auditor neither and both - if the Picade default mapping is using Esc/Alt, this may inpact the EmulationStation input handling.
Anyway, nobody is forcing you to do 'open-heart surgery', a simple backup of the config.txt file before you do any modifications on it is enough to get you back to your initial state. Could be also faster than re-installing from scratch.

auditor

@mitu I am understanding better the more I am looking at the issue. Where can the bindings be mapped other than config.txt? Because each time I push one of the 6 "fire" buttons, one of them inevatbly is Esc .
It seems something is overriding the settings, or hard-coded somewhere

mitu

@auditor said in keyboard config OK button not working:

It seems something is overriding the settings, or hard-coded somewhere

I'm not familiar with the Picade's driver, as said before. How did you install it on the RetroPie system ? Does it have a script/repository where there might be some documentation ?

auditor

@mitu I installed it years ago - I honestly don't remember. It DID work. I put it in the cupboard and the kids found it again. And now it's sitting on my desk and every few days they look at it, poke it and say "have you fixed it yet"?

Is there a command I can use so I can find the answer to your question?

mitu

@auditor said in keyboard config OK button not working:

Is there a command I can use so I can find the answer to your question?

Not really.

If it worked before, what was changed since then - updates to the system or RetroPie ? Did it have a special image you installed or do you remember installing the picade driver ?

auditor

@mitu I only rememebr following the instructions that came with the box. But yes, I defintely ran all the updates.