[akcam2006]

I used the very well written procedures from there: http://jozerworx.com/tutorials/wre54g/default.htm
It was after completing step 8 in section 4 using “dd-wrt.v24_micro_generic.bin” that the device stopped responding.

I have tried using the following pin outs from page two of this forum but they do not seem to be working.

O O O O left to right: +3.3v +3.3v grnd grnd
O O O O O ttyS0 output, unknown, unknown, ttyS0 input, unknown

I’ll recheck my solders and give it another try to see what happens.
Thanks for trying to help.

[dvlad666]

Sorry if thais offends you, but
Are you sure you used proper RS232 device? I.e. the one that's working and has 3.3-5v levels. WRE is not capable of communicating directly with PC's COM port!

[akcam2006]

Nope not offended at all and yep I am sure. I used the same setup on a couple of my other projects and it worked perfectly.

I just checked all my solders and everything seems to be correct yet when I run hyperterminal and get everything fired up nothing is received.

[dvlad666]

Have you played with bitrate/stop/parity bits?
Afaik that should be 9600 and not any flow control

[akcam2006]

Yep, I have played with just about every setting I could think of. Please keep the questions comming I'm sure you will ask one I have tried.

[gallo]

i have a serial connector port that i want to solder in place on the wre54g and i have an older laptop with a db9 connector on it so i can hook up the wre54g. my first question is the orientation of the connector that i am placing on the pcb. i looked at the beginning of this thread but am having a hard time figuring it out. next step is after i add the serial port and connect it to the laptop what do i do to reflash the original firmware back in to try and get it back to life. can someone please post a very detailed explaination or point me in some direction that has all the info.
Please help.
TIA.

[tech_fox]

Having read this topic I am a bit confused.
Has it been possible to connect using the internal connections and reflash the WRE54G.
I have a bricked WRE54G V1 as a result of applying the files listed in the database for this model.

I am keeping my fingers crossed.

[SparksCapone]

dvlad666 or akcam2006,
Did you ever manage to get your unit unbricked?

I am in a similar situation, followed the guide made by Jozer99, had the initial DD-WRT file flashed and running, then updated to the recommended dd-wrt.v24_micro_generic 14896 build recommended in the database at http://www.dd-wrt.com/routerdb/de/download/Linksys/WRE54G/1/dd-wrt.v24_micro_generic.bin/3746

After the 30/30/30 reset the router was bricked. I tried additional resets to make sure, but nothing helped.

I have since "serial-ed" into the router and get the following:

CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Mon Apr 12 17:57:52 CST 2004 (vlinux@Test)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.

Initializing Arena.
Initializing Devices.
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.50.21.0
CPU type 0x29007: 200MHz
Total memory: 0x2000000 bytes (32MB)

Total memory used by CFE: 0x8032BA00 - 0x80430F00 (1070336)
Initialized Data: 0x8032BA00 - 0x8032DB50 (8528)
BSS Area: 0x8032DB50 - 0x8032EF00 (5040)
Local Heap: 0x8032EF00 - 0x8042EF00 (1048576)
Stack Area: 0x8042EF00 - 0x80430F00 (8192)
Text (code) segment: 0x80300000 - 0x80309420 (37920)
Boot area (physical): 0x00431000 - 0x00471000
Relocation Factor: I:00000000 - D:00000000

Device eth0: hwaddr 00-90-4C-60-04-00, ipaddr 192.168.1.245, mask 255.255.255.0
gateway not set, nameserver not set
Boot program checksum is invalid
Reading :: Failed.: Error
CFE> ^C
CFE>

I have cleared the NVRAM area several times and rebooted with the same outcome.

I have read the Peacock thread, and the Serial Recovery page ( http://www.dd-wrt.com/wiki/index.php/Serial_Recovery )
but since this unit does not have an Ethernet port, I am unable to get tftp to connect.

I have also read the CFE pdf file at
http://melbourne.wireless.org.au/files/wrt54/cfe.pdf
and it seems there should be a way to use the Flash or possibly the Load command to write a new firmware.

So my questions are:
Is it possible to send the firmware to the router over the serial connection using CFE? If so, how?

If not, does anyone know how to either add an Ethernet jack to this unit, or possibly an SD card hooked to the GPIO ports?

I tried to find a pinout for the BCM4712 to see how hard this would be, but all I can seem to find is the 2 page product press release.

Any help at all would be greatly appreciated, thank you in advance!

[desiromeo]

Hi guys, i was fortunate enough due to forgetting to do the 30/30/30 reset after flashing 14896, that i still have my wre54g working....though it doesnt seem to be very stable...I read on the wiki that:

[desiromeo]

[desiromeo]

Has anyone tried running a micro version past 14896???

[rchadwick]

Hey Everyone. I followed the Jozerworx tutorial pretty much exactly, and I now have build 13064. The web server seemed to keep crashing, but I increased the CPU from 200MHz to the next highest notch, and it seems more stable now. A few questions for those that know:

1) What's the best build for this? I used the build Jozerworx used (13064), as I figured that would work. Should I stick with it?

2) Do I have to do anything in NVRAM to tell DD-WRT about the lights and reset button?

[desiromeo]

You could try 14896 from the router database...might be more stable...but DO NOT do the 30/30/30 reset after or you will brick your router like everyone else...or you can be a real trooper and try 14929 micro generic and let me know how it goes...lol.

Im running 14896 @ 252mhz and after a while im unable to reach the webgui but am still able to reach any webpage i want...so its still functional so i dont care too much, just cant reach the webgui for a while. But that happened even running @ 200mhz if not more...

[rchadwick]

Thanks for the response. Actually, I did the 30/30/30... Guess I was just lucky. The Web GUI is disappearing on me as well, but it's really annoying me. I thought raising the frequency did it. It helped, but it still happens. Must be something with the WRE instead of the firmware. Weird.

[rchadwick]

Well, I haven't bricked it yet, but I can't configure it either. In the process of setting it up to be a repeater, at some point it freezes, and the only way I can get it back is to hold the reset button for 10 seconds, which resets everything back to defaults. I guess I'll have to try 14896.