Bricked Buffalo WLA-G54C: Next Steps?

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Author Message
robsclone
DD-WRT Novice


Joined: 15 Jul 2010
Posts: 5

PostPosted: Mon Jul 19, 2010 1:03    Post subject: Bricked Buffalo WLA-G54C: Next Steps? Reply with quote
After successfully putting dd-wrt on a Buffalo WBR2-G54, I attempted to get it going on the WLA-G54C.

Steps:

Couldn't get tftp to work, so used the alternate method described in the Buffalo WBR2-G54/WLA-G54/etc wiki:

- used ddadder to modify dd-wrt.v24_std_generic.bin
- went through the Web interface, directed to new file, and had it update
- It started going, and then received error:

"An error has occurred during upgrade.
Rebooting...
If you want to continue configuration, please close browser software then execute it again."

Then it automatically rebooted, and it hasn't come back since.

Can not connect through tftp, telnet, web, or ping, through 192.168.11.1, 192.168.11.100 (read somewhere), or 192.168.1.1

Wireless LED no longer comes on, but Ethernet does when cable connected.

30-30-30 has been attempted many times.

It seems that the next thing to do is build some sort of serial cable, or try to short out pins in the chip. I took it apart (when apart, can see that the Wireless LED is faintly on) but to get below the miniPCI card there's some soldering to undo, and I don't want to touch that unless i know what I'm doing.

I found what may be a pinout for debricking here:
http://filer.case.edu/jkm26/img/Buffalo Airstation DD-WRT Mod.pdf

But I can't find enough info elsewhere to make it a doable project.

Does anybody know of any instructions posted to debrick this WLA-G54C? Searches have come up empty so far, though there was one thread from 2006 where people were debricking them, I just couldn't follow it.

Thanks for any direction or help with this issue!
Sponsor
zerofire
DD-WRT User


Joined: 20 Nov 2009
Posts: 93
Location: United States

PostPosted: Mon Jul 19, 2010 13:13    Post subject: Reply with quote
Buffalo routers have TFTP enabled after a few seconds after boot only and only answer to a specific IP for TFTP. Set your IP to 192.168.11.2 and issue a TFTP to 192.168.11.1 when the diag light comes up alone after all the lights come up once and go out.
_________________
Linksys WRT350Nv1 x1 DD-WRT v24-preSP2 14311-Not In Use
Linksys WRT54G2v1 x1 DD-WRT v24-preSP2 14311-Not In Use
Linksys WRT54G2v1 x1 Linksys OEM
Linksys EG008Wv3 x1
Linksys WRT54Gv3.1 x1 Linksys OEM
Linksys WRT54Gv5 x1 Linksys OEM
Linksys WRT54Gv6 x2 Linksys OEM
Linksys WRT54Gv8 x2 Linksys OEM
Linksys WTR54GSv1 x1 Linksys OEM
Linksys WRT160Nv1 x1 Linksys OEM
NetGear WNR834Bv2 x1 DD-WRT 25251
NetGear WG302v2 x1 Netgear OEM
Belkin F5D7230-4v1000 x1 Belkin OEM
Buffalo WHR-G300N x1 DD-WRT sp2
Buffalo WHR-G300N x1 Buffalo OEM
Airlink 101 AR430Wv1 x1 Airlink OEM
Cisco Catalyst 3548 Enterprise x1 Cisco IOS-Not In Use
D-Link DI-604vE x1 D-Link OEM-Not In Use
robsclone
DD-WRT Novice


Joined: 15 Jul 2010
Posts: 5

PostPosted: Mon Jul 19, 2010 13:50    Post subject: Reply with quote
zerofire wrote:
Buffalo routers have TFTP enabled after a few seconds after boot only and only answer to a specific IP for TFTP. Set your IP to 192.168.11.2 and issue a TFTP to 192.168.11.1 when the diag light comes up alone after all the lights come up once and go out.


Thanks for the reply!

Apparently the WLA-G54/C is a bit unique, it does not have a diag light and I've found in further research that it does not support TFTP, and the only way to update is through the web interface like I attempted.

Unfortunately, I'm a bit beyond the basic setup and need advanced help now, since after initial attempts it does not respond to any requests (TFTP, telnet, ping, web) on any of the default addresses.

Do you have any info or know where i may look for info on de-bricking Buffalos, specifically WLA-G54?
Eko
DD-WRT Developer/Maintainer


Joined: 07 Jun 2006
Posts: 5772

PostPosted: Mon Jul 19, 2010 14:05    Post subject: Reply with quote
It can be done with jtag only.
robsclone
DD-WRT Novice


Joined: 15 Jul 2010
Posts: 5

PostPosted: Wed Jul 21, 2010 1:16    Post subject: Reply with quote
Thanks for the reply, but that's a bummer. I think I'd rather put the $10 in parts towards another router rather than fixing this one and having it fail again.

Any idea what I may have done wrong in case anybody else finds this thread?

thanks again!
zerofire
DD-WRT User


Joined: 20 Nov 2009
Posts: 93
Location: United States

