Does it count down 3...2...1..0 at this point?
Can you ping it?
Does the Webinterface work?

please provide some more detail

It counts 3,2,1,0. I press enter but it doesn't stop.. CTRL-C doesn't work too. No access to webinterface, no ping.

(Last edited by falso on 16 Sep 2009, 13:07)

Which terminal program are you using? Is it PuTTY?

If not, maybe try using PuTTY.. I am, and it sends the enter command just fine, otherwise, perhaps, like mine was, the USB cable you are using is just too slow...

I am using PuTTy! I try to press enter but nothing happens.  I bought the TTL-232R-3V3-AJ usb cable.

@ Falso

Hmm looks like the pinout of your cable is the problem as Nilfred suggested. Check the documentation of the cable you are using. The WRT side is () Vcc () RX () TX () GND the RX is connected to the wrong pin or not connected at all.

I double checked the wire connections. It's all ok. Now i am stuck.

if you got any screen outputs via rs232 rx is ok. check tx wire
you dont need vcc if power is plugged in, you just need rx, tx and gnd

try this, it worked for me with my TTL-232R-3V3

JP5
                              pin1
(gnd)   (tx)     (rx)   (vcc)
black yellow orange  red
TTL-232R-3V3

(Last edited by pregi on 16 Sep 2009, 22:21)

Options to consider:
- try a different PC, maybe the one you are using has a more "laggy" USB port
- try a serial to serial converting cable, others appear to have better results with that
- double check the TX pinout as others suggest

Then reverse Tx and Rx connection. I'm thinking about Tx echo is what you're hearing. Remember: "Tx wire side" goes to "Rx router side", "Tx router side" goes to "Rx wire side". That is the way it goes.
If no luck try pressing reset button instead of Enter, console will show some fork. Did we talk about Sercomm utility already?

(Last edited by Nilfred on 17 Sep 2009, 08:40)

Hello,

The pinout is ok, i verified that twice, in adition i bought another 3,5mm jack and the problem is still here, cant press enter or ctrl-c using putty or hyperterminal and so on, etc..
I've tried Sercomm utility but i cant get it to work. The router is in download mode but Nothing appears after i select my pc card.
Dont Know what to do more.
Thanks for the infos anyway.

3,5mm stereo audio jack with 5 pins?

Did you disable the flow control in putty ?

No, with 3 pins!

Yes, flow control is disabled!

Well, i've tried two cables (TTL-232R-3V3-AJ and rs232 direct serial cable) and i dont know what's happening with my uboot.
I simple can't press enter CTRL-C. Everything is connected very well, i've tried in two pc's without success..
Please help me.

No, no, no. Not a direct RS232 cable, is always a TTL 3.3v to ±12v RS232 circuit implied. Like old Nokia DKU-5 (clone) serial cable (not USB).

ok..
I dont know what to do more.. if someone wants to do a remote conection to my pc to see uboot logs and if i'm doing something wrong please tell me via PM.
Thanks in advance!

Hi,

I own a wrt350N v2.1 with firmware 2.0.17 bought in Luxembourg (Europe)

I've contacted Linksys (using web chat)in order to get a firmware update and they told me to use the one from version 2.0

from oOo.Manu.oOo to All Participants:
the annoying thing is that I have a hardware version 2.1
from Harsh (46139E) to All Participants:
The latest firmware is 2.00.19
from Harsh (46139E) to All Participants:
http://www.linksysbycisco.com/UK/en/support/WRT350N/download
from oOo.Manu.oOo to All Participants:
no, it's for version 2.0
from oOo.Manu.oOo to All Participants:
and I have a 2.1
from Harsh (46139E) to All Participants:
Version 2.0 and 2.1 is similar
from oOo.Manu.oOo to All Participants:
a specific local version
from Harsh (46139E) to All Participants:
The firmware are same for both
from oOo.Manu.oOo to All Participants:
so you mean I can flash it without being scared to brick it ?
from Harsh (46139E) to All Participants:
That's right

(Last edited by oOo.Manu.oOo on 21 Sep 2009, 22:09)

I also have a bricked WRT350N v.2.1 EU-model. My friend tried to flash it to DD-WRT and bricked it... doh!

I had exactly the same problem, using Vista/windows 7 - the problem disappeared when I used Windows XP. I use one of these adapters:
http://cgi.ebay.com/USB-To-TTL-Converte … 286.c0.m14

I am then able to connect usb-adapter (only Tx TX and 3.3v) to the serial header on the board (motherboard with the RJ45 ports on the right side, from left to right: pin1=3.3v, pin2=Tx, pin3=Tx, pin4= not connected), then start Putty.exe to listen on the com-port, then plug in the power supply, then I am able to use the Enter-key to halt the boot-process.

