@mitu Well, if something worked incl. mouse orientation in the past (hdmi_rotate=..., config.txt) and then stops (rotate=..., cmdline.txt) working it is IMHO a regression as the foundation is still issuing the Rpi Kernel and firmware.

Anyhow, using xrandr or wlrandr is not an option as I don't want to configure X/Wayland for SDL based emulators I have in use.

It seems I have to table it at the Raspberry Pi forum.

@mitu

Only as purely information:

Yesterday i have turned on my Pi4 for pass some hours on retrogaming.
I do my usually and periodicy check for update by retropie_setup including the kernel and os update.

During that i have noticied another update to components rpi-eeprom....... this time, if correct, as version 16.x.

When all update it's completed, exited from retropie_setup and back to emulationstation i have open the terminal whit F4 and i have tryed to check the status of eeprom by command:

sudo rpi-eeprom-update

Immediatelly after that i have noticed there's an update on side VL805 in pending.....
I don't have touch anythings...... i'm not triggered this update manually how i have do whit the booloader side.

I thinks, in someway, the autoupdate service it's now works.........

From same Terminal i have do:

sudo reboot

Waited my Pi4 reboot whiout any issue...... and now by Bootloader and VL805 as been update to current and last stable release.

I think they fixed that.... because, in the pass, although there were updates it seemed to skip them.

@Simrose At the time of the writing of the guide the 5.10.x was hit and miss. Maybe it is more on the "hit" side in the meantime. I guess 5.15.x is the new "hit and miss". In any case: Good luck.

@mfraz74 Looks like Debian doesn't package the 8bitdo-tool or it's included in a plugin, but I haven't used fwupd so far, so I can't offer more details. Try using the macOS updater to install the latest (4.20 I think) version of the firmware.

One of the perils when updating to the bleeding cutting edge firmware.

Unless it is really needed I advise to stick to a kernel and firmware that works well on your setup and make it permanent and use a more cautious update than full-upgrade.

You should post issues with beta firmware on the Raspberry Pi forums, since you'll get better support there. If you want to get back to a working EEPROM, I suggest you use Raspberry Pi Imager and flash the latest stable EEPROM image.

@notthesame HAHA DERP. Thank you.

Hello, I was looking into the firmware flashing options too for my Controlblock. Have anyone tried to flash with Arduino Uno as ISP or with the Arduino Nano Every?
As I have both it would be the fastest but I would love some help to do it right...

Thanks

Oh I guess this may have something to do with it... on their sales page and not their support page:

nofwupdate2.png

And yet they still offer the firmware and utility on the support side of the website.
Oh well, only cost me 3 frustrating hours of my life.

I would think it would be fine as the firmware is stored on the SD Card itself

Thanks a lot for that!
I have just announces it in a tweet, see https://twitter.com/petrockblog/status/1000702534674198533 :-)

Thanks for the feedback!

It's to bad that the original SNES30 / SFC30 have been discontinued.

Would love to see a Bluetooth version of the new SF30 2.4G / SN30 2.4G models or a new production run of the original models.

I use Start+R to connect to retropie and Start+Y for connection to my switch. Not sure what the modes are actually called.

Hey I am having the EXACT same issue. So did you Filezilla in and remove the extra "input_player_1" entries? Ive been messing with this since Saturday. I also had this issue with an afterglow xbox 360 controller.

Pi: 3 B
RetroPi: Latest 4.0 build
Controller: NES30 Pro
Firmware: 4.0

so same specs as yourself.