@Flexo55 Sure it is possible. Just think about your requirements.

Which input formats (16:9, 4:3, 5:4, ...) and resolutions (1920x1080, 800x600) should be accepted on the HDMI side? Which output standard should be supported? (NTSC/PAL or both?) Which framerate you need for your CRT (50Hz/60Hz/...)? Shall it support conversion options when converting e.g. from 16:9 (in) to 4:3 (out)? Do you also want HDMI audio looped through the device or will you use the Pi's headphone jack or USB audio? Do you want extra filters supported by the device, e.g. blurring, scanline modification, ...?

This might be one device as example: https://www.startech.com/en-ch/audio-video-products/hd2vid2 (obviously you need a Micro HDMI to HDMI adapter)

I would also ask or research in some AV forums on recommended products for your project and your requirements.

@mitu @BuZz I know this is an old topic, but I'd also like to delete my account. I posted another topic but tried to delete it(couldn't) since I felt it was irrelevant. I don't see any options to message any admins to delete my account so I was wondering how I'd go about contacting an admin to delete my account? I know my post will stay there but it's alright since I privated the topic since I was embarrassed by my question.

First, back up the config.txt file.

Then, try modify disable_overscan=1 by changing it to #disable_overscan=1 .

Also, the last part looks strange. Did you have add it to fix the overscan issue?

state 0xa [HDMI CUSTOM RGB full 16:9], 1920x1080 @ 60.00Hz, progressive pi@bartop:/ $ /opt/vc/bin/tvservice -m CEA Group CEA has 4 modes: mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive (prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive mode 95: 3840x2160 @ 30Hz 16:9, clock:297MHz progressive mode 97: 3840x2160 @ 60Hz 16:9, clock:594MHz progressive pi@bartop:/ $ /opt/vc/bin/tvservice -m DMT Group DMT has 1 modes: mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive

Generally, for overscan issues, you have to uncomment and change these values:

#overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16

@StuMcBill

So, I've updated the bootloader to "NVME/USB Boot" (got the green screen and rapidly flashing green light), removed the SD card, placed a USB stick (flashed with Raspbian Lite) into one of the USB3 slots, and it won't boot.

I get the message below:

"Raspberry Pi 5 - 4GB

bootloader: 6fe0b091 2024/06/05

update-ts: 1718268387

board: c04170 ce7cb976 d8:3a:dd:a6:ef:65

boot: mode USB-MSD 4 order f14 retry 0/128 restart 1/-1

SD: card not detected

part: 0 mbr [0x00:00000000 0x00:00000000 0x00:00000000 0x00:00 power: supply: RPi USB-PD 5000 mA CC1 PMIC: reset normal 0x0 us net: down ip: 0.0.0.0 sn: 0.0.0.0 gw: 0.0.0.0

tftp: 0.0.0.0 00:00:00:00:00:00

display: DISPO: HDMI HPD=1 EDID=ok #2 DISP1: HPD=0 EDID=none #0

Boot mode: USB-MSD (04) order f1

USB2[1] 000206e1 connected

USB2[1] 0020003 connected enabled

USB2 root HUB port 1 init

USB2[1] 000206e1 connected

USB2[1] 00200e03 connected

enabled

USB2 root HUB port 1 init

USB MSD stopped. Timeout: 25

Boot mode: SD (01) order f

seconds

Failed to open device: 'scard'

Failed to

(cmd 371a0010 status 1fff0001)

Boot mode: RESTART (0f) order 0

open device: 'scard (cmd 371a0010 status 1fff0001)

Boot mode: USB-MSD (04) order f1

USB2\1) 000206e1 connected

USB2(1) 00200e03 connected enabled

USB2 root HUB port 1 init"

Any ideas?

READ THIS FIRST before asking for help.

It's been a while since your post, but I wanted to offer some insight. I had the same issue with using cheats in Retroarch MAME, and it took me a while to figure it out. One thing I want to point out is when you’re playing a game, you can enable cheats through the Retroarch menu by setting “Enable cheats” to On. Alternatively, you can enable cheats globally by editing the configuration file to include the line mame_cheats_enable = "enabled".
If you’re into more advanced game hacking, you might want to read this guide on kernel-level injectors. It has a lot of useful information.

@Addison No Problem :-)

@SuperMazut yeah. Retropie only cares about the retropie-mount folder on the USB drive -- whatever else you do with the rest of the drive, doesn't matter.

I have done exactly that myself because for some reason I couldn't get retropie to run on top the Lite OS. Long story short, I like it. You can set boot order to run Retropie first and you got a desktop environment as a bonus when you exit RP. I have yet to find any disadvantages to that... Space efficiency maybe, if you have a smaller SD card?

@Flexo55 Good you did find the cause. Please, as a courtesy to other users of this forum, do edit your first post and add to the subject something like [solved].

@mitu hi sorry yes I meant Raspberry Pi 4. I have since deleted all of the PS2 ROMs and replaced with PS1 ROMs in .chd format and I’m still getting the same error message about not being able to parse the data

I had the same problem.
In the bottom of this link is my solution. Generel advice is to make a backup before updating RetroPie.
https://github.com/BlitterStudio/amiberry/issues/1392