However, once the I let the boot process continue, I get this, which results in a Kernel Panic.

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
_   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/    |____/ \___/ \___/ \__|  ** LOADER **
** MARVELL BOARD: RD-88F5181L-VOIP-GE LE

U-Boot 1.1.1 (Dec 12 2006 - 16:12:22) Marvell version: 1.7.3

DRAM CS[0] base 0x00000000   size  32MB
DRAM Total size  32MB
Flash: mvFlashInit base 0xff800000 devW 1 busW 1
Flash: flashStructGet manu 0xec id 0xe0
Flash: flashStructGet flash is supported.
FLASH: initFlashSecs TOP Sector Type
Flash: flashSecsInit main sector loop 0 - 127
[8192kB@ff800000] Flash:  8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment

Soc: MV88F5181 Rev 9
CPU: ARM926 (Rev 0) running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz

USB 0: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   mvEgigaLoad: egiga0 load ok
egiga0 [PRIME]

***************DRIVER INFO*****************

DRIVER BUILD DATA: Jan  9 2007 at 18:25:44
DRIVER VERSION 1.06

*******************************************
dbSign is:65:52:63:4f:6d:4d
mac address in flash is:00:1d:7e:ad:c4:ca
have eRcOmM
Hit ENTER to stop autoboot:  0
copy kernel from 0xff800000 to 0x400000 with size 0x200000
## Booting image at 00400000 ...
   Image Name:   Linux-2.6.30.5
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    900180 Bytes = 879.1 kB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.30.5 (openwrt@debian5) (gcc version 4.1.2) #1 Tue Aug 25 20:43:08 CEST 2009
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Linksys WRT350N v2
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
Kernel command line: root=/dev/mtdblock1 rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
NR_IRQS:64
PID hash table entries: 128 (order: 7, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 30036KB available (2156K code, 157K data, 100K init, 0K highmem)
Calibrating delay loop... 332.59 BogoMIPS (lpj=1662976)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 1008 bytes
NET: Registered protocol family 16
Orion ID: MV88F5181L-Rev-A1. TCLK=166666667.
Applying Orion-1/Orion-NAS PCIe config read transaction workaround
PCI: bus0: Fast back to back transfers disabled
pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot
pci 0000:01:00.0: PME# disabled
PCI: bus1: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
msgmni has been set to 58
alg: No test for lzma (lzma-generic)
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:00:00:00:51:81
physmap platform flash device: 00800000 at f4000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition information
Creating 7 MTD partitions on "physmap-flash.0":
0x000000000000-0x000000100000 : "kernel"
0x000000100000-0x000000750000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=240000, len=510000
0x000000240000-0x000000750000 : "rootfs_data"
0x000000760000-0x0000007a0000 : "lang"
0x0000007a0000-0x0000007c0000 : "nvram"
0x0000007c0000-0x000000800000 : "u-boot"
0x000000750000-0x000000760000 : "eRcOmM_do_not_touch"
0x000000000000-0x000000760000 : "image"
i2c /dev entries driver
TCP westwood registered
NET: Registered protocol family 17
Distributed Switch Architecture driver version 0.1
eth0[0]: detected a Marvell 88E6131 switch
dsa slave smi: probed
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
SQUASHFS error: squashfs_read_data failed to read block 0x135b5e
SQUASHFS error: Unable to read metadata cache entry [135b5e]
SQUASHFS error: Unable to read inode 0x7c51cae
------------[ cut here ]------------
WARNING: at fs/inode.c:674 0xc00939a0()
Modules linked in:
Backtrace:
Function entered at [<c0025310>] from [<c0025770>]
r6:c00939a0 r5:c020da58 r4:000002a2
Function entered at [<c0025758>] from [<c0030a74>]
Function entered at [<c0030a24>] from [<c0030aa4>]
r7:c180ce48 r6:c1d6b800 r5:c1df15a0 r4:c180ce48
Function entered at [<c0030a8c>] from [<c00939a0>]
Function entered at [<c0093958>] from [<c0095adc>]
r4:c180ce48
Function entered at [<c0095abc>] from [<c00cabcc>]
r4:c1d9aec0
Function entered at [<c00ca87c>] from [<c0084bb8>]
r9:00000000 r8:00008000 r7:00000003 r6:c1d6b800 r5:c1d6b800
r4:c1802bbc
Function entered at [<c0084a90>] from [<c00ca774>]
Function entered at [<c00ca754>] from [<c0084588>]
r4:c1c0a320
Function entered at [<c0084530>] from [<c0084638>]
r8:c1d9b000 r7:c0245df4 r6:00000000 r5:c1c6b000 r4:00008000
Function entered at [<c00845f8>] from [<c00984f8>]
r8:00000000 r7:c1d9b000 r6:c1c6b000 r5:00008000 r4:00000000
Function entered at [<c0098384>] from [<c0098ae4>]
Function entered at [<c0098a58>] from [<c0008cbc>]
r7:00008000 r6:c1ce0000 r5:c001f884 r4:c1ce0000
Function entered at [<c0008c18>] from [<c0008f34>]
Function entered at [<c0008ed8>] from [<c0009088>]
r5:c001f83c r4:c02551a8
Function entered at [<c0008f44>] from [<c00087d0>]
r5:c001de38 r4:c0255198
Function entered at [<c0008714>] from [<c00339a0>]
r6:00000000 r5:00000000 r4:00000000
---[ end trace 73aec54a305472db ]---
VFS: Cannot open root device "mtdblock1" or unknown-block(31,1)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0 driver: physmap-flash
1f01            6464 mtdblock1 driver: physmap-flash
1f02            5184 mtdblock2 driver: physmap-flash
1f03             256 mtdblock3 driver: physmap-flash
1f04             128 mtdblock4 driver: physmap-flash
1f05             256 mtdblock5 driver: physmap-flash
1f06              64 mtdblock6 driver: physmap-flash
1f07            7552 mtdblock7 driver: physmap-flash
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,1)

