Sorry, sometimes you are so absorbed in a problem that you overlook the simplest things. Maybe this has happened to you at some point - that does not always have anything to do with laziness.
Anyway, thank you for the hint.
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.
Two years ago I bought the Pimoroni Picade (1st version) Arcade cabinet. It's slighty bigger than the current, 2nd version, has a 800x600 pixel display and a Pimoroni Picade PCB extension board - and I got Recalbox running without any troubles.
A few weeks ago I replaced it with the Pimoroni Picade (2nd version) Arcade cabinet. It's slightly smaller than the old, 1st version, has a 1024x768 pixel display and a new Picade X Hat extension board - and I didn't get it running at all!
The reason why Recalbox on the new Picade does not work is because the "Picade X Hat" extension board needs to have a driver installed. That's no problem with RetroPie, but it's NOT an easy thing with Recalbox, if it is even possible.
So I thougth I simply order the old Picade PCB and replace the new Picade X Hat. But I learned that even with the Picade PCB installed, I didn't get Recalbox running, because I didn't get the controlls (joystick and buttons) configured.
So I contacted the friendly guys from Pimoroni; and they had the solution for me - and for everyone else!:
It's the firmware of the Picade PCB which is now (obviousely) newer then the firmware shipped with the PCB 2 years ago. But Pimoroni provides the previous firmware on it's Github channel.
As soon I flashed the firmware "picade_original.hex" to my Picade PCB, all troubles vanished. Now it's again possible to configure the joystick and controlls/buttons within the Recalbox configuration dialog wizard.
The Picade PCB is an Arduino compatible board and fully corresponds to an Arduino Leonardo (ATmega32U4 AVR). The provided firmware is in Intel Hex format (*.hex) and can be flashed with "avrdude" quite easily. You will need a avrdude supported programmer (like the AVRISPmkII). I'm not sure if it's possible to flash a *.hex file within the Arduino IDE to the board.
The guy from Pimoroni additionally mentioned that the other provided firmware "picade_gamepad.hex" should work as well, because this firmware emulates a standard gamepad. I've never tried out this solution, but if anybody does, let me know how it works!
I hope I could describe the way to get Recalbox running on a (every!) Picade. Excuse me bad english, it's not my native language.
If anybode needs additional help, please contact me.
Perfect - worked!
Is there a way to get the "missing" games quick afterwards - without new installation and without searching the ROMs elsewhere?
I've just updated my Recalbox from v7.0.1 to v7.1.1 - update worked fine.
But what I wonder; is an update within a major version (actually 7.x.x) really the same as a new installation from scratch?
In the release notes of v7.1.0 you can read:
"... Add 4 MAME games from the '80"
As expected, I didn't get this 4 MAME games through the update (at least in the MAME folder)? If I would do a fresh install - I would get it.
Am I wrong? If not; are there even more diffenrences between an update and a new install? Is that described somewhere?
Thanks a lot - Recalbox is great!
I've really not as much knowledge as much others here. But what I notice is, that MAME often raises questions. So do I have questions.
I very often read that Mame 0.78 is very old and somehow "outdated". I don't know. But if so, why does the Recalbox team stay on this "outdated" version? There may be for sure a reason, right?
In the Readme.txt file the the roms\mame folder one can read:
Recalbox is using libretro mame2003 as default core. So, compatible roms must come from a 0.78 mame romset Are also included in Recalbox: - libretro core mame2000: 0.37b5 mame romset - libretro core mame2010 (not available on rpi0/1): 0.139 mame romset - libretro core mame2015 0.160 mame romset - librerto core mame 0.219 mame romset - standalone emulator advancemame: 0.106 mame romset So, if you want to use a core different of the default one, you must edit your recalbox.conf file following instructions of this page: https://github.com/recalbox/recalbox-os/wiki/recalbox.conf-%28EN%29
But, for a beginner, that makes not everything clear at all, because the provided link how to change to a different core doesn't work anymore - probably due to the rebuild of the Wiki pages.
I know so far, that I can edit the recalbox.conf file to do this job. Probably I have to insert a statement like mame.core= but which value I have to assign for e.g. Mame 0.219 is not clear. As well as if I need to add further statements.
I researched really a lot how to alter the default Mame core - and did find only fragments of the whole part. I just don't know if I get any advantages at all if I use a newer Mame version? All together is somehow confusing.
Is anyone willing to clearify this Mame issue - not only for me, but for other beginners - and maybe in a language beginners can understand?
As I see, the Wiki pages have moved. But have they moved all?
For example, in the old Wiki, there was a detailed desciption how to connect Arcade controlls and buttons to the GPIO of the Raspberry.
Where ever I search in the new Wiki, the best I can find is this:
Where is this description gone?
Since I couldn't edit my previous post anymore, here an additional information.
The new BIOS check feature of Recalbox 7 itself doesn't complain about this "scph101.bin" file.
So it seams (for me) to be quite sure; this could/must be a bug.
Eventually, I got all BIOS files for Recalbox 7.0.1 - my BIOS library is 100 complet. But all of a sudden, I noticed that Recalbox complains on one, single BIOS - just since today!? The last time I checked the BIOS section, I sure all BIOS very complet and with correct MD5 checksum.
Look at my screenshot; it shows the MD5 checksum file of my "scph101.bin" file which I copied to the Recalbox. I've double checked it several times. The BIOS "scph101.bin" which I copied to the bios folder has for sure the same MD5 as requested - nevertheless Recalbox complains about the checksum???
I noticed that Recalbox displays every BIOS checksum in lower letters, except this one. Could it be, that Recalbox compairs the MD5 somehwo case sesitive?
Today, I noticed that I can't save states in Prboom (Doom) anymore? I get a yellow message in the left, lower corner "core does not support save states".
Some weeks ago this was working for sure. I think I'm crazy. What the hell did I do wrong?
Update: Sorry, I'm really getting old; it was Wolfenstein where I could save states...
I would like to delete this post, but it's too late.
Sorry again, my fault.