No sound retroflag gpi case with pi zero w 2 (Solved)

retropieuser555

@slime1982 Heya yeah the screen lines is definitely specific to me, I left the gpi on for a few hours earlier and it's left some screen burn on the dpi screen itself. So a different problem but nothing relevant to this topic, the audio works, the video works and am happily testing out drastic, n64 and psp. It'll be interesting what we can push on this thing. Thanks again for the fix, we'll have to see if retroflag implement it and make it clear for pi zero2 this the way to go.

pumpytums

@slime1982
This works great thanks.

Can you SSH into your Zero 2 equiped GPI mine reboots everytime. Plays games fine though so doesn't sound like a power issue. Very odd indeed. I even put ssh.txt in the root keeps rebooting every time ssh is enabled.

retropieuser555

@pumpytums Is the file you made named ssh.txt you're putting into the boot folder? It needs to have no extension on the file, just called ssh

retropieuser555

This post is deleted!

pumpytums

@retropieuser555
I think this is an issue

fresh install of Retropie 24th October.
Retroflag default files
SSH in boot
wpa_supplicant.conf for WiFi setting

System boots then crashes. This problem occurs whenever SSH is enabled either via file method or through menu Raspi config.

Slime1982

@retropieuser555

Ah, yeah. I believe those lines will fade out eventually. I've done the same, left it on with no signal from the Pi, so you just get random lines on the screen. They burn in, but it seems to be temporary.

Slime1982

@pumpytums

I'm using the same weekly image, dated 24th October. I can SSH in no problem. That's an odd issue, maybe ask in a Raspberry Pi / Raspbian forum.

Does it happen if you power the GPi with the USB cable?

jpwhiting

@slime1982 Thanks for the fixes. I tried some other cmdline.txt options that were needed previously and various config.txt but this got it working. I ended up removing the other cmdline.txt bits that I tried before from https://retropie.org.uk/forum/topic/26628/audio-issues-after-latest-raspbian-updates-june-2020

I'm still hearing lots of buzzing during game play though. I've got the alsa device set to "default" and the sound device set to headphones have tried various settings in es menu but there always is a loud buzzing. Is it a bad connection to the gpio pins? everything else seems to work well (screen, buttons, etc.)

Thanks, this zero 2 seems to work much better besides the sound issue.

hyperwolf83

@jpwhiting

The following are my config.txt setting that worked for me. I got sound, wifi, and syncthing running with no isseues. I used the weekly retroarch pi 3 image dated 31 Oct. I also get correct stereo sound when using headphone port, with no static.

# For more options and information see
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# 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 to overclock the arm. 700 MHz is the default.
#arm_freq=800

# 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 the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

#config_hdmi_boost=0

# force hdmi while the tv can take time before sending the signal on the hdmi o$
#hdmi_force_hotplug=1

# uncomment for composite PAL
#sdtv_mode=2

# uncomment for lirc-rpi
#dtoverlay=lirc-rpi

# if you plug your tv at the same time as your rpi and that the rpi switches fr$
boot_delay=3

# uncomment if you don't want the rainbow at startup
disable_splash=1

# default CEC name
cec_osd_name=gpicase

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Overclock
gpu_mem_256=128
gpu_mem_512=256
gpu_mem_1024=512

avoid_safe_mode=1

kernel=zImage

dtoverlay=audremap,pins_18_19,enable_jack=on
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
# dtoverlay=pwm-2chan,pin=18,func=2,pin2=19,func2=2
avoid_safe_mode=1
disable_pvt=1
disable_audio_dither=1
# dtoverlay=pwm-audio-pi-zero

jpwhiting

@hyperwolf83 Thanks. That seems to work well here. At first I still got the buzzing but I pressed on the back of the gpi case "cartridge" briefly and it went away completely. I probably have a loose connection in there somewhere.

cnoto

Just confirming that this worked for me and it is definitely worth updating your GPI projects with the pi zero 2. Much better performance!

Lo0twig

At first this works well but after updating the pi via raspiconfig the internal audio error returns.
I tried to use the old config with no luck. Any ideas ?

Lo0twig

Ah i guess the solution is to copy the GPI-Case files again to the sd card after updating.

pumpytums

@slime1982
Hi,
It was the batteries I have another GPi and Zero 2 same issue even in Recallbox. Tried some rechargeables no problems at all.

Odd though it played games no problem which I would have thought would pull more amps.

So Amazon brand Alkaline batteries even new don't like the current draw.

Thanks for your help

suprjami

@pumpytums I've seen a few posts saying decent batteries are needed with the Zero 2W in GPi case.

I have Ikea Ladda 2450 which seem to work.

I have also seen the Panasonic Eneloop Pro are a good choice.

EG500

i had a gpi case, and for the life of me was never able to get the thing to work.

There was one point in time, after about a month of research, restarting the process 3 times and following every guide i could find, there was One time i was able to get the controls to work, the sound never worked, and the controls didnt work in any of the emulators.
After restarting, I couldnt get the controls to work in es at all, and recallbox wouldnt even boot up.

Id recommend staying away from the retroflag gpi case (plus the pi zero has always been pretty bad at emulation in general). Id recommend going with the Piboy dmg, it works with a pie 3 or 4, and just works perfectly right out of the box..

retropieuser555

@eg500 did you hold down select+left (or start+left) to change the controls? That's what seems to trick a lot of people up with the gpi.

The piboy is pretty much unavailable where I am as far as I can tell, unless I paid a big customs cost to import it.

Whereas retroflag's products do seem to be produced and sold quite widely so that is something to consider when choosing between the two. Extra buttons is pretty nice though

EG500

@retropieuser555 yes i did, both ways, it just flat out doesnt work correctly. I was really dissappinted woth it, where as piboy has their own retropie image you just doenload instal and youre done

mcbdz29

@hyperwolf83 Any use of having "avoid_safe_mode=1" twice ?

WhirlyFan

@Slime1982 bless you. this was so painful trying to get this thing set up.