GPi Zero 2 v1.52 & GPi Zero v1.15(Retropie Images for Pi Zero/Zero2 + GPi Case 1 & GPi Case 2W)
-
The size is normal: Retropie is split across two partitions on the card: A small FAT32 formatted one with the boot files and the remainder is an ext4 formatted partition: FAT32 is supported by any operating system made in the 21st century (It was introduced with Windows 95) but ext4 is Linux/Android only unless you use a third party utility to access it.
I mentioned the switch because, if that's not engaged, Safe Shutdown doesn't work at all and flipping power has a high liklihood of corrupting the OS depending on what's going on I/O-wise when it happens. Also don't install the Retroflag GPi Case patch, as I've integrated what it does into the image itself, with alterations (The stock patch simply copies config.txt files around, my scripts edit this file in-situ so other settings like overclocks aren't wiped when switching HDMI/LCD modes), so things will most certainly break if it's done.
-
Not sure I'm following what you're saying here: Back from what? Did it work at some point?
-
I only use FBNeo for CPS and Neo Geo in the default setup: ROMs would be put in those folders. You can always edit es_systems.cfg to change this behavior if you'd like.
-
@sliver-x
thank you for your quick reply. I am migrating my roms to your image. I was put gamelist and images in each console rom folder. Some how , seems this image use/opt/retropie/configs/all/emulationstation/gamelists- How can I set emulation station read game list and images from each rom folder?
- For megadrive, seems it's special one. I didn't find game list from above path?
-
Putting a gamelist.xml in the ROM folder will override any under /opt: I put the gamelist, screenshots and ROMs all in the same folder so they act as self contained "modules" on my unit (Roms and snaps are all referenced by relative paths like: ./images/Whatever.png ./Whatever.zip in the gamelists).
Note that doing it this way will cause issues with scraped data VS what's in the ROM folder, but I don't use the built in scrapers so it's not an issue for me.
-
@sliver-x
I put roms into gab folder, and none detected. I can see there is gba entry for es_system.cfg. Is it a bug ?False alarm
-
@sliver-x
Want to check, if you release a new version, like 1.3, how to upgrade?
I like this image very much. -
@sliver-x Yeah, I really don't know what is wrong with mine.
I totally wiped the SD, reset the partitions and then set it all as one partition and formatted it. When I reflashed, the two partitions were as you've described.
Same result when I put the card in, screen lights up but nothing happens. I left the GPi sitting around for a long time just in case it was doing something behind the scenes, but nothing changed.
It doesn't really matter that much, I do have a working build. I just don't know how else to proceed here, beyond buying another SD Card. This one has worked on a Pi4 previously though, I just traded it in for a bigger capacity card.
-
At this point all I can really think of doing, if I were in your situation, would be to manually enable SSH, connect to it and start looking at logs to see what may be going on.
You'd have to flash the image, I would suppose. I'm not really a programmer/developer (More of a back-end IT infrastructure person), but I guess maybe trying to set something up on Github would be an educational experience if anything.
-
Hello i'm using gpi case since 2 months ago, using the beta of recalbox and is stable with no problems, i have modded my case and added a batery of 3000mah of capacity but , i have no charge indicator.
I want to run retropie and i want to know if its possible to have a charge indicator with retropie and if using your image i can add another emulators for example nds psp?
I am following your posts and waiting for improvements and thanks for your work.
-
You would have to write some kind of driver that queries whatever charging circuit handles the battery pack, then figure out a way to get that displayed.
You can add any emulators you want via the Retropie Setup script as usual.
-
This update has been rendered obsolete.
-
I've updated this to v1.3, which barring any bugs will be the most likely final release. Primarily I've improved the LCD/HDMI dual configuration: It now supports unique Retroarch Configs/Core Overrides and EmulationStation settings for each mode.
There are also improvements to WiFi stability, Asian language font support and an improved CPU Overclocking script along with better HDMI scripts.
I've also thrown together a small update package that will upgrade v1.2 or v1.21 to 1.3. Extract the patch archive to /home/pi and restart ES or reboot: A new menu entry will appear under Advanced Settings that will initiate the upgrade process.
It will overwrite /etc/rc.local and /boot/config.txt so any custom changes to those files will be lost. Also do not run it in HDMI mode! I've tested it and it works for me going from a clean v1.2 image but I recommend doing a clean flash if possible.
-
@sliver-x Thanks for the update and for creating this image in the first place. I have yet to install the update but the previous version is working great!
-
Aside from the WiFi running better the only other major improvement over v1.2 is if you run the device via HDMI: The separate configs for each display mode allow me to have CRT shaders enabled and no ES Power Saving for HDMI and no shaders/Default Power Saving for LCD, etc.
Settings made in either mode are independent except on the first time HDMI is enabled: It uses the existing configs as the template to build the HDMI config archive.
(I actually like this thing as a console more than I do a handheld, lol)
-
@sliver-x I just did the update and all went fine. I will not use HDMI but it's always nice to have the latest :)
-
@sliver-x Would you be willing to elaborate on what was changed to increase wfi stability?
-
I was getting erratic behavior out of my WiFi connections: The interface would go down during transfers, or just at random for no discernable reason. As in not just losing connection, but outright disabling itself.
Digging through OS logs I was seeing the WiFi driver putting the NIC to sleep at seemingly random times, and never bringing it back up. I'm guessing the current driver is buggy in this regard or something? So I disabled the driver's power saving modes by putting this in /etc/rc.local to see if that made a difference:
iwconfig wlan0 power off
The problems immediately stopped after doing this.
-
Hello yesterday i flashed your image to an sdcard to and i ativate wifi and send some games , then when i choose restart emulationtstation i get an screen error - emulationstation crashed.
I shutdown system and start again but same problem.
What i can do to solve this problem ? -
Reflash it. Something's wrong if that's happening.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.