Hello.
My Linksys WRT54G v3.1 just went dead after I tryed flashing WhiteRussian. Now when I power it up - power led just blinks blinks and blinks and nothing happend. Im trying to recover using Serial Console I just soldered it,but the only things I saw were:

Welcome to minicom 2.1

OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Nov  7 2004, 13:39:16.

Press CTRL-A Z for help on special keys

CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Fri May 27 13:33:52 CST 2005 (root@localhost.localdomain)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.

Initializing Arena
Initializing Devices.

No DPN

After No DPN nothing else is shown.
Any Ideas whats wrong with it and how to recover it?

btw. I also tryed shorting pins on flash but also didnt work - dunno if it didnt because I didnt have anything good to short those pins or I did something wrong....

(Last edited by crashev on 7 Sep 2005, 15:43)

strange. Can you try to reset the router, holding down reset button on boot?

Otherwise you need jtag. If you did not get it repaired, send it to me for testing. I do not think it is going dead because of flashing OpenWrt...

Holding down reset button changes nothing - i tryed both resets -  its v3.1 version with reset on back and behind cisco logo.
wbx - please contact me

Hi, I have the same problem as crashev.
I tried to flash the original (!) Firmware back to my WRT54G v2 via the Webinterface. Everything just get fine. After the "...successfully flashed" message and a reboot my router was dead

From now on if I turn power on, the ether-leds flash for a second and then the power led is blinking all the time. The ether-leds show the connection status and are blinking if Data is sent (thus working correct). But the router doesn't react to the reset (nothing happens if I push the button, just power led is blinking).
I tried the tftp method also with shortcut pin 15/16 or 16/17 (DMZ led then is on and power led is blinking) of the flashmodule with no effect. the tftp-client (Windows and Linux) can't get a connection and router is not ping-able.
As yet I did not try to "enable" the serial console of my router. Maybe this can help?
Is it a hardware fault?

What else could I try?

thx,
Nick666

(Last edited by Nick666 on 9 Sep 2005, 23:54)

just a wild guess, if 3.1 has added any new partition scheme and is saving important data in an area, which openwrt overrides it, then you can kill the router. We need a unmodified wrt 3.1 to check with original
firmware and a serial connection. If anyone like to provide hardware, please contact me. (wbx@openwrt.org)

Ok so It look like something was overwritten.
Because Im my case it was like this - firmware was flashed correctly but the router went off when firstboot script was run....
So it has overwritten many important data since even serial console doesnt work.....

Ok - what can we do about it - we need oryginal JTAG-dumped firmware and then further we need support for v3.1 in OpenWrt....?

I've installed open-wrt on hw v3.1 just fine. fwiw with v3.1 hw I usually flash hyper-wrt first then reflash because I usually get "update are failed" otherwise.

Also re grounding the flash, the one brick that I did have (dd-wrt not open-wrt) I had to short to the antenna ground as shorting between pins didn't work.

- DL

Had a similar situation here yesterday, with the box hanging at 'no DPN' in the beginning of booting.
The cause here was permanent shortage between the leads of the flashchip due to excess pressure while shorting the leads 15-16 while connecting power. The solder is a soft material and the distance between leads very small.
Used a magnifying glass and a Stanley knive blade to remove solder from between the leads .....
After that the box booted normal.

Hi,
I get mine back to live Here what I had done (wrong):
- WRT54G V2 did nothing but flashing power LED
- no chance to upload the firmware with tftp. Tried different clients on win and linux.
- shortcut pin 15 with pin 16 of the flash method, DMZ-LED turned on but no chance with tftp/ping.
- BUT: you have to shortcut pin 15/16 to ground (!) I did this by "sticking" a tip from my multimeter between pin 15/16 and shortcut it with the antenna adapter (grounded). This is also logical because pin 15/16 are address lines and by this method I force them to logical 0. You can also do this only pin 15 OR 16 but it's much easier to "stick" something between two pins. Pin 17 is also a address line and works the same way.
- WRT54g booted up and DMZ-LED blinked slow (~5s interval). It was now pingable and I could upload a firm like described many times before!
- if everything gets right, the device reboots automatically and load the new firmware. This didn't happend to me at first (the device did not reboot and after a powercycle the device just hangs like in the beginning). I first had to make a hard-reset (holding down the reset-button for some seconds) when the device was in the failsafe mode (!!) (this seems to overwrite some variables) then upload the firm via tftp.

hope this helps...

(Last edited by Nick666 on 17 Sep 2005, 14:04)

doddel: yeah it was very likely that I did what u did ,but I looked with magnifing glass on it and it doesnt look shorted... a little bit damaged but not shorted hmmm... any other ideas how to fix this flash paths?

btw. do you know what serial consol shows when u short pins - ground them and tftp server starts?
I also tryed again shorting pins to the antenna with no efect - still blinking power and hangs on No DPN in serial console....

(Last edited by crashev on 18 Sep 2005, 19:53)