Hi Guys,
I have a bricked Netgear WGT634 V2 which I am wanting to unbrick and then try running OpenWRT / Kamikaze on it.
The specs of my WGT624 are :-
CPU :
ATHEROS
AR2313A-00
BA16185B
0604
TAIWAN
FLASH :
MX 8042072
29LV160ABTC-90
2J334400
TAIWAN
RAM :
SAMSUNG 419
K4S281632F-TC75
16 WQC4598A
SWITCH CHIPSET :
(STICKER)
U12H023T00
41000180-01
(CHIP)
88E6060-RCJ
A17567.4
0408 B00
TAIWAN
PCB BOARD :
U12H018
REV.1
19.1686.01
First thing I did was build a serial interface so that I could connect to the console. Upon the WGT624 booting, all I got through the serial console was :-
ar531x rev 0x00005850 firmware startup...
SDRAM TEST...PASSEDAtheros AR5001AP default version 3.0.0.43A
auto-booting...
Attaching to TFFS... done.
Loading /fl/APIMG1...Erroneous header readerror loading file: status = 0x610001.
Loading backup /fl/APIMG2...
Cannot open "/fl/APIMG2".Error loading file: errno = 0x388002.
Pressing escape during the boot process allowed me to get access to the VxWorks boot console. From here I was able to set the boot parameters to tftp. I was hoping that if I set the tftp function to receive the original Netgear firmware, then this would unbrick the WGT624. Unfortunately, all I got was :-
Attached TCP/IP interface to et0.
Attaching network interface lo0... done.
Loading...
Error loading file: errno = 0x610001.
I did a bit of research and found that I might need to boot from a .elf file. I found a .elf called "art", configured the tftp function to receive it and got the following output.
Attached TCP/IP interface to et0.
Attaching network interface lo0... done.
Loading... 19032 + 618848 + 105600
Starting at 0x80480000...boardData checksum failed!
Please check the ethernet cable on port 1!
Failed to attach to device etAttaching interface lo0...done
List of bridge ports not specified! -
Please set the bridge configuration parameter BRIDGE_PORTS.
This must a list of comma-separated device name and unit number pairs.
For example: "fei0,fei1,elPci0"
portsStringParse failed!Adding 3836 symbols for standalone.
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)0x
80fffdf0 (] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]] tRootTask
): Can't attach unknown device ]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]] et
(unit 0]]] ]]]]] ]).
]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version VxWorks5.4.2
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-2001CPU: Atheros AR5001AP default. Processor #0.
Memory Size: 0x1000000. BSP version 1.0.
/fl/ - Volume is OK
-> Starting ART Client...
Waiting for connection from Host
->
This .elf art file is apparently meant for a D-link DWL-2100AP (which shares the same cpu as the WGT624) which I am guessing is why a few errors are reported. Once at the shell, I have access to a whole lot of commands. Doing a directory listing, I can see the problem I have.
-> ll
-rwxrwxrwx 1 0 0 3178 Nov 14 2006 apcfg
-rwxrwxrwx 1 0 0 5520 Nov 14 2006 NVRAM
-rwxrwxrwx 1 0 0 0 Dec 24 00:00 apimg1
-rwxrwxrwx 1 0 0 3179 Jul 31 2004 apcfg.bak
-rwxrwxrwx 1 0 0 27126 Nov 14 2006 config.dbm
-rwxrwxrwx 1 0 0 50 Nov 14 2006 vpn.dbm
value = 0 = 0x0
The boot file apimg1 is empty. No worries I think to myself, I'll just copy the file from a working WGT624 and copy it across to my bricked WGT624 using a ftp command. I try to use some of the network commands to test the ftp function, but they all fail with an "undefined symbol:" error message. I'm guessing that the ethernet module is not working properly with this .elf file. I managed to find a second .elf file called "openwrt-atheros-2.6-vmlinux.elf". I reconfigure the tftp function to boot from the new .elf file, but receive this error message when it tries to load it.
Attached TCP/IP interface to et0.
Attaching network interface lo0... done.
Loading... 2530016
Starting at 0x80274000...Instruction Bound Exception
Exception Program Counter: 0x80144274
Status Register: 0x1000c000
Cause Register: 0x00800008
Access Address : 0xfff97fd7
Task: 0x80fca000 ""
80274950: 80279e5c (0, 1, 1, 0)
80279e80: 80278148 (0, 80062fe0, 0, 0)$0 = 0 t0 = 802915e4 s0 = 80290000 t8 = 0
at = 1000c000 t1 = 0 s1 = 80261fb0 t9 = 0
v0 = 0 t2 = 80290000 s2 = 80fc9fb8 k0 = 0
v1 = 8026461e t3 = 80290000 s3 = 80778730 k1 = 0
a0 = 802645e0 t4 = 802a0000 s4 = 0 gp = 80260000
a1 = fff97fd7 t5 = 0 s5 = 0 sp = 80261f70
a2 = 1 t6 = 83a074 s6 = 0 s8 = 0
a3 = 0 t7 = 0 s7 = 0 ra = 80279e88
divlo = 9999999a divhi = 1 sr = 1000c000 pc = 80144274
I'm now currently stuck and can see only two options from here. 1, build a jtag cable and copy the flash memory from a working WGT624 to my bricked WGT624 or 2, build a linux kernal for the WGT624 in .elf format so that it will boot via tftp and allow the network side of things to work. I have no experience in doing either, but like the idea of the 2nd option as it would help other people who have bricked their WGT624's or want to install alternative software to replace the Netgear system.
Can anyone offer me some advice or point me in the right direction please?