OpenWrt Forum Archive

Topic: Curiosity did not kill the cat but my ASUS WL-500g deluxe

The content of this topic has been archived on 25 Mar 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

A few days ago i had the (dumb) idea to test the 2.6 build from the current development branch
on my ASUS WL-500g deluxe.

The result is a now bricked wl-500gx.
But as you can see on the dump from the serial console, the bootloader seemd to be intact till the first reboot.
Since then NOTHING happens on the serial console anymore.
All i got when i do a power cycle ist a shot light up on the network leds LAN1-4 and WAN
POwer and AIR did not even light up.

Seems the flash including the bootloader is totally erased or corrupted.

The deluxe unit seems to lack a JTAG Port.

So does anybody have an idea what else can be done to unbrick the unit .
Probably some hints whether and how it ist possible to add a jtag port.

anny suggestions more than welcome

this is what i got on my console:

---------------
root@OpenWrt:/tmp# mtd -e linux -r write openwrt-brcm-2.6-jffs2-4MB-v0.9-b200509
21_7.trx linux
Writing openwrt-brcm-2.6-jffs2-4MB-v0.9-b20050921_7.trx to linux ...
Unlocking linux ...
Erasing linux ...
Unlocking linux ...
Unknown INCOMPAT nodetype F1C8 at 00170AB4
jffs2_read_inode(): No data nodes found for ino #312
Bummer, could not run '/sbin/halt': Input/output error
The system is going down NOW !!Node CRC 3b21bf2b != calculated CRC dd90d846 for
node at 001c7e70

Sending SIGTERM to all processes.
Please stand by while rebooting the system.
Restarting system.
Please stand by while rebooting the system...


CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: ¤­ 12¤ë3 20:46:15 CST 2004 (root@PaNLinux)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.

Initializing Arena.
Initializing Devices.
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 1.3.2.0
rndis0: Broadcom USB RNDIS Network Adapter (P-t-P)
CPU type 0x29007: 200MHz
Total memory: 0x2000000 bytes (32MB)

Total memory used by CFE:  0x80300000 - 0x80436CF0 (1273072)
Initialized Data:          0x803311B0 - 0x80333540 (9104)
BSS Area:                  0x80333540 - 0x80334CF0 (6064)
Local Heap:                0x80334CF0 - 0x80434CF0 (1048576)
Stack Area:                0x80434CF0 - 0x80436CF0 (8192)
Text (code) segment:       0x80300000 - 0x803311B0 (201136)
Boot area (physical):      0x00437000 - 0x00477000
Relocation Factor:         I:00000000 - D:00000000

Device eth0:  hwaddr 00-11-D8-70-1D-88, ipaddr 192.168.1.1, mask 255.255.255.0
        gateway not set, nameserver not set
Rescue Flag disable.
Reading :: TFTP Server.
Failed.: Timeout occured
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3732 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000

--> unit dead !!!!
----------------

cheers

Hey,

thanx for the answer,

BUT there is NO CFE anymore.

When i switch the power on
there is NO output on the serial console
no possibility to ping the unit

:-(

(Last edited by mmaexx on 26 Sep 2005, 14:16)

mmaexx wrote:

A few days ago i had the (dumb) idea to test thttp://openwrt.org/forum/viewtopic.php?pid=12829#p12829he 2.6 build from the current development branch
on my ASUS WL-500g deluxe.

From where you got the idea that you can use 2.6 for Asus WL500dx?!
Very bad idea. The flash driver is not ready for Linksys WRT54GS/G or any other model than Netgear WGT634u.

mmaexx wrote:

The result is a now bricked wl-500gx.
But as you can see on the dump from the serial console, the bootloader seemd to be intact till the first reboot.
Since then NOTHING happens on the serial console anymore.
All i got when i do a power cycle ist a shot light up on the network leds LAN1-4 and WAN
POwer and AIR did not even light up.

Seems the flash including the bootloader is totally erased or corrupted.

That is the reason, we call the tree: DEVELOPMENT TREE. If you do not communicate with the developers, you should not use any
DEVELOPMENT version on your router.

Get a new unit and do not play with stuff you do not participate.

(Last edited by wbx on 26 Sep 2005, 22:03)

wbx wrote:

From where you got the idea that you can use 2.6 for Asus WL500dx?!
Very bad idea. The flash driver is not ready for Linksys WRT54GS/G or any other model than Netgear WGT634u.

From nowhere - that's why i called it a bad idea ;-)

wbx wrote:

Get a new unit and do not play with stuff you do not participate.

Well i did in no way acuse you of anything.
You all do great work and this was definitely my fault.
It  was not my intention to blame you of anything.

But i guess the question if it is possible to add a jtag connector to a wl-500gx
IS of common interest.

BTW i know i use the Development branch
        i know what a development branch is
        i know of the risks
        i already once offered to participate but obviously no one was interested
       
BTW a ASUS is a nice Brick much nicer to put it an top of you letters than a linksys :-)

