Commodore is gearing up to block custom C64 Ultimate firmware, but it's exploring ways to balance "user freedom with user protection"

The Commodore 64 Ultimate just got its first firmware update, but proposed future changes are upsetting FPGA fans who prefer using custom software builds. While version 1.1 provides the microcomputer remake with perks like USB mouse support, a music detect mode for the RGB lighting, and various other improvements, the company is also planning to "prevent non-Commodore FPGA-level firmware builds from being installed" down the road.

In a blog post titled "Why We're Protecting Your Commodore 64 Ultimate FPGA," the reborn microcomputer maker directly addresses firmware lockdown concerns. The company's Chief Technical Officer, Marc Bilodeau kicks off the update by reassuring enthusiasts that upgrades and new features are part of the roadmap, but swiftly turns towards addressing the criticism at hand.

"There will be new hardware revisions, new components, and new capabilities! This is foundational to our roadmap and, frankly, core to the Commodore 64 Ultimate's value proposition. But it also means that firmware built for a different board may not behave safely on ours," Explains Bilodeau.

Latest Videos From

The CTO elaborates by arguing that if users implement custom firmware not made for the C64U, "it could lead to hardware returns and replacements due to actions entirely out of our control. This would have significant financial implications for Commodore, a brand that we know holds a special place in your heart."

Simply put, Commodore is hoping to protect the C64U hardware and the brand from potential FPGA firmware mismaps. The idea of locking down systems to better provide support extends to pretty much every proprietary platform out there, including some of the best retro consoles like the Analogue 3D, but enthusiasts will argue that users should have a choice when it comes to sideloading and modding.

Commodore stresses that its fear regarding custom C64 Ultimate firmware "isn't hypothetical," and is already seeing examples crop up. "We've seen it already in recent community posts," warns Bilodeau, "after users performed updates with the wrong firmware and found their machines in a non-functioning state. Then they contacted Commodore. It's an engineering reality we need to get ahead of now, not after more units stops working."

Addressing frustrations with the fact that the machine is using the same board as the original Ultimate64 by Gideon Zweijtzer, the microcomputer maker argues, "What's happening with this future update isn't about creating walled gardens to keep outside developers away from our systems. It's simply and primarily about two products that share a common origin but are forking down different paths."

Simply put, Commodore is arguing that the firmware lockdown is a damage control measure. At the same time, it's admitting that blocking custom sideloading isn't really in the spirit of FPGA tech, as the scene is already used to open-source hardware like the SuperStation One that uses MiSTer FPGA cores. The situation boils down to fears that the unofficial software could brick your machine due to hardware differences, but to many, it will be a massive caveat in terms of hardware ownership and customization.

The good news is that the FPGA lockdown could be a temporary measure, as Commodore says it's "still considering alternative approaches and evaluating which path best balances user freedom with user protection." That may mean it eventually opts to simply warn people with a message or provide what it deems a safer way to sideload firmware. It opens the door to suggestions by saying "we welcome your input on that," so there's a chance savvy users will influence a better solution for future updates.

Looking for ways to play classics on the go? Swing by the best retro handhelds for emulation gadgets and more.