@epb7 you need to do a full shutdown, not a quick one

@paradadf said in Cannot upgrade version after a few months:

@rodri hi... it seems you‘ve missed our announcements and the fact that you can‘t upgrade from anything before version 6.0 (which is the current latest release). So you‘ll have to do a clean instsllation.

I thought something like that might have been the issue. Thanks!

@dam said in Cannot upgrade version after a few months:

Try to a new install, because the upgrade don´t work online.

Choose your hardware:

https://archive.recalbox.com/

Remember to backup your roms before to install a new version on sdcard to put again after.

Yes, thanks for the reminder, I have both the roms and the theme to backup. I was trying to avoid that, because everything is on the same SD card.

Hello @mrretro

I had to re-control everything, the wiring file had nothing to do with the received Xin-mo (commissioned in February 2019)!
I create my own file for.. do not forget!

@cheungbx Thanks for your description! Tried that with 4.4.13-v7and always receive a segmentation fault after this:

# rmmod mk_arcade_joystick_rpi # insmod /lib/modules/4.4.13-v7/extra/mk_arcade_joystick_rpi.ko map=4 gpio=5,4,14,22,13,18,21,16,6,20,26,12,18

Have a Pi 3b.

Any ideas?

Well, I've now a general procedure to get Recalbox running on a Pimoroni Picade.
Because I think this could be a valueable information, I decided to finish this thread and to open a new and fresh one. So nobody has to read through all the posts in this thread to come to the solution.

Changed engine core to pcsx_rearmed and it's fixed!

@aintmichael
There is still one option staying, to replace the dosbox version in the packages with an older one, working pretty well for me and that I use currently. As /usr/bin/dosbox
Older Dosbox version

reinstalled RecalBox without resizing and let the Pi and the system took care of it. Now there is a third "shared" Patition and everything saves persistently. Thanks for help. This issue is solved :)

I solved used Sixasis Pairing tool from Windows, i forced my "problematic" Shanwan to connect to Raspberry BT address.
Now i have the problem that all 2 shanwan copies are detected as "Playstation 3 original" , but i selected Shanwan drivers from configuration and i read that supports "original and shanwan" , so at the moment i cannot see any issue with this.

Recalbox is free and support is not expected to be given quickly, i just ask if somebody can shed light about where BT pairing informations are stored, why Shanwan copies are detected as Ps3 original and so on.

In the FAQ, in the tutorial we can add Sixasis Pairing tool way for problematic controller, i can give my availability to improve the community experience.

I also had other issues with Ps3 ORIGINAL pad (that now i use only with Android phone), this device often pressed buttons, never really pressed! Led often stay OFF, but pad was working (with ghost pressing issue).
I thought was a problem with pad, but with Android works like a charm, maybe if reoccurs with Shanwan units i should open another thread.

@xnet1986 you're welcome!

My bad... The config of my keyboard had just nothing to do with everything I could find on the web... It actually works.

Forget everything, just put your control closer to the raspberry Jejeje. You're welcome

@kabukibear

done
next time you can mark it also yourself :)
Topic Tools -> Ask a question + Topic Tools -> Mark as Solved

@joseph-portuondo It seems to me you are using batocera and not recalbox

Ok. I made it work now completely (including start and select buttons) by setting global.inputdriver=sdl2 in the config. Thus, this thread can be closed.

@gavsta depending on the romset you use, you put your roms in different folders. On different folders, the cores are also different. You must specify exactly which romset you are using and in what folder you are putting the rom, plus any relevant modification you might have done. Wirh incomplete info we can't help. Read the arcade wiki if you don't know what I'm talking about.