Updating firmware for Topping audio hardware

I ran into a problem when I tried to update the firmware of my newly bought Topping DAC/headphone amp. Here's the process:

  1. Connect the power cable to the DX5 II and the power outlet.

  2. Connect the device's USB interface to a PC/Mac via a usb cable.

  3. Turn off the device with the power switch on the back. Press and hold the knob, then power on with the power switch. The screen will show the current software version.

  4. A removable drive will show up in the explorer on PC/Mac. Open the drive.

  5. Extract the downloaded compressed file, then copy the .Topping file to the root directory of the drive. The drive will then eject itself and reconnect

  6. Reopen the drive. A new file will be showing the current firmware version as "Update successful(Version.Vx.xx)" of which the "XX" is the new firmware version that indicates the firmware is successfully upgraded.

  7. Turn off and on the device again. The upgrade is complete.

1 to 4 were no problem and the removable drive showed up. Then in 5 I could drag the firmware file at the root of this drive and DOpus showed it but nothing changed and the firmware update process wasn't starting. I tried several times, rebooting both the Topping and Windows 11 to no avail, fearing my DAC was bricked until I thought of trying with the Windows File Explorer. It worked like a charm.

Now I imagine you won't be able to reproduce this issue and fix it unless you own one of the latest Topping pieces of hardware and it's obviously no big deal as you only have to launch Windows Explorer for a minute and updating a firmware isn't something you have do often. Still, I thought you should be aware of this issue and maybe it should be added to a FAQ as Topping is a very popular brand of cheap audio hardware.

Dopus 13.23 x64

off topic: though I'm not active on this forum, I used DOpus every day for 15 years now and I can't imagine Windows without it. You're the best. :smiling_face_with_three_hearts:

If Opus copied the file to the drive, then Opus's work was done. Why the drive reacts differently is anyone's guess, but all Opus has to do here is copy the file, which it sounds like it did.

(Opus also copies using the same API as File Explorer by default, so it's strange the results were different, unless something like antivirus was treating the two programs differently perhaps, which is quite possible when removable drives are also involved.)