ARpiCADE_5 - for Pi4 or Pi5

[dee2eR]

Anyone have issue with SEGACD/MEGACD roms not loading? Have bios' in roms folder but game just goes back to game list like atomiswave was doing before the last update?

Turns out Attract-Mode is getting confused due to the bin+cue structure of these games. Seems handling 2 files with the same name and different extensions broke at some point (it used to work). It sends the .bin extension when it should be sending the .cue extension. Quick fix its to edit the segacd settings in Attract-Mode. While in the game select menu press either 'test' (cab) or 'tab' (keyboard) and navigate to: Emulators > segacd > Rom Extensions - then change it to read '.cue' (no quotes) - the other extensions there arn't needed for segacd.

Finally, if there are spaces in the filenames for this emulator it can cause it's own issues. If there are spaces in the filenames of the .cue files replace spaces with underscores, you don't need to do the .bin files... I mention it because on games without spaces in the filenames I was getting blackscreened, not just kicked back to the menu.

Let me know if that doesn't fix it for you, I tried a bunch of things before figuring that out and may have done some other bit that was needed.

EDIT: looks like Picodrive can now use chds too. That could be worth putting in the rom extensions too.

[dee2eR]

Well... odd. Now I am 2/3 with updating.

Let me explain... exactly the behavior.

The first time when it failed (above)... I then brought it back to the computer where it found errors via Paragon. I corrected the errors with paragon and it tested clean. It still crashed at the same spot... the loading screen.

I re-burned my sdmemory card. I then figured... screw it.. and I re-updated.

It did the exact same thing. It crashes to that white box eventually. The box seems to let you choose between two boxes... top or bottom.. but you can't really choose... it does nothing. I powered down. I powered up and this time it crashed at the intro screen... Uh... OK.

So I take the card to the PC and sure enough, errors are found... errors are corrected... then back to the cabinet...

I power up and... IT WORKS?!?

Picture looks NICE (oddly even better than before and it looked nice before)... and i love being able to see the console.

I have NO idea what is going on or why... but ultimately all is good.

Glad it worked out... have to ask though, did you press 'enter' when the pop up appeared, then wait a little and 'alt'+'f4' (possibly do both again) then big wait? The update takes while to reboot after it's run. Unless something unexpected is happening (and that IS possible) you powering down before it was finished probably caused the SD card partition issue.

If for some reason you need to run the update again remove these lines from update.sh and it shouldn't happen again:

wineserver
wine Dx4vbInstall.exe
wine vcredist8_FIF_x86.exe

[Hashman]

Anyone have issue with SEGACD/MEGACD roms not loading? Have bios' in roms folder but game just goes back to game list like atomiswave was doing before the last update?

Turns out Attract-Mode is getting confused due to the bin+cue structure of these games. Seems handling 2 files with the same name and different extensions broke at some point (it used to work). It sends the .bin extension when it should be sending the .cue extension. Quick fix its to edit the segacd settings in Attract-Mode. While in the game select menu press either 'test' (cab) or 'tab' (keyboard) and navigate to: Emulators > segacd > Rom Extensions - then change it to read '.cue' (no quotes) - the other extensions there arn't needed for segacd.

Finally, if there are spaces in the filenames for this emulator it can cause it's own issues. If there are spaces in the filenames of the .cue files replace spaces with underscores, you don't need to do the .bin files... I mention it because on games without spaces in the filenames I was getting blackscreened, not just kicked back to the menu.

Let me know if that doesn't fix it for you, I tried a bunch of things before figuring that out and may have done some other bit that was needed.

EDIT: looks like Picodrive can now use chds too. That could be worth putting in the rom extensions too.

Thanks mate. I'll take a took. My segacd roms are in .chd format.

[dee2eR]

nice one, chds work great with sega cd, testing some now. Just make sure no spaces in the file names.

EDIT: chds work great for CD/GDi images in general and save heaps of space. DC, PSX etc. going to try to figure out why PC Engine CD is playing up now... edit: I had spaces in the filename, PCECD also works fine with chd.

[Hashman]

nice one, chds work great with sega cd, testing some now. Just make sure no spaces in the file names.

EDIT: chds work great for CD/GDi images in general and save heaps of space. DC, PSX etc. going to try to figure out why PC Engine CD is playing up now... edit: I had spaces in the filename, PCECD also works fine with chd.

removed the other extensions and just put in .chd and now theyre working!

for some reason just adding .chd to the list didnt work.

Still having issue with the pi5 not starting on boot on now TWO different arcade machines. The 5v is around 5.1v and ive tried adjust either way. Worked once on one the machines then second power on it didnt. If i push the little reset button on pi5 it fires up.

Nice and big jamma wiring too. I'm having a look at this site here to see if it can help https://forums.raspberrypi.com/viewtopic.php?t=364720

[dee2eR]

nice one, chds work great with sega cd, testing some now. Just make sure no spaces in the file names.

EDIT: chds work great for CD/GDi images in general and save heaps of space. DC, PSX etc. going to try to figure out why PC Engine CD is playing up now... edit: I had spaces in the filename, PCECD also works fine with chd.

removed the other extensions and just put in .chd and now theyre working!

for some reason just adding .chd to the list didnt work.

Still having issue with the pi5 not starting on boot on now TWO different arcade machines. The 5v is around 5.1v and ive tried adjust either way. Worked once on one the machines then second power on it didnt. If i push the little reset button on pi5 it fires up.

Nice and big jamma wiring too. I'm having a look at this site here to see if it can help https://forums.raspberrypi.com/viewtopic.php?t=364720

