I've updated the link above with guides for both 32bit and 64bit MAME cross compiles. Both verified and working on my setup, and confirmed by at least one other person. For me it takes an ~8 hour compile on my RPi4 overclocked to 2.0GHz down to a ~1 hour compile on my Core i5 machine.

I've added some links to scripts as well to hopefully make it a bit easier for people to get going. Still not automated end-to-end, but enough for someone familiar with package installation under Debian/Ubuntu to build a working cross compile environment.

I'm fairly confident this could be modified for anything running on RPi that uses gcc or g++ to compile, as long as the compile time headers and link time libraries were known, or could be discovered.

For example, if you want to find the dependencies for, say, ScummVM, install the "apt-rdepends" package on your RPi, and run:

apt-rdepends scummvm | grep -v ^' ' | sort | uniq | tr '\n' ' '

They're your runtime dependencies. To find build dependencies, ensure there's a matching "deb-src" repo for every "deb" repo in your /etc/apt/sources.list and your /etc/apt/sources.list/*list files, then run:

sudo apt-get build-dep scummvm

And log the files installed. You can find all dev packages installed with something like:

dpkg -l | grep '\-dev' | awk '{print $2}' | awk -F ':' '{print $1}

That would probably get you 99% of the way there. Ditto for anything where an older version is in the native Debian/Raspbian repos, and you want to build a much newer version.

@skylo By default, during boot, the native resolution of the screen will be identified, so I don't see any problems.

I realize you have resolved the issue, but I thought I might contribute something.

A lot of people don't realize that the quality of the MicroSD card makes a big difference for running Raspberry Pi operating systems. High-speed is important, with a minimum of Class 10 (I know, newer/faster standards now exist) always being recommended. However, the endurance of the card (or the number of writes/re-writes it can handle) is just as important. There are "high endurance" or "industrial grade" MicroSD cards available that should do a better job than run-of-the-mill MicroSDs with Class 10 ratings and will have a longer life-span.

MicroSD cards were meant for storage, for photos and the like. Running an OS from a MicroSD card causes a lot of heat due to random reads/writes happening almost constantly. For the most part, they weren't designed for this purpose and the extra wear and tear can cause early failure.

Of course, running your OS from a real SSD would be best but that's tricky to get working right on a Pi4 (and probably not worth doing on anything older).

@skylo You should open a new thread for that new question.

@rafaz182 having the same issue with 4.7.1. Downgraded to 4.6 with a new flash but stopped working after doing an "apt upgrade" on 4.6 - did this fix you posted worked on 4.7.1?

@tango Thanks for this comprehensive writeup. That's the spirit of a community. :)

For all coming accross this post: This guide works only for Rpi 3B+ (Note the +).

For other models suppporting USB mass storage boot see prerequites here: https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md

I haven't tried it using FBneo so maybe I'll do that. Failing that I'll just get hold of the NES version I guess.

@jamrom2 I did, but that doesn’t give me the option of choosing keyboard keys when I go to the config.

@radji Ran into this while I was researching my own struggles outputting dual monitors from my Pi 4. I found a way to get it done - I'll spare you the walkthrough if that's okay but it involved booting the desktop environment first with xrandr installed and the displays configured there - then rigging the thing to autostart emulation station from there on top of that environment. Long story short, I took a huge performance hit, even the gen. 4 consoles started dropping frames and chopping audio. I was super proud to get it working after many failures and posts online saying it couldn't be done, but unfortunately it just wasn't worth it in the end. Most people suggest an HDMI splitter and now that I can see how rough it can be on the system to make this work - just don't do it is my advice. Maybe it's a moot point for you by now, but FYI for anyone else down the road. Go with the splitter.

@mitu
Thank you, removing the call for the ds4drv on /etc/rc.local solved it!

Ok, thanks for all!!!!

@arcadez2003 said in dodonpachi dai ou jou (normal and black label) stopped working with latest fbneo + latest retropie:

If your using the latest version of FBN and your rom and PGM bios are correct then you should have no troubles running ddp3

Running was working but I had to load the game individually, ie, if I create a PlayList from a folder and scan it, 'ddp3' doesn't get added to that playlist (like if it's not recognized due to a different CRC32 value I guess). Not sure if how that could get officially fix so that it's recognized when creating Playlists.

@mikebrin
it explains how to run in verbose mode via the link @Clyde provided:

@clyde said in Cannot get Player 2 Joystick to work:

Please run one of the games with verbose logging

but if you can't get into the runcommand menu, it's a moot point i guess.

now, as for your issue - donkey kong's 2 player mode uses one stick - the real cabinet only had one (and why not, since, the 2 player mode isn't simultaneous). you take turns on one stick.

it's possible that there's a cocktail/2p mode you can select via the service menu or dipswitches, or you could map the player 2 controls as alternatives for player 2 via the MAME menu for this game only, or something like that.

note, these instructions are for mame2003 (which is recommended), not the mame2016 which you're using (which is not recommended).

@thorr69 Absolutely! When my girlfriend came to my home for the first time more than two years ago, she was very surprised by my RetroPie upright arcade cabinet (subsequently, she told me that she thought "okay, kissing later"), and soon after that, we played together next to another. 😊 We held hands for the first time when we looked up special moves for Street Fighter II Champions Edition online. 💞😄

(Her interest in playing retro games waned over time, but she still likes my "Automat" – German for "machine" – up until this day.)

Sorry for the off-topic, but this triggered some fond memories … 😇

@john_carter No, it's is when I enable the VMS video driver and then the audio fails to work under HDMI. I haven't seen any other reports of this.

It's a common issue, since the HDMI audio is handled by the KMS driver automatically. It's been widely reported - in fact when the KMS driver for Pi4 was announced, it was one of the changes included (see this forum post). Here in the foruns - see this topic.

@colstar said in Outrun control issue:

@colstar I actually placed a few other roms that were not running under MAME into the FBNeo folder and that worked fine! :)

Romsets have to match the emulator and its version, i recommend reading retropie's arcade documentation.

@george-spiggott I didn't know there was a Libretro version of pcsx2. I'm using the standalone version downloaded from the "experimental" section of retropie setup. Works great on my Linux Mint box. Just doesn't have support for CHD files. I'll keep my eye out for an lr version.