RV320 Firmware Upgrade Failure

[jasonreg]

I tried to upgrade my RV320 Router's Firmware today - did not go well.  I am left with a router with a Solid DIAG light and a flashing PWR light.  This condition is described in the release notes for the upgrade as a corrupted bin file. 
 
The solution is to rest the router and use a tftp put command from a cmd line prompt.  What I am getting is a "timeout occurred" and a "connect request failed" message.  This is a Windows 8.1 PC connected directly to LAN 1 port of router.  Have tried several times and no luck.  What am I missing?

 

[RAL]

Check out the discussion in this thread on Cisco's web site.  Note the comment from one user about the alternate tftp client working ( from  http://tftpd32.jounin.net/ ), while the normal windows tftp command did not.

 

[wkearney99]

I've run into issues with tftp on windows wouldn't work for some devices.  Never did figure out why, it was usually more effective to just spin up a linux machine (like from a Live CD or USB drive) and use that instead.
 
Now, did you upgrade for a specific feature/bug called out as being part of the new firmware?  Or did you just upgrade because it was a newer version?  And took a perfectly good piece of geared and bricked it...  Heh.  
 
Been there, done that, and have learned to not upgrade without there being something cited in the release notes as making it worth the gamble...

 

[jasonreg]

@RAL - Thanks yes I had found that but frankly I cold not figure out the utility for the alternate method.
@Bill - was very worried about that in fact.  I was actually trying to resolve upload speed (not getting what I should).
 
In any case, I did find something which worked so I will share for the next one: 

1. I opened two separate cmd prompts with admin access. Change directories to where the bin file is saved or save the bin file to the Windows\System32 file
2. In first cmd window typed PING -t 192.168.1.1 but did not press enter
3. In second cmd window typed tftp -i 192.1698.1.1 PUT RV32X_FW_v1.1.1.19.bin but did not press enter
4. Pressed enter on first window, then rapidly pressed enter on second window

Firmware uploaded to device on first try (though the site I found this on said it could take a few tries) - took about 10 seconds, router rebooted and I am now configuring it.  Let's hope after all this it actually does something for me!
 
Moving on!

 

[wkearney99]

yeah, there's sometimes a bit of voodoo behind the scenes with how arp entries and tftp sessions interact.  It's all supposed to happen 'automagically' with modern devices, but tftp and the reasons for using are rooted firmly in the old days when everything required a lot more configuring.  Glad to hear you're making progress.  Bricking the office gear on the weekend is never fun...