Debug console

9 posts / 0 new
Last post
hrlevy
hrlevy's picture
Debug console

Has anyone used the debug console on a WGR614 yet.

I have failed in all of my attemps to talk to it.

My hardware is the recomended rs232-3v3  usb adapter cable.

The cable works with othe test equipment.

Thanks

Howard R. Levy 

hrlevy
hrlevy's picture
I finally got access to the

I finally got access to the wgr614.

The doc is wrong speed must be set to 115kb not 38.4.

Now that I can talk to it, how do I get control of the wgr614 to try and reload the firmware???

looking at the output from the monitor it appear that there is no way to use it.

attach boot up  output  from wgr614::

///////////////

CFE for WGR614v8 version: 1.3                            
Build Date: Fri Apr 20 14:04:44 CST 2007                                       
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 4.138.1.0                                                              
Device eth0:  hwaddr 00-1E-2A-54-22-86, ipaddr 192.168.1.1, mask 255.255.255.0                                                                             
        gateway not set, nameserver not set                                          
Loading ............................                                  
CPU revision is: 00029029                        
Primary instruction cache 16kb, linesize 16 bytes (4 ways)                                                         
Primary data cache 16kb, linesize 16 bytes (2 ways)                                                  
Linux version 2.4.20 (dmy@fedora8.TTB) (gcc version 3.2.3 with Broadcom modifica                                                                               
tions) #197 Fri Feb 29 02:11:48 EST 2008                                       
Setting the PFC to its default value                                   
Determined physical RAM map:                           
 memory: 01000000 @ 00000000 (usable)                                    
On node 0 totalpages: 4096                         
zone(0): 4096 pages.                   
zone(1): 0 pages.                
zone(2): 0 pages.                
Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200                                                                     
CPU: BCM5354 rev 1 at 240 MHz                            
Calibrating delay loop... 237.56 BogoMIPS                                        
Memory: 14600k/16384k available (1233k kernel code, 1784k reserved, 100k data, 6                                                                               
8k init, 0k highmem)                   
Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)                                                            
Inode cache hash table entries: 1024 (order: 1, 8192 bytes)                                                          
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)                                                         
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)                                                           
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)                                                          
Checking for 'wait' instruction...  unava                                      
POSIX conformance testing by UNIFIX                                  
PCI: no core           
PCI: Fixing up bus 0                   
Linux NET4.0 for Linux 2.4                         
Based upon Swansea University Computer Society NET3.039                                                      
Initializing RT netlink socket                             
Starting kswapd              
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)                                                            
devfs: boot_options: 0x1                       
Squashfs 2.2-r2 (released 2005/09/08) (C) 2002-2005 Phillip Lougher                                                                  
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en                                                                               
abled    
ttyS00 at 0xb8000300 (irq = 3) is a 16550A                                         
ttyS01 at 0xb8000400 (irq = 0) is                                
PPP generic driver version 2.4.2                               
pflash: found no supported devices                                 
sflash: squashfs filesystem found at block 580                                             
Creating 8 MTD partitions on "sflash":                                     
0x00000000-0x00020000 : "boot"                             
0x00020000-0x003b0000 : "linux"                              
0x000912cc-0x003b0000 : "rootfs"                               
0x003b0000-0x003c0000 : "T_Meter1"                                 
0x003c0000-0x003d0000 : "T_Meter2"                                 
0x003d0000-0x003e0000 : "POT"                            
0x003e0000-0x003f0000 : "board_data"                                   
0x003f0000-0x00400000 : "nvram"                              
NET4: Linux TCP/IP 1.0 for NET4.0                                
IP Protocols: ICMP, UDP, TCP                           
IP: routing cache hash table of 512 b                                   
TCP: Hash tables configured (established 1024 bind 2048)                                                       
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.                                                  
NET4: Ethernet Bridge 008 for NET4.0                                   
802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>                                                            
All bugs added by David S. Miller <davem@redhat.com>                                                   
VFS: Mounted root (squashfs filesystem) readonly.                                                
Mounted devfs on /dev                    
Freeing unused kernel memory: 68k freed                                      
Algorithmics/MIPS FPU Emulator v1.5                                  
Reading board data...                    
WSC UUID: 0x6b4ff8cdd6688c1a39c35c8bb98ff6c6                                           
pa0maxpwr - 82             
pa0b0 - 0x164B             
pa0b1 - 0xFA6          
pa0b2 - 0xFE86             
opo - 8      
configure RF parameters OK                         
Using /lib/modules/2.4.20/kernel/drivers/net/et/et.o                                                   
insmod: bcm57xx.o: no module by that name found                                              
Using /lib/modules/2.4.20/kernel/drivers/net/wl/wl.o                                                   
Hit enter to continue...WARNING: console log level set to 1                                                          
*********************************************                                            
Wi-Fi Simple Config Application - Intel Corp.                                            
Version: Build 1.0.5, November 19 2006                                     
*********************************************                                            
Initializing stack...button monitor start...!                                            
 OK  
