Page 1 of 1

Firmware Upgrade problem

Posted: Mon Mar 24, 2014 3:55 am
by stingg
I'm trying to upgrade the firmware using the bat file provided. Somehow when I plug in the USB with the button pressed (3 Green led ligthed up) the device is detected as USB Input Device, Instead of Autosport Bootloader. I do really want to avoid opening up the case and do a fresh update. Am I doing something wrong in the sequence? I've installed the bootloader driver and previously I've updated the firmware once with no issue.

Re: Firmware Upgrade problem

Posted: Thu Mar 27, 2014 11:20 pm
by jcordle
stingg wrote:I'm trying to upgrade the firmware using the bat file provided. Somehow when I plug in the USB with the button pressed (3 Green led ligthed up) the device is detected as USB Input Device, Instead of Autosport Bootloader. I do really want to avoid opening up the case and do a fresh update. Am I doing something wrong in the sequence? I've installed the bootloader driver and previously I've updated the firmware once with no issue.
The latest versions of the firmware (1.2 and above) require newer USB drivers. Were you able to do that?

Posted: Mon Apr 07, 2014 10:18 pm
by brentp
stingg,

Separate drivers are required for the bootloader mode. Fortunately, they are automatically installed during the firmware update process. Make sure you download the latest firmware (currently 1.2.8) and run the .bat file that guides you though the installation process. Also, see the included instructions for installing.

Let us know how it works!

Posted: Thu May 01, 2014 7:42 pm
by momostallion
just a note, with windows 8, i was unable to update firmware (from 1.1x to 1.2x)

windows 8 recognized the device fine with 1.1x firmware using the non V2 drivers but during the update process, the firmware update utility never found the device. this occurred on both my windows 8.1 machines.

i tried my windows 7 machine to perform the update, it worked perfect on the first attempt.

my win 8 machines now work fine reading the device on the new firmware with the new new V2 driver installed.

Posted: Thu May 01, 2014 7:49 pm
by brentp
Thanks for the update. looks like we need to double check it on windows 8; might be related to the unsigned drivers restriction.