Freeplay CM3 GBA clone Kit.

[Dragu]

@Substring
And exactly when I was writing, I have some reactions on the GBA buttons ! Some wrong but it begins to work, yeah ! The apple is near.

[Dragu]

@Substring
@LumberJack
So, for the daily report. I have always the problem that I dont arrive to register my own gpio schematics in Recalbox. By chance vertical axe from standard Recalbox is the same in Freeplay, so this works. And with sdl2-jstest he show me :

Joystick Name:     'GPIO Controller 1'
Joystick Path:     '/dev/input/event2'
Joystick GUID:     15000000010000000100000000010000
Joystick Number:    0
Number of Axes:     2
Number of Buttons:  9
Number of Hats:     0
Number of B***s:    0
GameController:
  not a gamepad
Axis code  0:    0
Axis code  1:    1
Button code  0:   304
Button code  1:   305
Button code  2:   307
Button code  3:   308
Button code  4:   310
Button code  5:   311
Button code  6:   314
Button code  7:   315
Button code  8:   316

In /etc/modprobe.d I have mk_arcade_joystick,conf (and also under name mk_arcade_joystick_rpi.conf this line

options mk_arcade_joystick_rpi map=4 gpio=4,17,6,5,19,26,16,24,23,18,15,14,-20

But I dont arrive to register in /dev/input/js0.
Also if I indicate in recalbox.conf map=4, what should be legal after the github description

# ------------ D2 - GPIO Controllers ------------ #
## GPIO Controllers
## enable controllers on GPIO with mk_arcarde_joystick_rpi (0,1)
controllers.gpio.enabled=1
## mk_gpio arguments, map=1 for one controller, map=1,2 for 2 (map=1,map=1,2)
controllers.gpio.args=map=4

Recalbox dies with kernel panic, this should be an issue in Recalbox.
So, my only chance, I think, to redefine it under map=1. That's it for the moment.

[Substring]

@dragu said in Freeplay CM3 GBA clone Kit.:

map=4 gpio=4,17,6,5,19,26,16,24,23,18,15,14,-20

this is what you'd add in te line. But:

1. not yet handled
2. our KO doesn't handle custom mappings. this is why told you i'd compile one for you

[Dragu]

@Substring
Thanks, that is an answer. The problem, github is a horror of software version management, you dont find no old sources. In the Freeplay support files that are inside the .IMG release, I have the latest source versions from him also with hotkey modifications. If it could help you :
http://zclub.eu/Freeplayhome.7z

[Substring]

@dragu said in Freeplay CM3 GBA clone Kit.:

The problem, github is a horror of software version management

it's the best one ever, trust me. You just need ot learn how to use it.

Here is an upgraded hk version of the driver. Use map=5 gpio=4,17,6,5,19,26,16,24,23,18,15,14,20,-1

https://we.tl/hLeKAomdIy

[Dragu]

@Substring
So quick ? Thanks alot for your work, I will give feedback in short.
In between one picture from my testing place, Hub with keyboard and Wifi stick, HDMI mini to HDMI-HDMI to VGA adapter and power supply

[Substring]

@dragu sexy !

[Dragu]

@Substring
I am on the way to reload the system after the crash. Also concerning mk_arcade_joystick_rpi, there is some confusion about the file in /etc/modprobe.d
Described in github is mk_arcade_joystick.conf, but it seems that mk_arcade_joystick_rpi.conf is the good one, as what you read in the web. Logical, no ?

[Dragu]

@Substring
There is no crash anymore with map=5 in recalbox.conf. Concerning mk_arcade_joystick_rpi.ko, I tried out with both versions of the .conf file in /etc/modprobe.d, but evtest fails to find a controller.

[Substring]

@dragu check with lsmod if it's loaded + don't load it through recalbox.conf, it doesn't take all parameters. rmmod the ko, then manually modprobe it with your parameters

[Dragu]

@Substring
Hi friend, in lsmod the driver is not existing (was there before) and with modprobe I have following feedback

# # modprobe mk_arcade_joystick_rpi map=5
# modprobe: can't load module mk_arcade_joystick_rpi (extra/mk_arcade_joystick_rpi.ko): Invalid argument

[Dragu]

@Substring
Some more small info. If I put him map=1 (I suppose same with 1,2) in recalbox.conf, the driver is loaded correctly as with the version before and also same behavior.

[Substring]

@dragu have a look at /recalbox/scripts/recalbox-config.sh line 448 for loading the module and add your parameters

[Dragu]

@Substring
Hi, I just made some tests. So if I define in recalbox.conf map=5, he just dont load mk_arcade_joystick_rpi.ok and if I put there map=1, he load object but also with the standard gpio definition.
As you told I changed in recalbox-config.sh the following

if [ "$command" == "gpiocontrollers" ];then
    command="module"
    mode="load"
    extra1="mk_arcade_joystick_rpi"
    extra2="map=1,2"

to

if [ "$command" == "gpiocontrollers" ];then
    command="module"
    mode="load"
    extra1="mk_arcade_joystick_rpi map=5 gpio=4,17,6,5,19,26,16,24,23,18,15,14,20,-1"
    extra2="map=1,2"

I tried with and without map=5, but perhaps I made a mistake here ?
Anyway recalbox.conf seems to have bigger influence, as with map=5 there, he even dont load the object.

[Substring]

@dragu better summon @ian57 here, he made the tests with gpio remapping

[Dragu]

@Substring
@ian57 was last here 12 days ago, so I return to my cave
With PiGRRL the problem of the custom GPIO may also exist.

[Substring]

@dragu but i can get in touch with him almost whenever i want

[Dragu]

@Substring
I have the impression that this object dont accept arguments for map other as 1,2.
I am always somewhere astonished about in general software in Linux, as parameter files seems to be an acknowledged territory. I was about long time ago making with my team software for bigger companies, it was never software that had constant values inside that could at a certain moment change. By hardware or environnement.

[Dragu]

@Substring
Other thing on the schedule was the 3.2" waveshare tft screen, and this was a straight, because not necessary to use ED's driver, the waveshare32b.dtbo in /boot/overlays is working fine.

[Dragu]

Something else that I found out about this tiny waveshare displays, there are too much parameters in the description
If you just limit to the 3 not out commented, you have lcd screen + hdmi output all together, It seems to me that somebody was already asking this.

#Waveshare 3.2 TFT Screen
#same resolution for hdmi and tft
#hdmi_force_hotplug=1
#hdmi_group=2                
#hdmi_mode=1                 
#hdmi_mode=87                
hdmi_cvt=320 240 60 1 0 0 0
dtparam=spi=on              
dtoverlay=waveshare32b:rotate=270,speed=82000000,fps=60