OSSC Pro firmware v0.78

[marqs]

Firmware version 0.78 has been released:

* 1920×1440@60 input support added for both analog and digital sources
* 1152x864_75 sampling preset added
* 2048×1536 and 2560×1920 (PR2x) output presets added
* LG VRR compatibility fixed
* Workaround for Mister SNES core jitter added
* Scaler framelocking consistency improved
* Support for RF added (legacy AV expansion)
* UI improvements
** infoscreen display when OSD is off
** OSD highlight color option
** Profile number entry via remote
** FW file selection menu

Download link
Update instructions

Note: The following settings have been updated, thus their changes saved using previous firmware versions are not loaded from existing profiles:

* Custom output timings (due to added new presets)
* Sampling presets (due to added new presets)
* Legacy AV opt. (due to added CTI options)
* A-LM 384p/480p proc (due to added 2560×1920 mode)

[Zacabeb]

Nice! 🙂

One thing that I think is needed though is a means to convert sampling presets in existing profiles when affected by a firmware update, so they don’t have to be readjusted.

[Jamie Shaw]

Having issues myself with installing the update.  Tried two separate SD cards, both formatted to FAT32.  Both give “error -5” when using the renamed firmware .bin from GitHub.

Thoughts?

[Ray T]

Does your SD card work for other functions in the Pro. It took me a few tries to find a SD card that would work or by that maybe one I could format the right way, when I tried saving profiles to SD and renaming all the profiles on the Pro. My update took fine for the same card.

Only one thing with mine, after the update should the Pro reboot? mine went lights out and I left it for a few minutes, before power cycling it at the mains to bring it back. After that it turned on fine and shows 0.78

[Jamie Shaw]

Works absolutely fine for profile load/save.  Just firmware updates that seems to be giving an issue.

This is my first upgrade since getting the Pro, which came preinstalled with 0.77.  I could try reinstalling 0.77, to rule out the card…

UPDATE: Tried reinstalling 0.77, same -5 error. I will try a third, larger SD card that might be more reputable.  Other than that, faulty OSSC? 🤔

• This reply was modified 3 months, 2 weeks ago by Jamie Shaw.

[marqs]

Which tool do you use to format them? You can also try formatting them to exFAT.

[Hypetreme]

“Profile number entry via remote”

What does this exactly mean?

[Jamie Shaw]

I normally use the SD Card Formatter for Mac as it’s never given me any problems with any flashcarts (EverDrive, EZ Flash, etc).

I’ve just tried with two other cards, both 32GB (larger than the previous 1GB I’m using for profiles). One formatted to FAT32 with 32k clusters, the other formatted to exFAT.

Both give error -5.

• This reply was modified 3 months, 2 weeks ago by Jamie Shaw. Reason: Fix duplicated link text

[marqs]

Could you try some other tool for formatting? The update function is tested on the factory so unless there is something that breaks it on 0.77 for that specific board, chances are that the FAT library has issues reading the filesystem created by that tool. Error -5 btw. means CRC check for the firmware header fails.

[Jamie Shaw]

Firstly, thanks for the assistance with this.  It’s appreciated.  Apologies if this isn’t the correct thread for support, I’m happy to move this over to the GitHub repo to keep it organised if required? (Or a different thread on the VGP forum, as the OSSC Pro was purchased from them 12/02/2025).

So, I’ve tried all of the following:

• SD Card Formatter for Mac, using both “Quick Format” and “Overwrite Format”
• Disk Utility (macOS), using both FAT32 and exFAT, using MBR Partition Map.
• newfs_msdos command via Terminal (macOS)
• A 60GB PlayStation 3
• My wife’s old Panasonic Lumix digital camera

All yield “Failed (-5)”. And just to confirm: no SD card provides -1, no FW file gives -2.

As previously mentioned, saving/loading/renaming profiles on the SD Card gives me absolutely no trouble at all.  I just seem to fall at that CRC check for whatever reason.

And to be on the same wavelength, ossc_pro.bin yields the following checksums:

• MD5: b9c40357d7fd719cfc4f29713ad3e06b
• CRC32: 1b812510

• This reply was modified 3 months, 2 weeks ago by Jamie Shaw. Reason: Gratitude

[marqs]

If there really is SD related timing issue on 0.77 which corrupts read data on that board, then one option is to ship you a JTAG programmer to enable flashing another firmware version. We’ll need to consider feasibility of that and still think if there’d be any workarounds left.

[Jamie Shaw]

Thanks.

I’m kinda at a loss at this stage, having tried several cards (of various sizes), formatters, and devices. All are fine for profiles read/write, but firmware always fails.

In regards to JTAG, it sounds like a viable option if given step-by-step instructions. If it is a bad FW on this board, hopefully a clean flash could resolve that. If I could provide any debug logs, I would… 😅

Failing that, it’s going to be a return for replacement with VGP (and have to deal with the customs for returns 🙃).

[marqs]

JTAG update procedure is similar to OSSC Classic which is described here. You just need to enable “Unprotect EPCS/EPCQ devices selected for the erase/program operation” from options before flashing. The de-facto programmer is a bit expensive so we should just find a robust one from the many cheaper options available on market (out of which a majority have some issues, unfortunately).

[Jamie Shaw]

Any recommendations?

What’s the risk of a lousy programmer? Bricking the device?

[marqs]

The most economical option seems to be ordering $1 clone like this and programming custom firmware on it. We’ll need to test that before recommending it, though.

[Author]

Posts