Firmware Upgrade Problem [Solution: Update driver in Device Manager]

[JoeMD]

Hey folks,

I've only had my Retrode for a little while. I just got the SMS plug-in and tried to upgrade the device's firmware as described on the site. However, when I press HWB and RESET the computer continues to recognise the Retrode as the Retrode, it doesn't ask for drivers as stated in the instructions. I've tried it over and over and can't get it to work. Any help would be greatly appreciate.

Cheers.

Retrode 2
Windows 7

[Matthias_H]

You need to keep HWB pressed down until a second or so after you release RESET. Also, do they both *click* the same way when you press them? (could be that the HWB push button is not aligned correctly)

[JoeMD]

I tried it again but I'm still not getting anywhere. I help down the HWB for a few seconds after pressng Reset as you suggested. The computer "donged" (made the sound it does when removable media is removed) once as id media is being removed normally. Very soon after this (within the few seconds HWB is held after pressing Reset) and then twice more in quick succession. However, the computer no doesn't recognise the Retrode is plugged into it at all, as the Retrode itself or as a new device.

If I do the same but release HWB right after the first "dong" the computer recognises the Retrode again. No matter what I try, the computer NEVER asks for drivers.

I tried the Retrode as-is with the SMS converter and it seems to work fine, although I only ran it for a short time. Still, I'd like to get this issue sorted for any future firmware updates.

[Matthias_H]

Could you please check your device manager and see if there is a device like "Jungo" or "AT90USB646" there? Maybe you already have the driver installed for whatever reason.

[JoeMD]

Tried it twice. First I got a device called "Retrode" then "Unknown Device"

[korori]

1.) Use Device Manager
2.) Find Unknown Device
3.) Right Click on it
4.) Select Update Driver Software
5.) Select Browse my computer for driver software
6.) Browse to where you installed Flip
7.) Make sure Include Subfolders is checked
8.) Click Next
9.) It will then install the drivers needed for the device.
10.) Then Follow the tutorial on how to use flip to update the firmware.

Korori

[JoeMD]

Thanks very much. Worked like a charm. 

[thomasgame]

1.) Use Device Manager
2.) Find Unknown Device
3.) Right Click on it
4.) Select Update Driver Software
5.) Select Browse my computer for driver software
6.) Browse to where you installed Flip
7.) Make sure Include Subfolders is checked
8.) Click Next
9.) It will then install the drivers needed for the device.
10.) Then Follow the tutorial on how to use flip to update the firmware.

Korori

I try to browse for Flip and the program refuses to bring up Flip.

[Wannado]

6.) Browse to where you installed Flip

I try to browse for Flip and the program refuses to bring up Flip.

Did you first install FLIP?

The link to FLIP provided on the firmware page is outdated. It only takes you to the front page of Atmel's website.
Here's an updated link to the download page for FLIP: http://www.atmel.com/tools/FLIP.aspx

FLIP requires a Java Runtime Environment (JRE) to run.
If you already have a JRE installed, download "FLIP 3.4.7 for Windows (requires Java Runtime Environment)".
If you do not have a JRE yet, download "FLIP 3.4.7 for Windows (Java Runtime Environement included)" instead.
Note that, from time to time, the version number of FLIP will increase, but I will not update the text of this post to reflect that.

To start each download, click the icon next to its description text on the download page.

[thomasgame]

6.) Browse to where you installed Flip

I try to browse for Flip and the program refuses to bring up Flip.

Did you first install FLIP?

The link to FLIP provided on the firmware page is outdated. It only takes you to the front page of Atmel's website.
Here's an updated link to the download page for FLIP: http://www.atmel.com/tools/FLIP.aspx

FLIP requires a Java Runtime Environment (JRE) to run.
If you already have a JRE installed, download "FLIP 3.4.7 for Windows (requires Java Runtime Environment)".
If you do not have a JRE yet, download "FLIP 3.4.7 for Windows (Java Runtime Environement included)" instead.
Note that, from time to time, the version number of FLIP will increase, but I will not update the text of this post to reflect that.

To start each download, click the icon next to its description text on the download page.

I've got it to work.

[Matthias_H]

Sorry for the hassle. Other products are easier to update; I guess it takes more than a part-time wannabe engineer (read: me) to come up with more elegant and usable solutions. Glad to hear you got it to work now.

[zem]

I am wondering if I have a problem with the firmware update.

I followed the steps in Windows7, but after installing the driver the device  was called AT90USB64 and not AT90USB646. I repeated the steps, but it did not change.

Does anybody know, if the name is just cut or does this lead to problems?

[Matthias_H]

So does it work as it should, besides the naming issue?

[DER_OSCA]

Hey there,

I am wondering if I have a problem with the firmware update.

I followed the steps in Windows7, but after installing the driver the device  was called AT90USB64 and not AT90USB646. I repeated the steps, but it did not change.

Does anybody know, if the name is just cut or does this lead to problems?

It seems like I have the same / a similar problem. I followed the steps in Windows 10 and got the same result.

So does it work as it should, besides the naming issue?

It did not work for me because the device named AT90USB64 was not listed in Flip. Does anybody know a solution for this issue?

[skaman]

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.