exit151
DD-WRT Novice
Joined: 31 Jul 2011
Posts: 41
|
 Posted: Fri Sep 28, 2012 21:55 Post subject: WRT54gv2 brick verification request |
 |
Hey all.. Let me preface by stating a couple facts 
1. I've done this several times (have about 6 dd-wrt'ed routers, all wrt54g's around the house).
2. This unit was bought at a thrift store, new to me, but "arrived" in the condition it is in. While I'm fairly certain someone failed a firmware update, other than a visual inspection of the components (which I did) and a sniff test (for bad caps, overheated parts etc, which I also did) I don't know what was done to it previously, or if something internally "naturally" failed.
So here's what happened/happens..
I got it home and plugged it in. The power light flashes (and never stops). I performed the 30/30/30 reset. Same thing with the power light. Plugged into test PC, LAN light comes on.
Immediately I set out to do a brick test. I set my PC to a static IP (192.168.1.5). I opened up a cmd prompt and did the ping -t 192.168.1.1. Seconds after the router is plugged in, I do in fact get a ttl=100. It will go on forever (well, at least 5 minutes, this is important, read on).
So I thought, okay, time to tftp in. Downloaded the original firmware for said model from the linksys site (official release, again, no clue what is or was on there). Configured tftp for 99 retries, the proper IP, and unplugged, waited 30, plugged in, and counted to about 2 before trying to tftp.
That's where I get lost, and need help. I understand that there is finesse and timing involved. But no matter what my timing, I cannot get it to send the file.
When I start tftp to do it's thing, I lose my ttl, heck, I lose everything and only get request timed out. The router (seems) to just keep rebooting when tftp is running. I'll see about 6-8 ttl=100's, then about the same handful of "request timed out" msgs, it gives 2 hardware errors, and it just keeps repeating that loop (of proper ttl=100, rto, and he over and over.
The guide area under jtag and verifying it's necessary talks about getting specific msgs in the ping window, like a ttl=64, or cnstant req timed out / destination host unavailable msgs, but nothing specifically about a router whose msg alters back and forth.
Has anyone experienced this, or have any ideas for my next course of action? I've got the parts necessary for the jtag cable, just not the jtag software, which according to the same thread claims to be $5.. Also wondering if that would be the necessary solution, or if I should/could try the serial cable, as I do get the ttl=100's, which, from what I read indicates a working cpe. Just not sure why it goes to crap and reboots itself when tftp tries to make contact, and whether the same would happen via direct serial connection.. Don't have all the parts to make that (max232, unless I can scavenge one from something dead around the parts bin lol). Please advise
Tnx, Exit151 |
|
redhawk0
DD-WRT Guru
Joined: 04 Jan 2007
Posts: 10812
Location: Wherever the wind blows- North America
|
| Posted: Sat Sep 29, 2012 0:31 Post subject: |
|
Due to the age of the v2 units...first thing I'd check is the power supply.
My suspicion is its weak or rippling. Try another power pack...+12V @ 1A minimum....I've always used old PC power supplies and tap into the +12V line to test.
It could be that is the only problem here.
redhawk
_________________
I currently test dd-wrt on Asus, Buffalo, Linksys, and Netgear. Too many to list.
Looking for more test units (newer models) for the project...got a brick?...PM me to make a donation. (USA) A donation is not a debricking service....it is a way to "Give back" to the dd-wrt project.
I do NOT provide personal assistance through chat or phone....so please don't ask. |
|
exit151
DD-WRT Novice
Joined: 31 Jul 2011
Posts: 41
|
| Posted: Sat Sep 29, 2012 15:57 Post subject: |
|
| LoL I appreciate you're trying to help, but I really don't think you read my post, rofl. I well know how to tftp and have said tools. Please re-read the 1st post if you want to help, and explain why I am getting that result and why my CPE appears to be fine, yet I'm unable to tftp successfully. And why initiating tftp causes my router to seemingly reset itself, and why it pings just fine, when I don't do anything to it, rofl. That is, however a good canned response for some noob learning to do a firmware upgrade. |
|
