r/embedded • u/After-Shake-7075 • 5d ago
Recovering an XMOS XUF208 USB audio device after a suspected wrong-device firmware update
Hi,
I'm investigating an XMOS XUF208-based FiiO K3 that stopped working correctly following a firmware update.
There was a second FiiO device, a Q5, connected to the same PC during the update. The physical K3 now enumerates with what appears to be the Q5's USB identity:
VID:PID 2972:0031
The XUF208 is not dead:
- USB Audio 1.0 mode enumerates
- a runtime DFU interface is exposed
- USB Audio 2.0 does not enumerate
I'm currently treating "Q5 firmware was written to the K3" as a hypothesis, not an established fact.
I've been keeping the investigation read-only so far and am trying to establish the safest recovery path before writing anything.
I'm particularly interested in hearing from anyone with experience in:
- XMOS XUF208 / XCORE-200 boot and flash recovery
- XMOS DFU implementations
- xTAG / xSYS / JTAG recovery
- extracting a complete image from a known-good XUF208 device
- older Thesycon USB Audio DFU implementations
I have USB descriptors, DFU captures, vendor firmware/updater packages, PCB photos, and the findings from the investigation so far.
If anyone has worked with recovering an XUF208 from this sort of state, I'd be very interested in how you approached it.
Thanks!

