Help: ADSL2MUE Not booting anymore

All about firmwares for routers. Support for RouterTech firmwares is here too.
wisdom
Newbie
Newbie
Posts: 1
Joined: Thu Jan 11, 2007 10:30 pm

Help: ADSL2MUE Not booting anymore

Post by wisdom » Thu Jan 11, 2007 11:54 pm

I'm sorry.. I've been searching all around for an answer for my problem but no way to find what I hope to!

I have an ADSL2MUE from LinkSys and one day it stopped working.. when I power on, the red light is the only thing that I see. I built the RS232 adapter to connect my computer to the console of the router and what I see on the terminal is:

Code: Select all

Minimal POST completed...     Success.
Last reset cause: Hardware reset (Power-on reset)

PSPBoot1.2 rev: 1.2.0.4
(c) Copyright 2002-2004 Texas Instruments, Inc. All Rights Reserved.
That's all folks! No way to enter commands, no way to boot anything, no way to nowhere!

I dont' see the "Press ESC for monitor..." message or the "(psbl)" prompt.. no "Booting..." or "Launching kernel decompressor." message... nothing.

I guess that there's something wrong with one or both the images (kernel / firmware).. but I can only guess!

The only avaliable key is the reset button... but it looks like I get no effect...

Help me please... is there something hidden... a secret magic formula.. an easter-egg?!?! something!?! All the interfaces... lan, usb... are (obviously) down... Can I upload new image/images via serial-console? something else?! telepathy?!

TNX
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Post by thechief » Fri Jan 12, 2007 12:43 am

Corrupt flash? Corrupt bootloader? You might be able to use JTAG to restore the bootloader, and then erase the flash afterwards and start again. Search this forum for JTAG and you will find lots of information about how to build one.
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
^Albe^
Regular
Regular
Posts: 50
Joined: Sun Oct 29, 2006 2:17 pm

Post by ^Albe^ » Sat Jan 20, 2007 11:47 pm

can happen, i have flashed my adsl2mue with the wrong firmware: bricked and the ti utility cannot connect
i have already a jtag, but i cannot found any info about the jtag connector on the adsl2mue
any help is appreciated

i forgot: obv no chance at all to connect via ssh to the bootloader
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Post by thechief » Sun Jan 21, 2007 3:28 pm

Perhaps you may wish to post screenshots of your board, and then maybe someone can help you.
Edit: just flashing the wrong firmware should not normally require JTAG. You should try different versions of the pctool. In fact, you should not require the JTAG unless you have trashed the bootloader (i.e., mtd2).
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
^Albe^
Regular
Regular
Posts: 50
Joined: Sun Oct 29, 2006 2:17 pm

Post by ^Albe^ » Fri Jan 26, 2007 10:05 pm

thx thechief
the bootloader is gone, i (stupid...) downloaded (loooong time ago) the wrong image from yours site and flashed it...
i have found some info's about the connector at soon as possible i will try a reflash (and if works i can report it to u)
where can i found info about the jtag reflashing (or bootloader recover) ?
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Post by thechief » Fri Jan 26, 2007 11:00 pm

As I said, simply flashing the wrong firmware will not damage your bootloader. The only way you will damage your bootloader is if you do something to your mtd2 partition, That would almost always require a conscious effort to copy something there or repartition it, etc. If you have done either of those, then it would truly be gone. I don't know anything about JTAG, so I can't help you there. I believe that Biro has posted many instructions about JTAG on this forum. Do a forum search and you will find them.
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
mstombs
RouterTech Team
RouterTech Team
Posts: 3753
Joined: Wed Jan 10, 2007 11:54 pm

Post by mstombs » Fri Jan 26, 2007 11:28 pm

Google is your friend - the info is out there! I have seen it - but hasten to add - never tried. Here's some info I have gathered to help you search!

The JTAG connector needs to be soldered onto the board 12/14 way 0.1 pitch, seems the same as Linksys WRT54G with the extra pair as per standard. Then the 'hairydairymaid', for example, parallel port JTAG cable made up and used with the supplied software (info on openwrt wiki). Then a weird and wonderful command used of the style

