GPi Zero 2 v1.52 & GPi Zero v1.15(Retropie Images for Pi Zero/Zero2 + GPi Case 1 & GPi Case 2W)
-
Just had an idea. With some experimentation, the overclocking script could become an undervolting tool as well. I am currently experimenting with stock 1000MHz freq and an over_voltage value of -1 (negative values are indeed possible for those who didn't know)
If it's stable, I'll keep going down to see if -2 works on my board. The thing is, (and I'm not sure if this is the case or not) if the voltage value is the same as the Pi 3, but the CPU is running underclocked vs the Pi 3, there should be a fairly decent amount of undervolting headroom.
-
The overclocking script I wrote sets the voltage level, even if not present initially in config.txt (At stock voltage): It should be easy to modify for this purpose.
-
@sliver-x yeah, I'm going to modify it myself. Just thought I would throw the idea out there in case you wanted to drop a patch on the OP if you thought the idea was useful.
-
awesome
-
How can I make sure all your custom retropie menu options stick between theme changes? Seems changing to say carbon loses all your custom toggles etc. At least it did for me. Any tips on where to look to make sure they appear?
-
The Advanced Settings menu is defined in es_systems like an emulator: It should show up regardless of the theme, even if the theme doesn't have explicit support for it (Like es-carbon).
I just tested it on mine and it shows up under Carbon for me?
-
@sliver-x ok then I'll have to add it back as I believe I overrode the one in /opt since I added emulators that did not show up. That answers my question thank you! I can amend one to the other. That should fix it.
-
@sliver-x hmm well I checked and it's the same yet I only see the default menu items that come in a standard install weird. Any advice on adding them back?
Edit: scratch that in an idiot and was looking at the standard retropie settings I see the entry adding it back now lol.
-
I can't seem to open the .img file. Windows Imager and Imageburn both give me an error that the file is corrupt or unrecognizable. Anyone get that when they try to image the SD card?
-
@azfunguy are you trying to install the image? Why not use the official raspberry pi imager? It's painless.
-
Does anyone know if it's generally safe to update the OS if needed? Or should we stick to only updating the emulators and packages.
-
@sliver-x I love the theme, it works and looks fantastic in my GPi with the zero w 2. Is there a reason Neo Geo Pocket is not a system? I noticed Neo Geo Pocket Color is and the roms show when I add them, just not the original Neo Geo Pocket.
EDIT: I just added it to the es_systems.cfg file. No big.
-
Unlike the Wonderswan/Wonderswan Color, where there were quite a few black and white only releases, there was, IIRC, 10 non-color NGP games ever released.
Due to this I've never treated them as separate systems on any emulation setup I've made. I have both .NGP and .NGC extensions set up for EmulationStation, so both are detected and handled by the one "System".
Upgrading should generally work (I was able to do a full upgrade of everything from the state of 12/31 to day before yesterday fine), unless dtbo files get updated, then either the LCD or sound will have issues without manual intervention to fix. This would be the same case for any OS image for the machine, not just mine, due to how the LCD/etc hardware needs patches to function correctly.
-
I just made some mods and opened up the hdmi port. I wasn't able to use it successfully though. Any tips? I'm gonna try another tv since I know mine tho new can be wonky about it. I tried a few different ways but didn't have any success. Nothing broke but it just didn't care for displaying. I'm using a straight cable for testing. I'm gonna try other tv's tomorrow but so far no luck. I'm hoping it's just my tv since I'd never use it personally on my own tv having an rpi4 rig with synced saves.
-
@killj0y1 you changed the config txt file and got rid of the dpi display settings?
-
@retropieuser555 no I did but I missed that post mind pointing me in the right direction?
-
@killj0y1 ah okay if you did edit the config txt already back to using HDMI then that's my idea gone. So the gpi case patch comes with the original files and the patch files. Just pop the original config.txt back into the boot directory and that should allow the pi to boot into it's default HDMI mode
-
This image has a custom config.txt that the HDMI scripts edit in place to replace the (crude) functionality the original GPi Case patch performed.
When you enable HDMI out under the Advanced Settings menu, it removes a block of text that sets up the A/V over the GPIO pins, allowing the HDMI output to work at next reboot. When/if it detects the cable has been unplugged, or the HDMI toggle script is ran manually again, it adds it back.
Replace all text in config.txt with the following to set it back to how my setup expects it to be:
# For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details # uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan #disable_overscan=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 # Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # Uncomment this to enable infrared communication. #dtoverlay=gpio-ir,gpio_pin=17 #dtoverlay=gpio-ir-tx,gpio_pin=18 # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on [pi4] # Enable DRM VC4 V3D driver on top of the dispmanx display stack #dtoverlay=vc4-fkms-v3d max_framebuffers=2 [all] disable_splash=1 enable_uart=0 dtparam=sd_overclock=50 gpu_mem_256=128 gpu_mem_512=128 gpu_mem_1024=256 overscan_scale=1 arm_freq=1000 over_voltage=0 initramfs initramfs.img ###gpicase### boot_delay=3 dtoverlay=audremap,pins_18_19,swap_lr display_rotate=1 dtoverlay=dpi24 overscan_left=0 overscan_right=0 overscan_top=0 overscan_bottom=0 framebuffer_width=320 framebuffer_height=240 enable_dpi_lcd=1 display_default_lcd=1 dpi_group=2 dpi_mode=87 dpi_output_format=0x6016 #hdmi_timings=320 0 28 18 28 480 0 2 2 4 0 0 0 60 0 32000000 6 hdmi_timings=240 1 38 10 20 320 1 20 4 4 0 0 0 60 0 6400000 1 avoid_safe_mode=1 disable_pvt=1 disable_audio_dither=1 extra_transpose_buffer=2 audio_pwm_mode=2 dtparam=act_led_trigger=default-on ###gpicase###The HDMI scripts should work now. Unless you deleted ~/gpihdmiout, in which case, you need to put that back since that's where the scripts themselves and the required dtbo files live.
If not, not sure what you're running into; I've gotten it to work with 8 different TVs and monitors so far.
-
@sliver-x ok got it but can I still add an overclock or will your script just refuse to work if anything is set differently. Really only would edit that and overvoltage. So long as it works but way you described I'm happy with that.
-
"enable.sh" takes a backup of current Retroarch config files and EmulationStation's config then restores the HDMI mode copies of them if they exist, deletes the text between the #####gpizero##### markers in /boot/config.txt, copies /home/pi/gpihdmiout/hdmi.dtbo to /boot/overlays/dpi24.dtbo, blanks the file /etc/asound.conf and sets the default sound device in EmulationStation to HDMI.
"disable.sh" takes a backup of current Retroarch config files and EmulationStation's config then restores the LCD mode copies of them if they exist, adds the text between the #####gpizero##### markers in /boot/config.txt, copies /home/pi/gpihdmiout/lcd.dtbo to /boot/overlays/dpi24.dtbo, builds a copy of /etc/asound.conf that performs mono downmixing of the audio and sets the default sound device in EmulationStation to "Headphone".
So long as nothing you set in config.txt conflicts with something "disable.sh" or "enable.sh" is writing to config.txt, or trying to do custom ALSA configs via /etc/asound.conf, it shouldn't matter what you change, the scripts won't touch it.
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.