![]() ![]() So as a first step I tried to reverse the source code of the driver. ![]() The problem is that the xusb_xlp.sys driver is not compatible with Windows’ “Device Guard” feature. Once the firmware is uploaded the cable detaches and comes back as a new USB device called “Xilinx USB Cable”, backed by the more common windrv6.sys Jungo driver. This is the job of the xusb_xlp.sys driver from Xilinx. The integrated CY7C68013A microcontroller comes with a default firmware that presents itself as an USB device with the sole purpose of loading the real firmware into RAM (shown as the “Xilinx Platform Cable USB Firmware Loader” device). The USB cable has a somewhat unusual boot process. “Device Guard” can for example be disabled by setting the “Enabled” key in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity to 0. TLDNR: A quick fix is to disable Windows’ “Device Guard” feature, for a more thorough fix read on. ![]() And the next generation USB cable was sufficiently expensive (>300€) that I wasn’t about to just give up, so in the rabbit hole I went. Googling that didn’t turn up much useful advice, but the adapter still worked on an older laptop, so it wasn’t the USB device per se.
0 Comments
Leave a Reply. |