**********************************************************************end of log.

I have tried the TFTP-method, but without any luck.

Once I power on holding the reset-button, and let go, the LED flashes continually orange/green, but no replies to ping.

How do I get on from here, please advice.

is it possible to use the built in tools in the U-boot-system?

Once I halt the autoboot-process, and type help, these commands appear:

********************************************************************* begin

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
_   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/    |____/ \___/ \___/ \__|  ** LOADER **
** MARVELL BOARD: RD-88F5181L-VOIP-GE LE

U-Boot 1.1.1 (Dec 12 2006 - 16:12:22) Marvell version: 1.7.3

DRAM CS[0] base 0x00000000   size  32MB
DRAM Total size  32MB
Flash: mvFlashInit base 0xff800000 devW 1 busW 1
Flash: flashStructGet manu 0xec id 0xe0
Flash: flashStructGet flash is supported.
FLASH: initFlashSecs TOP Sector Type
Flash: flashSecsInit main sector loop 0 - 127
[8192kB@ff800000] Flash:  8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment

Soc: MV88F5181 Rev 9
CPU: ARM926 (Rev 0) running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz

USB 0: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   mvEgigaLoad: egiga0 load ok
egiga0 [PRIME]

***************DRIVER INFO*****************

DRIVER BUILD DATA: Jan  9 2007 at 18:25:44
DRIVER VERSION 1.06

*******************************************
dbSign is:65:52:63:4f:6d:4d
mac address in flash is:00:1d:7e:ad:c4:ca
have eRcOmM
Hit ENTER to stop autoboot:  0
Marvell>> help
?       - alias for 'help'
base    - print or set address offset
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootext2    dev:boot_part1,boot_part2 addr boot_image linux_dev_name
bootm   - boot application image from memory
bootp   - boot image via network using BootP/TFTP protocol
bubt    - Burn an image on the Boot Flash.
cmp     - memory compare
cp      - memory copy
cpumap - Display CPU memory mapping settings.
crc32   - checksum calculation
diskboot- boot from IDE device
echo    - echo args to console
erase   - erase FLASH memory
ext2load- load binary file from a Ext2 filesystem
ext2ls- list files in a directory (default /)
flinfo  - print FLASH memory information
go      - start application at address 'addr'
help    - print online help
ide     - IDE sub-system
loop    - infinite loop on address range
md      - memory display
mm      - memory modify (auto-incrementing)
mtest   - simple RAM test
mw      - memory write (fill)
nm      - memory modify (constant address)
pci     - list and access PCI Configuraton Space
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
reset   - Perform RESET of the CPU
saveenv - save environment variables to persistent storage
scload  - Sercomm load binary file from flash image
setenv  - set environment variables
tftpboot- boot image via network using TFTP protocol
version - print monitor version
Marvell>>

***************************************'end

I have tried the TFTP-method, but without any luck.

Once I power on holding the reset-button, and let go, the LED flashes continually orange/green, but no replies to ping. Putty displays this:

*************************************** begin

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
_   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/    |____/ \___/ \___/ \__|  ** LOADER **
** MARVELL BOARD: RD-88F5181L-VOIP-GE LE

U-Boot 1.1.1 (Dec 12 2006 - 16:12:22) Marvell version: 1.7.3

DRAM CS[0] base 0x00000000   size  32MB
DRAM Total size  32MB
Flash: mvFlashInit base 0xff800000 devW 1 busW 1
Flash: flashStructGet manu 0xec id 0xe0
Flash: flashStructGet flash is supported.
FLASH: initFlashSecs TOP Sector Type
Flash: flashSecsInit main sector loop 0 - 127
[8192kB@ff800000] Flash:  8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment

Soc: MV88F5181 Rev 9
CPU: ARM926 (Rev 0) running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz

USB 0: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   mvEgigaLoad: egiga0 load ok
egiga0 [PRIME]

***************DRIVER INFO*****************

DRIVER BUILD DATA: Jan  9 2007 at 18:25:44
DRIVER VERSION 1.06

*******************************************
dbSign is:65:52:63:4f:6d:4d
mac address in flash is:00:1d:7e:ad:c4:ca
have eRcOmM
if release button,enter download
mvEgigaLoad: egiga0 load ok
egiga0 [PRIME]

mvEgigaInit: egiga0 init - mvBoardPhyAddrGet()=0x0 , priv->port =0x0
ring full
mvEgigaInit: egiga0 complete ok
In download function
mac address:00:1d:7e:ad:c4:ca
Pin:36.39.33.30.38.34.32.30

**********************************************************end

Any ideas?

Dude, you have a lot of reading to do, begin at the start and work your way through paying particular attention to https://forum.openwrt.org/viewtopic.php … 744#p89744 <-- this post by maddes.b

I had a hell of a time understanding the idea of offsets (the hexadecimal addition is actually pretty easy if you use the 'padded' files created by maddes.b), but I think the post is ONLY logical if you follow the WHOLE train of though.. if you're thinking of posting here, asking for a quick fix, no.. sorry, doesn't exist.. but there is working router to be had if you're patient enough to read through the forum thread and apply some logic.

DD-WRT?
Do they support the V2 modell by now?

The deepest issue with the kernel is, that the mtd-tables (kernel) are often too tiny.
Therefore You run into these kernel panics.

So please be very careful compiling the kernel by your own. (or grap it elsewhere beside maddes place)
Although it is a little bit forgotten, I extended the wrt350n-webbuilder with some size-tests,
which helped me to look at the file-sizes.

So please check the mtd-partition sizes first, compile, check kernel and rootfs-sizes, build
and ..... happy flashing.

Your issue seems to be rather easy.
Stop at uBoot.

set the serverip
start a tftp-server on your desktop
tftboot

unprotect and copy to the right flash-memory
reboot

References
https://forum.openwrt.org/viewtopic.php … 417#p91417
https://forum.openwrt.org/viewtopic.php … 808#p88808

in this download mode, you can flash an image. I followed suggestions from Maddes.B and others, see here.

If he/you had checked the hardware list of DD-Wrt and its forums, you would know that DD-WRT does not support v2.x versions of WRT350N. (Sebastian stopped to add support for it around June 2008, do not know if he will pick it up again as the kernel and drivers became more stable).
All possible solutions to your problem have been posted to your question. The one from drizzt81 via download mode should be your escape route. Good luck.

(Last edited by maddes.b on 22 Sep 2009, 22:10)

Bricked WRT350n V2.x Recovery HOWTo

DO YOU THINK YOU HAVE BRICKED YOUR LINKSYS WRT350n v2.x ROUTER??

OK! Well I think I have some good news!

I've seemingly found a very very simple way to recover one's router to the original firmware (and perhaps later, even OpenWRT) without needing to open the case at all and without needing to use a serial interface! It's all done via a very simple point and click graphical program and a simple sequence with the reset button..

The inspiration came from a post by drizzt81 explaining how his router had entered into what is described as 'download mode'. However users who have seemingly 'bricked' their routers and do not have a serial connection would have no way of knowing if their router is in 'download mode' or not.

The solution was explained in a step by step guide by drizzt81 who used information gathered from previous posts from people who I would LIKE to credit as sources, but I do not have their posts handy at this point, I mean no disrespect to the hard working folk who have given their time and knowledge in this forum. The process is VERY VERY SIMPLE and requires no special hardware and in fact doesn't require any advanced computer knowledge either! A total beginner can expect to successfully recover their router using this method.

Step 1:

Software requirements

Required Knowledge:

* Usage of a .ZIP utility to extract some of the installation files.
* Basic software installation knowledge.