mmaexx wrote:

But i guess the question if it is possible to add a jtag connector to a wl-500gx

It's currently _unpossible_ to get a JTAG working on the Asus WL-500g Deluxe.

It even don't have any pin outs from the processor the the JTAG adapter.

mmaexx wrote:

A few days ago i had the (dumb) idea to test the 2.6 build from the current development branch
on my ASUS WL-500g deluxe.

The result is a now bricked wl-500gx.
But as you can see on the dump from the serial console, the bootloader seemd to be intact till the first reboot.
Since then NOTHING happens on the serial console anymore.
All i got when i do a power cycle ist a shot light up on the network leds LAN1-4 and WAN
POwer and AIR did not even light up.

Seems the flash including the bootloader is totally erased or corrupted.

The deluxe unit seems to lack a JTAG Port.

So does anybody have an idea what else can be done to unbrick the unit .
Probably some hints whether and how it ist possible to add a jtag port.

anny suggestions more than welcome

this is what i got on my console:

---------------
root@OpenWrt:/tmp# mtd -e linux -r write openwrt-brcm-2.6-jffs2-4MB-v0.9-b200509
21_7.trx linux
Writing openwrt-brcm-2.6-jffs2-4MB-v0.9-b20050921_7.trx to linux ...
Unlocking linux ...
Erasing linux ...
Unlocking linux ...
Unknown INCOMPAT nodetype F1C8 at 00170AB4
jffs2_read_inode(): No data nodes found for ino #312
Bummer, could not run '/sbin/halt': Input/output error
The system is going down NOW !!Node CRC 3b21bf2b != calculated CRC dd90d846 for
node at 001c7e70

Sending SIGTERM to all processes.
Please stand by while rebooting the system.
Restarting system.
Please stand by while rebooting the system...


CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: ¤­ 12¤ë3 20:46:15 CST 2004 (root@PaNLinux)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.

Initializing Arena.
Initializing Devices.
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 1.3.2.0
rndis0: Broadcom USB RNDIS Network Adapter (P-t-P)
CPU type 0x29007: 200MHz
Total memory: 0x2000000 bytes (32MB)

Total memory used by CFE:  0x80300000 - 0x80436CF0 (1273072)
Initialized Data:          0x803311B0 - 0x80333540 (9104)
BSS Area:                  0x80333540 - 0x80334CF0 (6064)
Local Heap:                0x80334CF0 - 0x80434CF0 (1048576)
Stack Area:                0x80434CF0 - 0x80436CF0 (8192)
Text (code) segment:       0x80300000 - 0x803311B0 (201136)
Boot area (physical):      0x00437000 - 0x00477000
Relocation Factor:         I:00000000 - D:00000000

Device eth0:  hwaddr 00-11-D8-70-1D-88, ipaddr 192.168.1.1, mask 255.255.255.0
        gateway not set, nameserver not set
Rescue Flag disable.
Reading :: TFTP Server.
Failed.: Timeout occured
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3732 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000

--> unit dead !!!!
----------------

cheers

Today I started working on 2.6 for brcm boards again, and flashed my WRT54GS v.1.0 with a new image.
I can't believe that the box is dead. I still can push "strg-c" and get into CFE. Same should be possible on your router.

Why CFE can't be overwritten?

long story:

CFE on Asus WL500g deluxe is 256 kb in size. CFE on Netgear WGT634u is 364 kb in size. CFE on Netgear use the ELF binary format to
load the linux kernel. (more exactly in our case, the LZMA-Bootloader, which finally extract and load the LZMA compressed kernel)

The LZMA bootloader in front of the snapshots are in ELF format. Asus WL500g deluxe use TRX format to find the LZMA bootloader.

That is the reason it stopps at   Starting program at 0x80001000, because the CFE bootloader on Asus do not recognize ELF.

BUT, if OpenWrt never starts up, it can't use the mtd tool to accidently erase any areas like CFE. I think you should check your cables.

Serial output should still work. Otherwise send me the "dead" box.

The discussion might have continued from here.