Netgear → Fried my RT314 -help??

Long story short -- wanted to down-rev my RT314 from 3.25 firmware to 3.22 because of a dyndns registration issue (it simply didn't work). Decided to use the fancy new web interface in 3.25 to upload a .bin -- selected the 3.22 bin, the web page told me to wait a few minutes then connect to the router. 10 minutes later all the lights on the router were solid - now a hypertrm session via serial cable produces the following screen (and NOTHING else):
-----
Bootbase Version: V2.03 | 1/15/2001 15:47:45
RAM: Size = 4096 Kbytes
FLASH: Intel 8M
-----

No "press a key to debug", no ability to issue 'at' commands to up a new ROM.

Any ideas?

I did the same thing earlier this week. I saved the message Netgear sent as an answer. Worked for me. Good luck.

"Subject: FW: Directions for the Hyperterminal for the RT314

You will need a serial cable to enter the serial Manager interface to
upload the 314v324.bin and romfile0.311.

1. create a Hyperterminal session with the router (either com1, com2, com3
or com4 and bits per second is 9600.

2. once the hyperterminal session is created and opened, unplug the power
from the router for 5 seconds and repower the router. Now you will notice
the sequence of events occuring on the hyperterminal display. When prompted,
hit any key to continue into debug mode. Now you will be in debug mode. Now type 'atur'. This will say something like uploading or working, but it is not so go straight to transfer>send file, choose to use xmodem for the protocol and then point it to the 314v324.bin file that you unzipped from the firmware file.

3. Then you will want to type in atur3 and do the same thing by going to transfer>send file and then using xmodem and this time pointing it to the rom file.

4. Once this is done, it could take about 10 mins, type in atgo to restart the router.

5. Now the password has been reset back to '1234' and the IP address for the
router has been set to '192.168.0.1' and it is set back to factory defaults"

I was going to suggest this but it appears from the message above that the router never gets to the point where you can press a key to get into debug mode. If you can't get to that point, you can't do much.

Still worth a try cycling power and starting fresh on the serial port. Maybe it'll respond. Generally speaking the serial port is far more reliable.

JS

Jsimmons -- You are correct. The router never gets to the point of "Hit a key to debug." In my journeys searching around for an answer (because netgear's tech support sucks) I found one post that suggested killing the power for five minutes and when it's turned on, the router will respond with a C^C^C^C^ telling me that it's ready for an Xmodem serial transfer. I tried this, but my router now spits back garbage (random ASCII characters) and when i try an upload I have no luck.

Another router's on the way, wondering how long it will take me to kill this one

Netgear *REALLY* needs to implement something like a "insert paperclip here to reset the router to factory shipped ROM/settings" to alleviate these problems.

Oh well, one can only dream...

said by brone:

---

my router now spits back garbage (random ASCII characters) and when i try an upload I have no luck.

---

Sounds like a baud rate mismatch. Try different settings on your computer.

As Bobsled says... First set your term emulator to 9600 baud, No parity, 8 bit data, and 1 stop bit (this is often referred to as 9600-N-8-1) and try powering the RT up. If you get garbage on the term emulator, power down, change the baud on term emulator up to 19200-N-8-1 and power up the RT again. Keep upping the baud rate up to 38400, 57600, then 115200 until you see the real boot messages. The default factory setting for the console port is 9600, but if it got changed along the way and you don't know what it is, you just have to use trial and error. Good luck.

JS

If im not mistaken... once you power down the router, it defaults back to 9600? So stabbing in the dark is of no consequence? Sounds like either he has ansi or mismatched baud rate lower or higher than 9600! Then there is the last option, a fried chip?

no, the baud rate is saved in flash and will not change after a power loss.

said by SYNACK:

---

no, the baud rate is saved in flash and will not change after a power loss.

---

Synack....

To which and who was this reply to??

Sorry, I should have been clearer. We are both right

There are two ways to change the baud rate:

(1) If you simply change it in debug mode with ATBAx, it will not be saved and will revert back to default once you cycle power. I assume you were referring to this.

(2) If you change the baud rate in menu 24.2.2, it will be saved in flash ROM and will be retained forever, or until you change it.

I messed up by ftping 3.25's config file first, and now I can't do anything. I'm trying connecting through a serial port com2 9600baud. The test light just keeps blinking. Any ideas? Hyperterminal says its connected and just has a blinking line.

Reboot your router with hyperterminal connected and watch for messages. If it says press enter to go to debug do so.

Your baud rate is wrong.

TO change in hyperterminal, make sure to "disconnect":

See HERE for DrTCP's instructions

(Hyperterminal has problems changing rate while a connection is active.)

Now I cant even recreate those funky characters. I've tried the 9600 baud thing and am positive I'm connected at 9600 before the routers turned on.

I forgot to mention this, I've got a RT311.

Does Hyperterminal actually say you're connected? I think I had to hit return to get it to connect, then power-on the router.

It's gotta be a baud rate mismatch.

StuartB-

Sounds like your router is fried. Go get an RMA from Netgear. I just did the same, waiting to see how long it takes me to fry my second..

Actually, it was the cable, hurrah

Well now the router(RT311) says when I type atur:

atur
Starting XMODEM upload (CRC mode)....

Then I goto send file, and it doesnt respond, IM using Xmodem protocol. Any ideas?

Heh I should smack myself, I had Zmodem selected, but all is well now, much thanks to your replies