PostPosted: Wed Jul 21, 2010 6:43    Post subject: Reply with quote
It seams like it was a partial flash or a bad firmware. You would use JTAG to clear the memory locations with the settings and firmware. Then feed a OEM firmware from Buffalo to start over. It would also be possible to load DD-WRT instead of the OEM to try to bypass the flash part and see if the firmware mods were correct.

Eko is probably right about needing JTAG to fix that unit.

_________________
Linksys WRT350Nv1 x1 DD-WRT v24-preSP2 14311-Not In Use
Linksys WRT54G2v1 x1 DD-WRT v24-preSP2 14311-Not In Use
Linksys WRT54G2v1 x1 Linksys OEM
Linksys EG008Wv3 x1
Linksys WRT54Gv3.1 x1 Linksys OEM
Linksys WRT54Gv5 x1 Linksys OEM
Linksys WRT54Gv6 x2 Linksys OEM
Linksys WRT54Gv8 x2 Linksys OEM
Linksys WTR54GSv1 x1 Linksys OEM
Linksys WRT160Nv1 x1 Linksys OEM
NetGear WNR834Bv2 x1 DD-WRT 25251
NetGear WG302v2 x1 Netgear OEM
Belkin F5D7230-4v1000 x1 Belkin OEM
Buffalo WHR-G300N x1 DD-WRT sp2
Buffalo WHR-G300N x1 Buffalo OEM
Airlink 101 AR430Wv1 x1 Airlink OEM
Cisco Catalyst 3548 Enterprise x1 Cisco IOS-Not In Use
D-Link DI-604vE x1 D-Link OEM-Not In Use
nn5i
DD-WRT User


Joined: 18 Jun 2010
Posts: 263
Location: Tallahassee, FL

PostPosted: Wed Jul 21, 2010 12:07    Post subject: Reply with quote
I have never bricked a router -- not yet anyway -- but when I do, I will probably follow the following recommended procedure:

(1) Take router out on back patio.

(2) Place router carefully on the concrete surface.

(3) Strike router smartly with 20-pound sledgehammer. If you are a Judo practitioner you may kiai (emit a loud shout) while striking.

(4) Repeat (3) until frustration is eased.

By this process you may stop worrying about whether the consarned thing can ever be fixed. Laughing

_________________
Netgear WNR834Bv2 DD-WRT build 14311 nokaid (Primary)
Linksys WTR54GSv1 DD-WRT build 14896 mini with AutoAP (x2) -- cool!
Linksys WRT54Gv2.2 DD-WRT build 14896 mini with AutoAP -- cooler!
Netgear WNR834Bv2 DD-WRT build 14896 mini with AutoAP -- also cool.
Linksys WTR54GSv1 DD-WRT build 14311 std (Client bridge for Ooma voip phone)
Linksys WAP54Gv2 DD-WRT build 14896 micro -- haven't figured out a use for it.
jasper502
DD-WRT Novice


Joined: 24 Jul 2010
Posts: 4

PostPosted: Sat Jul 31, 2010 22:20    Post subject: I am in the same boat... Reply with quote
I followed the same procedure and got the same error message and I have a brick too.
yoshio_will
DD-WRT Novice


Joined: 23 Sep 2010
Posts: 2
Location: Japan

PostPosted: Thu Sep 23, 2010 16:10    Post subject: I am in the same boat too... Reply with quote
I followed the same procedure and got actually same result.

I opened enclosure and desolder mini-PCI card, and removed it.
Detach 4.7K register from JTAG pads and soldered wires with 100ohm register.

Connect it to pararell port, initiate jtag flashing with following:
tjtag3 -flash:wholeflash /nocwd /nobreak /fc:71

...it seemed work propery.
but it still no answer to tftp, http, ping.

I used distribution V24SP1 this time.
Next, I'll go with V23SP2 and post result here.
yoshio_will
DD-WRT Novice


Joined: 23 Sep 2010
Posts: 2
Location: Japan

PostPosted: Sat Sep 25, 2010 10:46    Post subject: My bricked brick is still bricky Reply with quote
I misunderstood about jtag flash..

My understand is:
CFE is bootloader, placed on Flash block 1, 2.
CFE is not contained in distributed dd-wrt .bin files.
Kernel is actual firmware and is placed on Flash block 3-32.
NVRAM contains settings and is not placed on Flash. (another device)

Is this right?

First, I flashed distributed .bin file using jtag.
(tjtag3 -flash:wholeflash /nobreak)
But this will write bin file to Flash block 1-32. CFE is overwritten.

Next, I got CFE file from Eko's post
( http://www.dd-wrt.com/phpBB2/viewtopic.php?p=43660 )
and flash this with -flash:cfe.
In prior to flash, cleaned other memory.(nvram, wholeflash)
After done it, flash distributed dd-wrt .bin file (V23 Generic) to kernel area (-flash:kernel).

As result, I can get answer to arp requests, but ping is still timed out.
I think that CFE is loaded and properly work, but because of some reason, kernel did not work.

I'm tired because kernel flash needs very long time (over 100 minutes!).
I wonder my jtag cable is too long (about 25cm) but I take rest first.
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum