@frolickin Thanks for the kind words, and glad you have everything up and running.

@mitu OK I will have to go for a pi4 then.

Thank you very much for your help

It works by having only the right pad for the console plugged in at a time. I'll stick to that since my daughter has a USB hub with a switch for each port on her Pi. So I can have all pads plugged in at once but only use the one I want thanks to the power button on the hub.

I've set up four kinds of pads: a NES pad, 3 SNES pads, a N64 pad and a Megadrive pad. Thanks to your setup (with retroarch.cfg files) I don't have to map the pad buttons anymore: I can just power them on and off with the button on my hub and enjoy any console that I like.

Thank you so much for my daughter & cheers from France! :-)

@mitu Thanks a lot for your help.

@clyde
That's fantastic, thanks for the info! I had been searching for usb interfaces on the web, but hadn't seen one like this. I don't see why this wouldn't work. I'll give it a shot, and let everyone know.

@mitu ok i try to put it before emulationstation runs, basically the script erase an empty file that i use with an if conditional, i make an option that let me pause the music, if i activate it, the if creates an objects and while the file exists the music stop playing and if i push again the if erase the file and the music continues. i want that the raspberry erase that file if we have music paused so the music start on the startup and i can activate pause again in the menus.

@mitu Yeah, unfortunately even though they are physically different PCBs, they detect as the same type (Generic Dragonrise USB Controller)

@agtrigormortis that is cool.

@yfzdude thanks... will try them out.

Just wondering if you are got anywhere with this. I'm having the same issue with an AMD RX580 I just got.

OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.6 /opt/retropie/supplementary/emulationstation-dev/emulationstation.sh --debug Dec 23 14:06:19 lvl2: EmulationStation - v2.10.0rp-dev, built Dec 23 2020 - 13:53:37 Dec 23 14:06:19 lvl2: Parsing XML file "/opt/retropie/supplementary/emulationstation-dev/resources/mamenames.xml"... Dec 23 14:06:19 lvl2: Parsing XML file "/opt/retropie/supplementary/emulationstation-dev/resources/mamebioses.xml"... Dec 23 14:06:19 lvl2: Parsing XML file "/opt/retropie/supplementary/emulationstation-dev/resources/mamedevices.xml"... Dec 23 14:06:19 lvl2: Creating window... Dec 23 14:06:19 lvl2: Created window successfully. Dec 23 14:06:19 lvl2: GL vendor: Dec 23 14:06:19 lvl2: GL renderer: Dec 23 14:06:19 lvl2: GL version: Dec 23 14:06:19 lvl2: Checking available OpenGL extensions... Dec 23 14:06:19 lvl2: ARB_texture_non_power_of_two: MISSING Dec 23 14:06:19 lvl2: Added unconfigured joystick SZ-MP USB Audio Gamepad (GUID: 030000004c0500006802000011810000, instance ID: 0, device index: 0). emulationstation: /home/johnston/RetroPie-Setup/tmp/build/emulationstation-dev/es-core/src/resources/Font.cpp:410: void Font::renderTextCache(TextCache*): Assertion `*it->textureIdPtr != 0' failed. Aborted (core dumped)

@g0nz0uk it could be that the driver support has changed in the kernel for this controller, and it's seen differently.

can you not just reset your controller configuration in emulationstation, and rebind? -

Choose Manage Packages.
Choose Manage Core Packages.
Choose emulationstation (Installed)
Choose Configurations / Options (it may also be named Configurations Tools)
Choose the option to Clear/Reset Emulation Station input configuration.
Choose Yes to proceed to clear the controller settings.

Then when you return to ES you will be asked to rebind your controller, that will then filter through to all cores, etc.

@mitu that make sense .. thanks for the help.

@f4cepa1m Worked well, thanks for sharing!

@zera said in Display Problem with CM4 Board:

We combine CM4 and the DPI display, however, we cannot enter the emulator and it only stuck in booting. It can work normally if we change to an HDMI display.

This seems like a problem with the DPI configuration/driver. Does Raspbian Lite works normally with the configuration - does it boot to a text console/terminal ? What emulator are you starting ? By default, RetroPie boots to EmulationStation, not to an emulator.

There is also a solution that we install retropie in Raspbian image, however, it also has a problem. It will flash the desktop of Raspbian when starting, begin the game, or exit from the game.

RetroPie is based on Raspbian Lite (not the Full/Desktop), running RetroPie (EmulationStation) under a desktop env on a Pi is not a supported or tested configuration.

@dankcushions well, I have edited a few more configs and its all working fine. There is an option for resetting permissions - which I thought may have been the solution - if it happens again, that's what I'd probably try - because once it created the file itself it seemed to me ok.