% wrt54g -flash:custom /noreset /nobreak /nodma /fc:29 /window:0x90000000 /start:0x90000000 /length:0x10000

The guy who posted this said he was then able to telnet in and would report back later, but never did!

The flash arrangement does seem to agree with what my box reported

mtd0 0x900a0000,0x90400000
mtd1 0x90020000,0x900a0000
mtd2 0x90000000,0x90010000
mtd3 0x90010000,0x90020000

It seems you should make up a special 5V/3V serial console cable first and see what that says (I have a Nokia DKU-5 USB cable on order!), JTAG is really a last resort. The serial connector is already on the board supplied by Linksys. Are you sure you cannot get the PCTOOL to connect using a hub and the rest button on power up? As the bootloader is the lowest memory address you shouldnt be able to overwrite it. Trying to flash an image that is too big is more likely to corrupt the config area mtd3, for example?

I have saved my 64k mtd2 bootblock, but won't post these on public forum as it should contain the MAC address? I also have Linksys v 4.12 and 4.22 kernels and filesystems (which should go into mtd1 and mtd0), but still don't understand why the upgrade from 4.12 to 4.22 needed 2 web loads? Maybe I do V 4,22 has a new flash partition defined

mtd4 0x90020000,0x90400000

which extends across the other mtd1 and mtd0.

I don't have mtd3 as I assume this is the config area which will be defaulted on a reset???

One thing I am a bit confused about at present is that the ADSL2MUE uses a pspboot bootloader, but the first prompt and ftp utility seems to be ADAM2, so unless people have posted about patched/ different revision systems the ADAM2 hands over to pspboot and both are actually used?
Last edited by mstombs on Fri Jan 26, 2007 11:34 pm, edited 1 time in total.
User avatar
Neo
RouterTech Team
RouterTech Team
Posts: 3586
Joined: Thu Jan 26, 2006 1:09 pm
Contact:

Post by Neo » Fri Jan 26, 2007 11:33 pm

I would suggest reading posts by Biro etc on the RouterTech forum as these should be a little more specific ;)

E.g. viewtopic.php?p=14051&highlight=jtag#14051
RouterTech Team and Founding Member
Image
RouterTech Merchandise (UK)
No support via PM, please ask your questions on the forum!
mstombs
RouterTech Team
RouterTech Team
Posts: 3753
Joined: Wed Jan 10, 2007 11:54 pm

Post by mstombs » Sat Jan 27, 2007 12:03 am

On the ADSL2MUE the JTAG connector is labelled JP1 and looks to be in an easier location on the edge of the board to get at - you can see its the same one, and serial connection at the other end looks the same as your picture.

I like the design of the wiggler (buffered JTAG) cable in the link, but the other one seems to work with Linksys WRT54G's and really does look easy enough to make at home (or buy on ebay)!
User avatar
Shotokan101
RouterTech Team
RouterTech Team
Posts: 4779
Joined: Thu Jan 26, 2006 3:17 pm
Location: Glasgow, Scotland

Post by Shotokan101 » Sat Jan 27, 2007 12:04 am

mstombs wrote:On the ADSL2MUE the JTAG connector is labelled JP1 and looks to be in an easier location on the edge of the board to get at - you can see its the same one, and serial connection at the other end looks the same as your picture.

I like the design of the wiggler (buffered JTAG) cable in the link, but the other one seems to work with Linksys WRT54G's and really does look easy enough to make at home (or buy on ebay)!
....if you've found a source please post the link/details :wink:
Jim

.....I'm Sorry But I Can't Do That Dave.....
mstombs
RouterTech Team
RouterTech Team
Posts: 3753
Joined: Wed Jan 10, 2007 11:54 pm

Post by mstombs » Sat Jan 27, 2007 10:27 am

The Linksys WRT54G/GS/L can be debricked with the passive JTAG hardware and software described in here

