Xilinx (AMD) bootloader (FSBL) issues on Windows
Multiplatform USB DFU host utility
Brought to you by:
tormod
Menu
▾
▴
#218 Xilinx (AMD) bootloader (FSBL) issues on Windows
My company uses DFU-util to load a bootloader and UBoot a device running a Xilinx SOC. This system has worked flawlessly for almost 4 years. After Windows released updates to end Windows 10 support; our process has failed on all company computers.
For more information, when we connect the device; Window recognizes it as a USB device but forces the driver to libusk0 and does so on every connection.
I use Zadig to load the WinUSB driver and I can use that to install the first stage bootloader; but then Windows loses the device and opens a DFU 1.1 Emulator that will not accept a WinUSB driver nor give it a WCID. Whether I use Zadig or Device Manager to manually install I keep getting the "invalid suffix" error and the device locks up.
I know this isn't purely a DFU issue; but I'm mainly interested if this is only for people using Xilinx devices; or if all DFU devices have started seeing these errors in the last 2 weeks?
Discussion
Anonymous
Hi Christopher,
Just letting you know, we've encountered the same situation (can be reproduced on win11 and win10). Turns out new MS Teams are probing USB devices (presumably searching for communication devices to use) which triggers a request for device language ID descriptor from each connected USB devices. Since Xilinx (AMD) bootloader (FSBL) does not know how to handle this request, it goes into some weird state which causes DFU to stop responding. Issue can be mitigated by closing MS Teams. I believe this issue is not directly tied with dfu-util and should be solved by Xilinx (AMD).
Best regards.
Seconding this solution. Thank you so much!