Author Topic: Firmware Upgrade Problem [Solution: Update driver in Device Manager]  (Read 6461 times)

Offline Igb

  • Baby Retrode
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
This possible solution was posted in another thread:
Hi!

I had this problem too, looks like it is a common problem not limited to the retrode.
Following the instructions there brought me fúrther, problem is described there:
 
http://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx, go straight to the Workaround! You can search for the following sentence: "To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that"

(Though I am not done with flashing yet, at least no usb error and usb connection can be opened.)

edit: Flashing is now working.
This workarround worked for me. I was able to enter DFU mode and install drivers but Flip always threw an error on connecting. I suggest adding this piece of information to firmware update instructions if it is not too much of a hassle.

Using Win10 pro x64 in case that ring any bells.

Regards.

Offline skyhawk71

  • Baby Retrode
  • *
  • Posts: 2
  • Karma: +1/-0
    • View Profile
This possible solution was posted in another thread:
Hi!

I had this problem too, looks like it is a common problem not limited to the retrode.
Following the instructions there brought me fúrther, problem is described there:
 
http://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx, go straight to the Workaround! You can search for the following sentence: "To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that"

(Though I am not done with flashing yet, at least no usb error and usb connection can be opened.)

edit: Flashing is now working.
This workarround worked for me. I was able to enter DFU mode and install drivers but Flip always threw an error on connecting. I suggest adding this piece of information to firmware update instructions if it is not too much of a hassle.

Using Win10 pro x64 in case that ring any bells.

Regards.

How did you find the hex and binary codes for the USB Device Descriptor? I tried the workaround a couple days ago but couldn't get it to work. I feel like I did the workaround wrong.

Offline newbie2

  • Baby Retrode
  • *
  • Posts: 20
  • Karma: +0/-0
    • View Profile
If you go to device manager, double click the entry, and click details, and in the "Properties" drop down select  "Hardware Ids." it should show the VID, PID, and REV. With respect to Retrode 2, it should probably be VID_03EB PID_2FF9, and REV_0000.  If the computer can't get that information from the device (for example, it says the VID and PID are both 0000) then the work around won't help. In that case, I'd recommend trying a different PC. (Note, this VID/PID combination match the entry for AT90USB64 in the atmel_USB_dfu.inf file that is installed as part of Flip 3.4.7).
« Last Edit: 22/Aug/2017 01:43:24 AM by newbie2 »

Offline skyhawk71

  • Baby Retrode
  • *
  • Posts: 2
  • Karma: +1/-0
    • View Profile
I see. I should probably try messing around with it again to see if I could get it working. If push comes to shove, I might have to get my WinXP machine up and running again.

EDIT: As it turns out, I did the workaround incorrectly. I had accidentally created a sub-folder inside the root folder that was supposed to be made in regedit. The workaround now works.
« Last Edit: 25/Aug/2017 02:42:42 PM by skyhawk71 »