http://downloads.openwrt.org/utils/Hair ... ty_v48.zip

Applicability to AR7 based boards described here

http://wiki.openwrt.org/AR7Port#head-68 ... 99c03e1f61

You can buy ready ('home?') made and tested copies of this cable from ebay, there's a couple of International sellers from Canada and USA advertising there now.

http://search.ebay.co.uk/search/search. ... g+%2B+jtag

An interesting looking serial console cable for a WRT54G is described here

http://www.martin.cc/OpenWrt/USB%20cons ... router.pdf
User avatar
Shotokan101
RouterTech Team
RouterTech Team
Posts: 4779
Joined: Thu Jan 26, 2006 3:17 pm
Location: Glasgow, Scotland

Post by Shotokan101 » Sat Jan 27, 2007 10:44 am

Thanks for the info.. mstombs :D
Jim

.....I'm Sorry But I Can't Do That Dave.....
^Albe^
Regular
Regular
Posts: 50
Joined: Sun Oct 29, 2006 2:17 pm

Post by ^Albe^ » Sun Jan 28, 2007 5:28 am

mstombs wrote: One thing I am a bit confused about at present is that the ADSL2MUE uses a pspboot bootloader, but the first prompt and ftp utility seems to be ADAM2, so unless people have posted about patched/ different revision systems the ADAM2 hands over to pspboot and both are actually used?
YES! the mistake begin from this..
the old reply to an ssh connection was

Code: Select all

220 ADAM2 FTP Server ready.
so i think is an adam2 bootloader