Download a .zip file containing the 'Upgrade Utility' program from this link and extract the file Upgrade_207_XP.exe then run that file to install the 'Upgrade Utility' application. (Scanning for nasty stuff 1st is recommended, just in case as this is not hosted in Linksys's website..) Please note that if you are using Windows Vista, you must select to run the application with 'Windows XP, Service pack 2 Compatibility Mode' enabled.

Download the full-image.bin file(provided by relghuar) and put it somewhere you can remember, (Desktop maybe?). (Thanks to relghuar for extracting and hosting this file, please let me know if you object to me direct linking to it.) The original post for the process by which relghuar extracted the image and file location can be found here (WARNING: DEADLY BORING TECHY STUFF!)

Step 2:

Cabling

Required Knowledge:

* Be able to locate the LAN ports on your router and be able to tell them apart from the WAN port. (LAN ports are (damn it, I am color blind! is it.. yellow? edit(maddes.b informs me that the ports are in fact orange, DOH!)) anyway, the WAN port is definitely blue.. Reasonably speaking here, if you managed to have the technical savvy to brick your router by installing OpenWRT, I think it's reasonable to assume you can tell the difference between a LAN and WAN port..

Directly connect your computer to one of the LAN ports on your router, I chose port 1, but I assume any LAN port will work. (I am also assuming that the WAN port won't work, but this is untested.. If you have some free time to just waste for stupidity's sake, perhaps you can test the theory and let me know.. I personally couldn't be bothered, just plug into LAN port 1 for pity's sake!!)

Step 3:

Entering 'Download mode' (This information was originally found at the NSLU2 Linux users group and through experimentation, adapted to work for the WRT350n V2.x)

Required knowledge:

*Be able to locate the 'reset' button. It is beside the power jack on the back of the router, beside LAN port 4. You will need a paperclip, or as I used, a thin screw driver.

Disconnect the power from the router, or as I did, turn off the powerboard's power. The reason I did this is because I have fat fingers and inserting the power cable whilst holding in the reset button proved difficult. (MAKE SURE THE POWER BOARD IS NOT THE ONE YOUR COMPUTER IS CONNECTED TO!!) *blush* Enough said on that matter... ehhem..

Method - with the power to the router OFF, hold in the reset button. Turn on/plug in the power and as soon as the LAN light comes up (1 - 2 secs) release the reset button. It's a pretty quick thing... If you have done it successfully, the power light on your router should be flashing between red... err.. ora.. umm yellow? (damn it I knew it was a bad idea for ME to write a HowTo..) Anyway! It'll be flashing!! If not, turn off/unplug the router's power and try again..

Once you are in download mode, you can move to Step 4.

Step 4:

Using the 'Upgrade Utility' software

Required knowledge:

*Location of the 'full-image.bin' file we downloaded earlier, I suggested locating it on your desktop, unless you decided to put it elsewhere..

Open the 'Upgrade Utility' application.

Once inside the utility, click the 'Browse Targets' button. Shortly, a dialogue box showing the MAC address (a long and confusing looking number) will be listed in the 'Devices List'.

Click the 'Files' button and browse to the 'full-image.bin' file. Once you select 'OK' you should get a 'BIN file Information' box, which will allow you to select 'OK' at the bottom.

Once you click 'OK', you will be returned to the 'Devices List' dialogue. Here you should click 'Upgrade'. You will get an information dialogue box that informs you that the version is older than the one currently installed in the router. Dismiss it, the dialogue is in fact correct, the 'full-image.bin' file was created a long time ago and is extracted from a router which was running version .17 (the current version is .19) No big deal. If you want version .19, download it from the Linksys website after you recover your router.

The next process is time consuming. IT IS ALSO FATAL TO THE ROUTER IF INTERRUPTED. In the spirit of Zen, I suggest removing yourself from the room while the router does it's thing. 'The watched pot, never boils'.

Step 5:

Power cycle the router and you should have a working router again, using Linksys firmware. If you want to try OpenWRT again, you can use the 'Webupgrade' package.

Voila!

DBM

P.S. Here is a quote of the posting I referenced from drizzt81. Many thanks to you!! Please let me know your sources, so that I may reference them also!

(Last edited by DaBigMac on 25 Sep 2009, 12:48)

hi!
I'm new here, so please don't flame me if what I'm asking is bullshit^^.

Is there any chance that the DIR-615 A1 will be supported? If I saw it correctly it should have the same type of cpu too, with the same amount of ram/flash.
(edit: grammar)

(Last edited by rviktor on 25 Sep 2009, 18:30)