Launcher: LCD backlight flickering about retro-go HOT 13 OPEN

from retro-go.

I don't think is a software related problem.
Are you using the Odroid-Go or custom diy? If it's custom diy, is lcd module or lcd only? If module, the voltage to module's VCC pin?

from retro-go.

I don't think is a software related problem.

I can't observe it while playing games. I can see it only in the launcher selection screen. It also stops flickering when I press the MENU/OPTIONS button.

Are you using the Odroid-Go or custom diy? If it's custom diy, is lcd module or lcd only? If module, the voltage to module's VCC pin?

Custom DIY with LCD module. The module has 3v3 regulator, so it requires 5v on VCC the pin.

from retro-go.

I got the same issue before too, this trick works for me. Skip the regulator by jumping J1 on the lcd module, then 3v3 to the vcc pin.

from retro-go.

Thanks! Jumping J1 fixes the issue, but then I can hear a crackle from speaker when I enable the circuit. This is ESP32 DevkitC v4 and I'm using its internal AMS regulator to expose 3v3.

from retro-go.

i2s dac or internal dac with amp? which amp board?
if you planning to use the battery, you should use a 5vdc booster(recommend using power bank circuit), get 5v output to esp32's vin.

from retro-go.

My diy custom. Working good except some super small noise while charging.
Parts list: lilygo t7 v1.5(esp32-wrover-e 16mb eeprom/8mb psram, support battery), ili9341 2.8 lcd, pam8302 2.5w amp(with some small changes on the module to use fixed volume input), 7mm buttons(default odroid-go schematic).

Below image is testing wifi, web file server switch control, i'm just added a fews min ago

from retro-go.

I don't think is a software related problem.

I can't observe it while playing games. I can see it only in the launcher selection screen. It also stops flickering when I press the MENU/OPTIONS button.

Are you using the Odroid-Go or custom diy? If it's custom diy, is lcd module or lcd only? If module, the voltage to module's VCC pin?

Custom DIY with LCD module. The module has 3v3 regulator, so it requires 5v on VCC the pin.

Got the exact same issue with my selfbuilt retroesp32 boards. With only the lanuncher open the speaker crackles and the backlight flickers. With the menu open it stops. I thought the issue is sd card activity. The pcb routing isnt great and there is crosstalk between the sd lines and the audio line. The crackling causes the amp to draw more power and that draws down the backlight voltage. Some boards are worse than others so it looks the underlying issue is the hardware design but it can be improved or fixed in software.

from retro-go.

Got the exact same issue with my selfbuilt retroesp32 boards

Are you referring to my boards? Retro ESP32 Hardware

I recently released (8 months ago) a slimmed version without the FTDI chip, reducing noise, cost, added usb c + programming header.

I can confirm that you will get flicker if the programming header is plugged in and the device power switch is set to OFF. Thats just a power supply issue. Move the power
switch to ON position and signal noise is gone.

Once you are done programming, power from LiPo or USB, flicker doesn't happen

from retro-go.

Yes got some of of your pcbs made. Pic

Agree it is a power issue. I use lipo but a larger c7 because the audio was too low. 220pf is far lower than what the datasheet suggests. Then the audio was ok when using the emulators but it made the screenflicker and audio noise worse in the launcher. I think the launcher must be constantly polling the sd card whereas the games dont. Audio and sd traces run parallel which also doesnt help. With the 220pf cap the noise was barely noticable and no flicker.
Was planning on re designing the board when i find time. Maybe with a s32s3 and i2s audio. That should avoid some of the issues.

from retro-go.

software solution is in
g_input_read_battery: noise to signal ratio #51

from retro-go.

Can anyone attach a short video of the flicker, for reference?

from retro-go.

I'm doing some spring cleaning of issues inactive for 1-2 years.

Is this issue still relevant? And if so has anyone made progress in improving the situation?

from retro-go.