Comment 12 for bug 1596662

I was able to upgrade the firmware of the reader from a virtual machine running windows with virt-manager/qemu.

But I don't recommend this method of upgrade.

You have to attach the broadcom usb device to the machine, then execute the dell control vault2 firmware upgrade.

The thing is that once it starts the USB device will disappear, and it will appear again with a 0a5c:5831 ID. You have to be quick to reatach this new usb device (in live) on the machine so the upadate can continue. And it will disappear again and appear again. Like 8 times. If you fail to be quick in attaching the device the updater will abort and will tell you to reboot.

If the device don't completes the update it will be unusable. It will not identify itself as a smart card reader and will have the 0a5c:5831 ID.

You can however retry the update.

Once the upgrade completes the USB ID will change to 0a5c:5832 and it will identify itself as a smart card reader.

Another important thing is that you have to enable the TPM and set it to disable. And also attach the TPM as a passthrough device on the qemu/kvm machine for it to work.

I finally was able to upgrade the firmware correctly using this dirty method.

So, meanwhile I achieved to upgrade the firmware from a windows virtual machine, I don't recommend it.

I think in the end is simple and less risky to run the upgrade from windows directly.

Its a shame that dell or broadcom don't provide a way of updating this firmware without requiring windows.