And mentioned when connected via the cable, PUTTY started and connected, but no power on of the router - I have echo. see the letters I type.. (the same if I make a short circuit between Rx and Tx). When Power the router, the echo disappears. is it normal?
Sometimes people make the mistake of connecting TX on the cable to TX on the router, and RX on the cable to RX on the router. Double-check to make sure that TX on your cable is correctly connected to RX on the router, and vice-versa.
GND on the cable should be connected to GND on the router, of course.
Thank you! You are right - I have connected the wrong way after correction (Tx to Rx ) it works and I fixed the router )
@myname.
Could you Plesse tell me the system You are running. Win or Linux Which sSoftware did You use to recover?
Well, I used Windows 8.1 64 bit version but used virtual machine in order to install Win XP 32 bit. And use the DKU5 WinXP driver (you can find it in the google) for the cable and Putty for serial connect.
I have very similar problem with e3200 and dd-wrt.v24-23204_NEWD-2_K2.6_mega-nv60k, which after flashing over trailing version gave me half-bricked device. It responds to pings with ttl=100 though, so i thought there is still a hope. I tried to tftp it with original Linksys firmware (FW_E3200_1.0.04.001_US_20120410_code from linksys website) - doesn't work. Any any other dd-wrt.v24-23204_NEWD-2_K2.6 versions neither. And even dd-wrt.v24-19342_NEWD-2_K2.6_big-nv60k, which is from the same build as successfully installed over original Linksys version (at the very beginning) recommended in installation page - doesn't work either.
I think it's something wrong on the tftp stage. I've read than linksys routers require a password during tftp, so i put default "admin" into tftp Password line - still nothing (it uploads bin file successfully every time, doesn't matter with password or not, so i really not sure if it's necessary).
I noticed that after uploading the bin file, power led continues flashing while i wait required 2 minutes "while the new firmware flash configures itself" (and even 10-15, doesn't matter how long) and ping says
"Reply from 192.168.1.1: bytes=32 time<1ms TTL=100" - for all 2-15 minutes, before i do 30-30-30 hard reset as recommended. Is it a normal behavior? Or power led should stop flashing when the new firmware done configuring itself? I've never seen it completing, so i don't know.
Also, during 30-30-30 reset, ping shows:
General failure.
General failure.
...
Reply from 192.168.1.8: Destination host unreachable.
Reply from 192.168.1.8: Destination host unreachable.
then, at some point bootloader responds again with ttl=100:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=100
then Request timed out, and finally "Destination host unreachable".
I tried power down/up, it again shows bootloader respond with ttl=100, and then immediately "Destination host unreachable". Doest it mean that flash was not completed, or it's nvram problem, or what?
Also, am i missing something in tftp procedure (like password, etc)?
Posted: Thu Jan 02, 2014 19:47 Post subject: soldering to serial connectors
Hi!
How did you manage to solder the cables/pins to your router. in my opinion it is very trick and not so easy as it seems.
Any tips for that?
EDIT: Finally i managed to solder the cables. GND contact was the problem. The rest of the procedure was easy. Boomchakalaka
EDIT1: BTW i used a silabs CP2102 for only 2,24 euro within shipping costs
Is it normal? Or should it be some meaningful text, as router boots up? Please let me know what you see during boot.
I tried to do control-c as fast as i can, but no cfe> prompt so far. Is it related to the hyperterminal settings, "ASCII sending" may be, or "Emulation"? Which setting in the hyperterm did you use?
UPD1. I changed speed at the port settings to 115200, and finally got meaningful output! It goes pretty fast, but it says:
"CFE version 1.0.37 for BCM947XX, etc. "
and ends with
"TCP: Hash tables configured (established 2048 bind 2048)
Kernel panic - not syncing: Attempted to kill init!"
Ctrl-C so far doesn't get me to the prompt
Last edited by lugger1 on Fri Jan 17, 2014 0:12; edited 1 time in total
Is it normal? Or should it be some meaningful text, as router boots up?
It is normal if something is not connected correctly. You should see readable text. Check all connections again. See the serial recovery wiki. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Yes, i found that the garbage was coming because i set baud-rate to 56700, i changed it to 115200 and can see the meaningful output. But i can't stop it with ctrl-C. Is there a way to see if i really send something via putty (if ctrl-C really go through)? I tried to connect Rx to Tx wires and didn't see any echo in terminal. The wire itself is good, i checked it with ohmmeter.
after correction (Tx to Rx ) it works and I fixed the router 