From that link you could try adding:
usb_max_current_enable=1
to config.txt. I'm going to eat some food, will have a play with that setting myself in the next day or two if you don't try it aand report back.

[Hashman]

nice one, chds work great with sega cd, testing some now. Just make sure no spaces in the file names.

EDIT: chds work great for CD/GDi images in general and save heaps of space. DC, PSX etc. going to try to figure out why PC Engine CD is playing up now... edit: I had spaces in the filename, PCECD also works fine with chd.

removed the other extensions and just put in .chd and now theyre working!

for some reason just adding .chd to the list didnt work.

Still having issue with the pi5 not starting on boot on now TWO different arcade machines. The 5v is around 5.1v and ive tried adjust either way. Worked once on one the machines then second power on it didnt. If i push the little reset button on pi5 it fires up.

Nice and big jamma wiring too. I'm having a look at this site here to see if it can help https://forums.raspberrypi.com/viewtopic.php?t=364720

From that link you could try adding:
usb_max_current_enable=1
to config.txt. I'm going to eat some food, will have a play with that setting myself in the next day or two if you don't try it aand report back.

No luck with that command unforunately. I placed it in a randomm spot in the config.txt would that matter?

So I spliced a usb c cable. Connected the ground and 5v wires to the arcade power supply and am getting 5.2v from the usb c. PI5 STILL DOESNT POWER UP until i push the pi5 power button which cancels out any gpio power issues.

Could it be the be the sd card? Im using sandisk 128gb or 1tb extreme cards.

Just found this...

Differences on Raspberry Pi 5
The power button is used to wake up from PMIC STANDBY or HALT instead of GPIO 3.

Instead of loading start.elf, the firmware loads the Linux kernel. Effectively, the bootloader has an embedded version of start.elf.

USB boot is disabled by default when connected to a 3A power supply. Set usb_max_current_enable=1 in /boot/firmware/config.txt to enable USB boot. Alternatively, you can press the power button a single time on a failed USB boot to temporarily enable usb_max_current_enable and continue booting. However, this setting will not persist after a reboot if enabled by pressing the power button.

Got it from https://www.raspberrypi.com/documentati ... k-on-again

FINAL EDIT: I gave up with this cab. Im blaming the cheap arcade supply in there (it must be a timing thing with pi5 power as every other board works).

I ended up splicing in an AC Power Board/Strip and using a standard pi5 power adaptor and now it powers up every time. Itll do the job.

OMG: Even using the power board it wont fire up half the time now. Still having to push the power button on the pi5. This is driving me nuts.

[dee2eR]

I ended up splicing in an AC Power Board/Strip and using a standard pi5 power adaptor and now it powers up every time. Itll do the job.

OMG: Even using the power board it wont fire up half the time now. Still having to push the power button on the pi5. This is driving me nuts.

Damn, I would have thought the Pi5 USB power supply would definately fix it (certainly rules out the ribbon cable or JAMMA power supply or wiring...). Maybe an issue with the Pi itself? Not sure what else to suggest, unfortunately.

I didn't see any weird behaviour when I had your boards here... wish I had done a bunch of power cycling or something...

[Hashman]

I ended up splicing in an AC Power Board/Strip and using a standard pi5 power adaptor and now it powers up every time. Itll do the job.

OMG: Even using the power board it wont fire up half the time now. Still having to push the power button on the pi5. This is driving me nuts.

Damn, I would have thought the Pi5 USB power supply would definately fix it (certainly rules out the ribbon cable or JAMMA power supply or wiring...). Maybe an issue with the Pi itself? Not sure what else to suggest, unfortunately.

I didn't see any weird behaviour when I had your boards here... wish I had done a bunch of power cycling or something...

It powers every time on my Astro City, sometimes on this cab at work and never on my cab at home. Got me stuffed.All these cabs have no isssues booting any sort of jamma board including another pi5 jamma board made by one of your competitors (crap software so dont want to use it).

Looking at this now https://www.raspberrypi.com/documentati ... wer-button

EDIT: Just tried another pi5. Same thing happens so its not the pi.

Looking at this now https://forums.raspberrypi.com/viewtopic.php?t=368938 Rise time seemed to be the issue?

[dee2eR]

I ended up splicing in an AC Power Board/Strip and using a standard pi5 power adaptor and now it powers up every time. Itll do the job.

OMG: Even using the power board it wont fire up half the time now. Still having to push the power button on the pi5. This is driving me nuts.

Damn, I would have thought the Pi5 USB power supply would definately fix it (certainly rules out the ribbon cable or JAMMA power supply or wiring...). Maybe an issue with the Pi itself? Not sure what else to suggest, unfortunately.

I didn't see any weird behaviour when I had your boards here... wish I had done a bunch of power cycling or something...

It powers every time on my Astro City, sometimes on this cab at work and never on my cab at home. Got me stuffed.All these cabs have no isssues booting any sort of jamma board including another pi5 jamma board made by one of your competitors (crap software so dont want to use it).

Looking at this now https://www.raspberrypi.com/documentati ... wer-button

EDIT: Just tried another pi5. Same thing happens so its not the pi.

Can I come visit you at work (or home) sometime to take a look at one of the trouble cabs? If it's not the Pi, and not the software, and not the power and not the... Whatever it is I would like to figure it out.

It shouldn't need a power button, should just work like any other board... I'm not sure how I could have changed anything from vanilla RaspiOS lite that would be causing this to happen... certainly didn't mean to if I have.