Now starting stack                 
get mac = 00 1E 2A 54 22 86                          
DEVICE PIN: 91050403                   
eth1: ignore i/f due to error(s)                               
Reading board data...                    
WSC UUID: 0x6b4ff8cdd6688c1a39c35c8bb98ff6c6                                           
Using /lib/modules/2.4.20/kernel/net/ipv4/acos_nat/acos_nat.o                                                            
insmod: unresolved symbol acosNat_IpFragInput                                            
insmod: unresolved symbol acosNat_IpFragOutput                                             
insmod: unresolved symbol acosNat_unregister_hook                                                
insmod: unresolved symbol acosNat_register_hook                                              
open failed:: No such file or directory                                      
dnsRedirectReply.c: Can't open device file: /dev/acos_nat_cli                                                            
info, udhcp server (v0.9.8) started                                  
error, unable to parse 'option wins '                                    
error, unable to parse 'option domain '                                      
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /d                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
Can't open device file: /dev/acos_nat_cli                                        
POT integrity check OK.                      
Can't open device file: /dev/aglog                                 
wl: Unsupported              
Start DHCP client daemon                       
info, udhcp client (v0.9.8) started                                  
Hit enter to continue...eth0: No such process                                            

DEVICE PIN:91050403
WSC: In unconfiged AP mode, wait for start command....
tlvPtrChar* : func CMasterControl_InitiateRegistration  line 656 allocating memo
ry 0x10003680 for 0x10003668
Waiting for Registrar to connect...

BusyBox v0.60.0 (2008.02.29-07:05+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.

# help

Built-in commands:
-------------------
        . : break cd continue eval exec exit export help login newgrp
        read readonly set shift times trap umask wait

#

////////////////////////////

Thank you

Howard R. Levy

hrlevy
hrlevy's picture
I finally get into the

I finally get into the console

what command should be used to reload the firmware from the debug console??

Nachi
Nachi's picture
tftpd.
Nachi
Nachi's picture
By the way I have noticed in

By the way I have noticed in your earlier email about this BPS 38.4 Kbps. Which doc are you using. The one that you should use is this one and it does have the correct baud rate. We would need to get the documentation corrected and we appreciate your effort on this a lot. I will respond to other threads separately.

Regards,

Nachi

Brandon C
Brandon C's picture
Nachi,

Nachi,

On one of my routers that won't boot I see an ifniite loop in the serial console. It just starts over and over again.

So I never get to the CFE prompt. Any ideas on this?

SouvikGhosh
SouvikGhosh's picture
It is evident from the dump

It is evident from the dump that every time your kernel is trying to boot. Actually you need to press ctrl+c while rebooting the router to get the CFE prompt. Please try that.. if you have already done so please make sure that your minicom is properly configured.

Brandon C
Brandon C's picture
SouvikGhosh said:

SouvikGhosh said:
It is evident from the dump that every time your kernel is trying to boot. Actually you need to press ctrl+c while rebooting the router to get the CFE prompt. Please try that.. if you have already done so please make sure that your minicom is properly configured.

Thanks for the tip. Got it now. Up and runnng.

Peter Redmer
Peter Redmer's picture
We've just published an

We've just published an article by BrandonC showing how to recover the WGR614L router using a serial console and cable. I thought this may be of interest to those participating in this thread!

You can find the article here:

Recover Your WGR614L Using A Serial Console & Windows