AMD has quietly pulled a bait-and-switch on its Linux-using FPGA developers. The company changed Vivado’s licensing mechanism so that activating a license now requires running a Windows-only tool. For a community that has relied on AMD’s FPGA toolchain on Linux for over a decade, this is not a minor inconvenience. It is a breach of trust.
The change, first reported by It’s FOSS, replaces the old license activation flow with one that demands a Windows executable. Linux users must either spin up a Windows VM, dual-boot, or borrow a Windows machine just to activate the software they already paid for. The tool itself runs on Linux. The license check does not.
AMD’s official workaround — use a Windows machine — is insulting. It tells the Linux FPGA developer community that their workflow is an afterthought. This from a company that has spent years courting open-source developers with ROCm, with its acquisition of Xilinx, with promises of better Linux support. Those promises ring hollow when the licensing gatekeeper is a .exe file.
The timing is particularly galling. FPGA development has been a rare bright spot for Linux in hardware design. Xilinx tools, now AMD tools, were among the few professional EDA suites that treated Linux as a first-class platform. Vivado users on Linux built entire CI/CD pipelines, remote development clusters, and automated build systems. Those workflows now carry an asterisk: works on Linux, but only if you have a Windows machine to turn the key.
AMD could have offered a Linux-native license manager. It could have provided a command-line activation tool, or a web-based flow, or a hardware dongle. It chose the cheapest path: ship a Windows binary and call it done.
What this means for builders is simple. If you are evaluating FPGA platforms for a Linux-first design shop, AMD just gave you a reason to look at Lattice, at Intel’s Quartus, at open-source alternatives like Project IceStorm. Trust in toolchain reliability is hard to earn and easy to lose. AMD lost some of it this week.