@mrchief:
you said "just flashing the wrong firmware should not normally require JTAG. You should try different versions of the pctool." , time ago, i have tryed one (only one, i dont' remember wich one) and a connection with ssh but i have not results at all
tomorrow i will try again with that utility (i'll search for some different version)
thx to all for the help
for sure i will report the results!
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Post by thechief » Sun Jan 28, 2007 3:13 pm

The greetings/prompts that you see when you login with ftp (or anything else) are not a reliable guide to what bootloader you have. Psp seems to be some sort of update to Adam2 anyway, and so, even with psp bootloaders, you might still see Adam2 greetings.
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
mstombs
RouterTech Team
RouterTech Team
Posts: 3753
Joined: Wed Jan 10, 2007 11:54 pm

Post by mstombs » Sun Jan 28, 2007 10:36 pm

I hooked up my very cheap "Nokia DKU-5 USB cable" a cheap chinese clone that only works with a very specific old Prolific driver in windows (but registers it as Nokia!). I tried forcing newer generics but no-go. There were only 4 wires in the cable, only 3 used/needed. NB Windows will not open the emulated com-port in HyperTerminal unless the serial cable is terminated.

Here is what this console reports when the ADSL2MUE boots successfully into RT2.1, Manually edited to remove duplicate line feedsdue to incorrect capture setup!

Code: Select all

Minimal POST completed...     Success.
Last reset cause: Hardware reset (Power-on reset)

PSPBoot1.2 rev: 1.2.0.4
(c) Copyright 2002-2004 Texas Instruments, Inc. All Rights Reserved.

Press ESC for monitor... 3321

(psbl) 

Booting...
Copyright (C) 2006 Merlion-ACORP Russia Software Company.
Launching kernel LZMA decompressor.
Kernel decompressor was successful ... launching kernel.

LINUX started...
Config serial console: ttyS0,38400
Auto Detection SANGAM chip
This SOC has MDIX cababilities on chip.
CPU revision is: 00018448
Primary instruction cache 16kb, linesize 16 bytes (4 ways)
Primary data cache 16kb, linesize 16 bytes (4 ways)
Number of TLB entries 16.
Linux version 2.4.17_mvl21-malta-mips_fp_le (root@localhost.localdomain) () #1 Sun Oct 29 18:07:31 GMT 2006
Determined physical RAM map:
 memory: 14000000 @ 00000000 (reserved)
 memory: 00020000 @ 14000000 (ROM data)
 memory: 00fe0000 @ 14020000 (usable)
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: 
calculating r4koff... 000b71b0(750000)
CPU frequency 150.00 MHz
Calibrating delay loop... 149.91 BogoMIPS
Freeing Adam2 reserved memory [0x14001000,0x0001f000]
Memory: 14320k/16384k available (1548k kernel code, 2064k reserved, 99k data, 60k init)
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...  unavailable.
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
TI Optimizations: Allocating TI-Cached Memory Pool.
Warning: Number of buffers is not configured.Setting default to 128
Using 128 Buffers for TI-Cached Memory Pool.
DEBUG: Using Hybrid Mode.
NSP Optimizations: Succesfully allocated TI-Cached Memory Pool.
Initializing RT netlink socket
Starting kswapd
Disabling the Out Of Memory Killer
devfs: v1.7 (20011216) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
Squashfs 2.2-r2+lzma (C) 2002-2005 Phillip Lougher, (C) 2005 McMCC
pty: 32 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with no serial options enabled
ttyS00 at 0xa8610e00 (irq = 15) is a 16550A
ttyS01 at 0xa8610f00 (irq = 16) is a 16550A
block: 64 slots per queue, batch=16
DEBUG: Initializing the voice port management module. 
DEBUG: Initialization of the voice port management module successful..
Using the MAC with internal PHY
Cpmac driver is allocating buffer memory at init time.
Cpmac driver Enable TX complete interrupt
Default Asymmetric MTU for eth0 1500
Default Asymmetric MTU for eth1 1500
Default Asymmetric MTU for eth2 1500
Default Asymmetric MTU for eth3 1500
PPP generic driver version 2.4.1
avalanche flash device: 0x400000 at 0x10000000.
 Amd/Fujitsu Extended Query Table v1.1 at 0x0040
number of CFI chips: 1
Looking for mtd device :mtd0:
Found a mtd0 image (0x97000), with size (0x369000).
Creating 1 MTD partitions on "Physically mapped flash:0":
0x00097000-0x00400000 : "mtd0"
mtd: partition "mtd0" doesn't start on an erase block boundary -- force read-only
Looking for mtd device :mtd1:
Found a mtd1 image (0x20090), with size (0x76f70).
Creating 1 MTD partitions on "Physically mapped flash:0":
0x00020090-0x00097000 : "mtd1"
mtd: partition "mtd1" doesn't start on an erase block boundary -- force read-only
Looking for mtd device :mtd2:
Found a mtd2 image (0x0), with size (0x10000).
Creating 1 MTD partitions on "Physically mapped flash:0":
0x00000000-0x00010000 : "mtd2"
Looking for mtd device :mtd3:
Found a mtd3 image (0x10000), with size (0x10000).
Creating 1 MTD partitions on "Physically mapped flash:0":
0x00010000-0x00020000 : "mtd3"
Looking for mtd device :mtd4:
Found a mtd4 image (0x20000), with size (0x3e0000).
Creating 1 MTD partitions on "Physically mapped flash:0":
0x00020000-0x00400000 : "mtd4"
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 1024)
Linux IP multicast router 0.06 plus PIM-SM
ip_conntrack version 2.1 (128 buckets, 1024 max) - 384 bytes per conntrack
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
ip_tables: (C) 2000-2002 Netfilter core team
ipt_account 0.1.6 : Piotr Gasid³o <quaker@barbara.eu.org>, http://www.barbara.eu.org/~quaker/ipt_account/
netfilter PSD loaded - (c) astaro AG
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Ethernet Bridge 008 for NET4.0
Initializing the WAN Bridge.
Please set the MAC Address for the WAN Bridge.
Set the Environment variable 'HWA_3'. 
MAC Address should be in the following format: xx:xx:xx:xx:xx:xx
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 60k freed

serial console detected.  Disabling virtual terminals.
console=/dev/tts/0

init started:  BusyBox v0.61.pre (2006.10.29-18:09+0000) multi-call binary
Starting pid 9, console /dev/tts/0: '/etc/init.d/rcS'
Algorithmics/MIPS FPU Emulator v1.5

 Reading Standard Configuration File /etc/led.conf

 Configured 15 states 
Using /lib/modules/2.4.17_mvl21-malta-mips_fp_le/kernel/drivers/net/avalanche_usb/avalanche_usb.o
USB: Entering USB_init_module.
USB Driver built for RNDIS-CDC protocols.
Error getting protocol configuration from bootloader environment.
Defaulting to "RNDIS-CDC" mode.
Start usb_clk_check
VID = 0x13b1
PID = 0xf
No Serial Number String present.
Manufacturer = Texas Instruments                      
Product description = Linksys RNDIS Network Adapter
USB: Entering USB_Init.
USB: Leaving USB_Init.
Default Asymmetric MTU for usb0 1500
USB: Leaving USB_init_module.
Using /lib/modules/2.4.17_mvl21-malta-mips_fp_le/kernel/drivers/atm/tiatm.o
registered device TI Avalanche SAR
Sangam detected
DSP binary filesize = 356930 bytes
tn7dsl_set_modulation : Setting mode to 0x1
Texas Instruments ATM driver: version:[6.00.01.00]
SIOCGIFFLAGS: No such device
SIOCGIFFLAGS: No such device
Sep  8 12:00:11 crond[61]: crond 2.3.2 dillon, started, log level 8
SIOCGIFFLAGS: No such device
PVC dB
vpi = -1 vci = -1 in_use = 0
vpi = -1 vci = -1 in_use = 0
vpi = -1 vci = -1 in_use = 0
vpi = -1 vci = -1 in_use = 0
vpi = -1 vci = -1 in_use = 0
vpi = -1 vci = -1 in_use = 0
vpi = -1 vci = -1 in_use = 0
vpi = -1 vci = -1 in_use = 0

Sep  8 12:00:12 cfgmgr(pppoa-108): Sep  8 12:00:12 | Valid Configuration Tree
Doing BRCTL ...
addbr br0 
Doing BRCTL ...
addbr br1 
Doing BRCTL ...
addbr br2 

Sep  8 12:00:12 cfgmgr(sntp): Sep  8 12:00:12 | NTP Polling Timer for DHCP Started succesfully.
Sep  8 12:00:12 cfgmgr(sar): Sep  8 12:00:12 | DSL Polling Timer Started succesfully.
Sep  8 12:00:12 cfgmgr(sar): Sep  8 12:00:12 | PSP Boot environment  Modem Modulation Change: 1
Sep  8 12:00:13 cfgmgr(fdb): Sep  8 12:00:13 | Firewall NAT service started

Default Asymmetric MTU for br0 1500
Default Asymmetric MTU for br1 1500
Sep  8 12:00:13 cfgmgr(lanbridge0): Sep  8 12:00:13 | Bridge Created: br0

Waiting for enter to start '/bin/sh' (pid 88, terminal /dev/tts/0)

Please press Enter to activate this console. Default Asymmetric MTU for br2 1500
device eth0 entered promiscuous mode
br0: port 1(eth0) entering learning state
device usb0 entered promiscuous mode
br0: port 1(eth0) entering forwarding state
br0: topology change detected, propagating
br0: port 2(usb0) entering learning state
br0: port 2(usb0) entering forwarding state
br0: topology change detected, propagating
And a poor photo of my hookup (No Ethernet/DSL) I'm sure I've seen better photos on the net. Image
The space to solder a JTAG header is the 14 solder filled holes next to the LEDs.

*UPDATED*

See the "How to make a Class II USB serial cable guide" on Neo's website under Guides

RT based intermediate link - kb.php?mode=article&k=38
Attachments
adsl2mueserial.JPG
(107.92 KiB) Downloaded 1407 times
Last edited by mstombs on Tue Oct 23, 2007 12:28 am, edited 3 times in total.
Post Reply