4.26.13 Updated with new versions
Note this post is only about hubs. Users with any other product. For our own UD-3000 dock, please don’t follow this post — we have a separate post on the customized UD-3000 firmware upgrade.
USB 3.0 is rapidly evolving with new hardware and software that create new compatibility considerations, and Plugable is committed to staying on the cutting edge.
This update utility is Windows-only and requires a USB 3.0 capable PC. If your PC has USB 2.0 rather than USB 3.0 ports, or if you use a Mac, you will not be able to complete this upgrade, and should instead contact firstname.lastname@example.org. For Mac customers wishing to update, a Windows installation in BootCamp can complete this update, however virtual machines like Parallels, VMWare, or VirtualBox are NOT able to complete this update.
Plugable products for which the updates in this post are relevant are listed in the table below. Since the updates vary with chipset, to update your hub, you must first determine it’s chipset. You may check the table below for expected chipset based on shipping date, however checking in device manager or system profiler for the device’s vendor and product ID’s is the more accurate and recommended method. Instructions to check this follow the table below.
|VL811||Units shipping from Mid-March 2013 have firmware v9.83- this is the latest available version. Older units shipped with firmware versions 9.20, 9.72, and 9.82- customers with any of these older versions should use the Plugable VL-811 USB 3.0 hub update utility.||Units sold until November 16, 2012 have the VL811 chipset. These units shipped with firmware versions 9.20, 9.72, and 9.82- customers with any of these older versions should use the Plugable VL-811 USB 3.0 hub update utility.|
|VL812||Units purchased from Amazon US after November 16, 2012 (January 17, 2013 for Amazon UK orders) have the VL812 chipset. Depending on your order date and location, these units may have had firmware version 8564, 8571, or 0701. Customers with any of these older versions should use the Plugable VL-812 USB 3.0 hub update utility.|
The discontinued USB3-HUB4 (white) also used VL811 and can follow the same steps as the black four port using the Plugable VL811 USB 3.0 hub update utility.
How can I tell what chip and version of firmware I have?
To launch windows device manager, hit the Windows-R hot-key and run devmgmt.msc
- Find your hub under “Universal Serial Bus controllers.” The device will typically be listed as a “Generic SuperSpeed USB Hub” although it may appear as a “Renesas USB 3.0 Hub” “AMD USB 3.0 Hub” or other entry depending on your system’s USB 3 host controller chipset and driver. Pictured below on the left, highlighted in a red box.
- Right click on the device and choose “Properties” (not pictured).
- From the properties window that comes up, select “Details.” After doing so the window will update to show information similar to what is pictured on the right below.
- From the device’s details page, select “Hardware IDs” as pictured below on the right.
The firmware version can now be seen under the “Details” tab and “Hardware Ids” as pictured below, highlighted in blue on the bottom right.
Note the “REV” details listed after the VID and PID are the version numbers to check in the “Latest Firmware Versions by chip set” section below.
To launch Apple’s system profile, from the top right of your screen click the Apple Logo, choose “About This Mac” and click “More Info” on the screen that pops up. Another screen will appear: click the button here for “System Report.” Once system report is loaded, click on “USB” at the bottom of the “Hardware” section, and then find your USB hub. Different models of hub will display differently, however you’ll know you found the right device when you find one with the following details: in the lower right hand section of the next 2 images:
Product ID: 0×0812
Vendor ID: 0×2109 (Via Labs, Inc)
Note the OS X System profile entries for hub firmware version (both old version 8564 and new version 8571 are pictured below, two hubs were connected)
Mapping USB VID, PID, and REV to your chip and firmware version
VIA does not set USB REV to be consistently mapped to the firmware version, but you can map them like this:
|Hardware Ids (USB VID, PID, and REV||VIA chip and firmware version|
|VID 2109, PID 0812, REV 8571||VIA VL812, firmware version 8581|
|VID 2109, PID 0811, REV 3198||VIA VL811, firmware version 9.83|
Once you have your firmware version, you can compare against the latest available firmware versions.
Latest firmware versions by chipset
Firmware Update Utility system compatibility
As mentioned before, the actual firmware update process requires a USB 3.0 capable Windows PC.
We’ve tested this firmware flash utility on 32 and 64 bit Windows 7, 64 bit Windows 8, as well as 32 bit Windows XP with good results. We were also able to successfully update the firmware on a hub running Windows 7×64 in BootCamp (Parallels and other virtual machines, however, will not work).
If you do not have access to a Windows PC with USB 3.0 support (or a BootCamp partition on your Mac) please contact email@example.com for assistance.
Updating VL811, VL811+, or VL812 USB 3 Hub Firmware
Download the appropriate firmware upgrade utility below. Save the file, do not run it from its current location.
After the file is downloaded, double click on the file, and follow the prompt: pressing Y (then enter) to continue when prompted.
The utility will either confirm that it has detected a VIA VL811 or VL812 hub and briefly show the current firmware version before proceeding with the update, or inform you if no hub is detected. Confirmation of whether the upgrade has completed successfully or failed will also be shown. This should happen within 15-30 seconds after launching the utility and pressing Y (then enter) when prompted.
After update has fully completed successfully, you must unplug both power and incoming USB to the hub to reset it. After waiting a few seconds, plug the power, then the USB cable to your PC back in. If you follow the steps above for checking the firmware version, you should see the newly applied version.
Please feel free to comment with your results and observations if you run into issues during the actual upgrade. We welcome your feedback, and will update the post with any improvements.