WL-500gP ... probably really dead!?
Hey guys!
I got myself a bricked router (don't know how it was bricked exactly because I received it in this state from its former user)... still I wonder if someone has an idea as to what course of action to take when the following serial console output is the only thing that the router will output:
----------------------------------------------------------------------
CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: ¤@ 6¤ë 12 16:31:07 CST 2006 (root@localhost.localdomain)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.
Initializing Arena
Initializing Devices.
rndis0: Broadcom USB RNDIS Network Adapter (P-t-P)
CPU type 0x29006: 264MHz
Total memory: 33554432 KBytes
Total memory used by CFE: 0x80800000 - 0x8089B670 (636528)
Initialized Data: 0x808317E0 - 0x80833EC0 (9952)
BSS Area: 0x80833EC0 - 0x80835670 (6064)
Local Heap: 0x80835670 - 0x80899670 (409600)
Stack Area: 0x80899670 - 0x8089B670 (8192)
Text (code) segment: 0x80800000 - 0x808317E0 (202720)
Boot area (physical): 0x0089C000 - 0x008DC000
Relocation Factor: I:00000000 - D:00000000
Device eth0: hwaddr 00-XX-XX-XX-XX-XX, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Null Rescue Flag.
Boot program checksum is invalid
Hello!! Enter Rescue Mode: (Check error)
Reading :: TFTP Server.
Failed.: Timeout occured
Reading :: TFTP Server.
Failed.: Timeout occured
[this continues forever]
----------------------------------------------------------------------
Additional notes:
1) Although it seems that an IP address is assigned to eth0 I can not ping the router (of course I have set a static IP in the same subnet on the computer I'm trying to connect from)!
2) The MAC address in the console output above has been altered for this posting, in real life looks like it should.
2) Recovery mode: same output except that it says "Hello!! Enter Rescue Mode: (Forced!)"
3) Pin shorting has not changed anything (Pin 9)
4) Neither TFTP or the ASUS Utility can connect to the router, not even in forced recovery mode.... probably because the router can not even be pinged (cp. point 1).
... sombeody got an idea how I can get some life back into the device?
Warning 2 bricked routers
Hello all,
I managed to brick two brand new wl500gp routers, just call me dum and dumer :). If anyone wants them just drop me a email and i will give you the address so you can arrange pickup (Brisbane).
I strongly recommend anyone considering using the wl500gp with alternative firmware, DD-WRT, OLEG, or OpenWRT to stick with the linksys hardware. These WL500's are technically better but the units are bugger, in that hardware reset and update process do not work very well at all.
I have tried all the methods suggested, reset, Firmware restoration, etc, with the expection of adding a serial port, which is just not worth my time!