Posted: Thu Mar 31, 2011 4:39 Post subject: wrt350n v1.1 serial ttl not sure of how to set it up
I already tried to recover via the tftp method, and although I do catch a short time response from ping, ttl=100, I read the peacock thread multiple times, and every time the mini image transfers successfully (looks like it worked and recovered according to tftp) it still doesn't truly recover. Follows blinking power led in forever loop. I followed every step to a tee, and I have recovered this unit in the past when messing with different firmwares on it through tftp, so I am sure I know what I am doing.
I read a few other posts with people whom had the same issue, so anyway, I am desperate now, I soldered wires out to the serial ports (I found pics here and on openwrt and got the pinout) and I have a Serial TTL to USB which my friend had used in the past to recover a Bountiful with DD-WRT... so I know it works.
I double checked and all my solder connections are good (tested with multi meter).
I am using WinXP Pro and Serial is on COM3 by default, COM1 is available if needed.
I never used serial recovery before, and the readings here on the forums are a bit limited in that there is no written out good procedure, and not all in one place, bits and pieces of info are scattered on this.
Here is what I tried, did I do something wrong?
With everything connected (all 4 cables (VCC, Ground, TX, & RX), I checked and am quite sure its correct, I open putty, click on Serial (last option in Connection category) and set up as COM3, 115200 baud rate, DB is 8, SB is 1, Parity set to None, and Flow Control set to Xon/Xoff but also tried with it set to None as well.
I open the connection so it sits there now in the Main Session category, and then I power up the router. (Just to make sure as I understand I power the router from the power brick, but the serial connection also supplies 3.3v) is this necessary???
I see no output in the putty window, as from what i read I am supposed to press ctrl+c to interrupt the process. I just see nothing but the small green square.
Any input people??? I also ordered a jtag but it should arrive next week. Is my process wrong, what else can I try?
Posted: Thu Mar 31, 2011 5:00 Post subject: Re: wrt350n v1.1 serial ttl not sure of how to set it up
xtacydima wrote:
I never used serial recovery before, and the readings here on the forums are a bit limited in that there is no written out good procedure, and not all in one place, bits and pieces of info are scattered
There is a serial recovery wiki, with the important bits collected together. Link is in note 6 of the peacock.
Connect your tx and rx together (removed from router). Type on your keyboard and see if there is output on the screen.
If you don't have a working cfe, you will not get serial output, and will need to jtag. _________________ I fix "shortcuts". If you don't have time to read thoroughly, I don't have time to re-type what you missed.
I see where you were going with that, good idea I can't believe I didn't think of testing it.
Yes, what I typed on the keyboard was output in the putty screen. I am definitely confirmed now that my solder job was good and that the USb TTL device is working properly, as well as all settings are good in putty.
Guess I need to wait for arrival of my jtag cable, looks like a bad cfe.
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Thu Mar 31, 2011 20:57 Post subject:
hmmmm.
if you were getting a few ttl=100 when pinging it during power up, there is nothing wrong with the cfe.
Your serial problems are else where.
1st, disconnect the wires from the pcb. connect the tx wire to the rx wire. You may also have to use a battery to give the ttl adapter power if it is not powered by the usb port.
With tx and rx connected to each other, you key strokes should be echo'd in the terminal. If not, you have a problem with your adapter.
post a pic of what you are using for serial on the pcb.. if memory serves, there are 7 connections in a row, only 5 are used for the serial console (4 actually.. 1 is n/c)
I have some pics posted here somewhere when I was modding my 350 by puting in a 5ghz radio card.
In pic 1819, the serial is the 5 pin header on the right. Connections are from left to right: gnd, n/c, rx, tx, vcc _________________ [Moderator Deleted]
in my prev post I stated that yes, I got a repeat of what I was typing in my putty window off the keyboard, so my usb/serial connection is good. When router boots there is no output though.
I read other posts with people having the same exact unusual problem, I can only think to jtag and try remove nvram and try again in tftp
Try reversing the tx and rx. Tx on the router should go to rx on the adapter.
It won't hurt anything if tx and rx are connected backwards. _________________ I fix "shortcuts". If you don't have time to read thoroughly, I don't have time to re-type what you missed.
No DPN
This is a Parallel Flash
Partition information:
boot #00 00000000 -> 0003FFFF (262144)
trx #01 00040000 -> 0004001B (2
os #02 0004001C -> 007F7FFF (8093668)
nvram #03 007F8000 -> 007FFFFF (32768)
Partition information:
boot #00 00000000 -> 0003FFFF (262144)
trx #01 00040000 -> 007F7FFF (8093696)
nvram #02 007F8000 -> 007FFFFF (32768)
PCI bus 0 slot 1/0: _pci_map_mem: attempt to map 64-bit region tag =0x800 @ addr
=18010004
PCI bus 0 slot 1/0: _pci_map_mem: addr=0x18010004 pa=0x18010000 pci_mem_spac
e_pci_base=0x40000000 pci_mem_space=0x8000000
mcfg = 000810fe
ge0: BCM5750 Ethernet at 0x18010000
CPU type 0x2901A: 300MHz
Total memory: 32768 KBytes
Total memory used by CFE: 0x80300000 - 0x803A7AB0 (686768)
Initialized Data: 0x8033C900 - 0x8033FCB0 (13232)
BSS Area: 0x8033FCB0 - 0x80341AB0 (7680)
Local Heap: 0x80341AB0 - 0x803A5AB0 (409600)
Stack Area: 0x803A5AB0 - 0x803A7AB0 (8192)
Text (code) segment: 0x80300000 - 0x8033C900 (248064)
Boot area (physical): 0x003A8000 - 0x003E8000
Relocation Factor: I:00000000 - D:00000000
Boot version: v4.2
The boot is CFE
mac_init(): Find mac [00:1D:7E:F9:66:13] in location 0
Nothing...
eou_key_init(): Find key pair in location 4
The eou device id is same
The eou public key is same
The eou private key is same
CMD: [ifconfig eth0 -addr=192.168.1.1 -mask=255.255.255.0]
bcm5700: no firmware rendevous
eth0: Link speed: 1000BaseT FDX
Device eth0: hwaddr 00-1D-7E-F9-66-13, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Automatic startup canceled via Ctrl-C
CFE> nvram erase
CMD: [nvram erase]
*** command status = 0
CFE>
OK I tried and failed but I think my process is screwed up
when I set the static IP, and have the cat5 cable plugged into port 1 (not that it matters which port) I notice that my NIC shows no connection (is this normal, will it appear at the next command issued?)
I issued the command with tftp already started and clicked upgrade but if couldn't connect.
I tried to switch from dd-wrt to openwrt to play around with it. This is my spare router, but I would like to revive it. I want to get dd-wrt back on, but obviously must debrick it first.
I need to find the ifconfig commands I guess, cause it looks like switch is not initialized at all, I tried every port, no link light.
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Fri Apr 01, 2011 14:59 Post subject:
fggs wrote:
You could also try to configure your nic as 10/T half-duplex.. sometimes when it's configured as gigabit it isn't detected.
Bingo
@ xtacydima... You switch is initialized..
Boot version: v4.2
The boot is CFE
mac_init(): Find mac [00:1D:7E:F9:66:13] in location 0
Nothing...
eou_key_init(): Find key pair in location 4
The eou device id is same
The eou public key is same
The eou private key is same
CMD: [ifconfig eth0 -addr=192.168.1.1 -mask=255.255.255.0] <=======
bcm5700: no firmware rendevous
eth0: Link speed: 1000BaseT FDX <========
Device eth0: hwaddr 00-1D-7E-F9-66-13, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Automatic startup canceled via Ctrl-C
CFE> nvram erase
CMD: [nvram erase]
*** command status = 0
CFE> _________________ [Moderator Deleted]
