I'm planning on purchasing the Linksys WRT54GR-EU wireless router with rangebooster.
It's info can be found here: http://www.linksys.com/servlet/Satellit … 9441396B24

Now my question is: Does OpenWRT support this router ?
I've looked at the 'Supported Devices Page' but there isn't any info available for this device.

Some help here ?
Thnx

I have one of these with OpenWrt on it and I am using it "as we speak".
There are no pre-compiled packages for it on openwrt I downloaded the source tree and compiled it to get my version. You need the RDC31XX set in the configuration menu.

If you go to x-wrt.org they have pre-compiled snapshots for this port but I have not tried them they are compiled daily I believe so they will probably work.

Best

Colin

The x-wrt.org Kamikaze (rdc) snapshot boots properly on my WRT54GR.

A couple of questions for you guys, I'm new to the OpenWRT stuff

How do you get he snapshot images onto the linksys - the firmware upgrade want's a .bin whereas the snapshot files are all .img

What is the Redboot IP address - reading the redboot sopurce from the Linksys FTP site suggests that it should be 192.168.1.1 but that doesn't seem to work for me (nor does 192.168.0.1)

could you tell me please how did you flashed the router? all i find are .imgs and via the upgrade window i can only submit .bin

im a bit lost, do i have to use flashcp for this?

thanks you in advance for some clear guidelines.

/a

Hi

I was able to flash my WRT54GR today by
1) checking out with subversion (on ubuntu hardy)

2) building as per the README except that I also
needed to install autoconf (to build) and tftp (to install)
and make my terminal taller (terminal must be 80x19+).
Per forum messages, I configured for Airlink 101 AR525W
(they are said to be hardware-identical).  The only non-default
choice I made was to omit pppoe

I installed according to these directions...

http://wiki.openwrt.org/OpenWrtDocs/Installing/TFTP

It worked after a few trial-and-error sequences like so:

  cable plugged directly from laptop into port 1 in the yellow "ethernet" block (not the blue "internet" port)

  held recessed button for five seconds, and pressed enter on:

  # flash.sh openwrt-rdc-jffs2-64k-ar525w.img linksys

The instructions say...

tftp> Please wait until power led stops flashing. Do not poweroff! Then you can login via telnet 192.168.1.1.

For me, the power light never blinked, but it did eventually reboot (power light off, then back on, and solid light comes on for ethernet 1)

At first telnet didn't work, web didn't work, but then telnet did, on second try!  I logged in, and, per instructions, set a password, which then disabled telnet and I was able to log in again with ssh root@192.168.1.1

Haven't tried X-WRT yet, etc., or configured anything, but it does see wlan0 and three ethernet devices (why not five?), and I thought I'd get my notes up here while it was still fresh in the mind.

Nil0

This model is software-identical to the AirLink101 AR525W. You can find images that may be expected to work out-of-the-box at:
http://downloads.openwrt.org/snapshots/rdc/

Hi, novice here...

Where do I find flash.sh, is it possible to acheive the upload from Windows XP? Does anyone have a .bin file that can be loaded using the Linksys interface. Thanks for reading.

John

I don't know what the web interface requires on the WRT54GR, but if anyone else does, it should be trivial to make the buildroot autogenerate it.

Also, somebody in #openwrt ("lopz") reported having flashed his WRT54GR over TFTP with the openwrt-rdc-squashfs-ar525w.img file, and had many problems due to the way the previous (original) firmware was laid out. The fix/workaround was to flash openwrt-rdc-jffs2-64k-ar525w.img instead, and then reflash again with openwrt-rdc-squashfs-ar525w.img, after which it worked correctly.

Hello again,

I managed to load http://downloads.openwrt.org/snapshots/rdc/ using Windows FTP and things appeared to work. But then I broke it - trying various settings around bridging the WAN connection. Now I can't log into the the unit. It boots fine but doesn't allow connection on 192.168.1.1. The reset button appears to be ignored wih OpenWRT loaded. When trying to re flash the unit the behaviour is odd:
1) Doesn't respond to ping 192.168.1.1 UNLESS a DHCP server is present.
2) When DHCP is present the base MAC and the base MAC+1 request and are serviced.
3) Ping on 192.168.1.1 responds during the boot phase but TFTP is unable to load the unit - using windows as I did originally - also tried 2 other TFTP packages but no joy re flashing.
4) The WLAN appears to be offering an Ad-Hoc connection but no action.

The unit is running in its own little world but not responding to the outside world. I did configure the DMZ light to flash the heartbeat which is does normally once booted.

Does anyone know if there is a special sequence to 'factory default' the unit ?
Any other tricks to get TFTP to load my unit?

Thanks, John.

That is very strange indeed, but if you flashed a squashfs image directly over the Linksys firmware without first flashing a jffs2 image, I'm not really surprised. Now, the best course of action would be to get a log of what's happening from the serial console.

Hi, thanks for the reply. I loaded the  openwrt-rdc-jffs2-64k-ar525w.img file and it was working fine.
Can you point be at a wiki for the log file ?

John.

I don't think I understand your question; if you're asking where to paste the log you get from the serial console, you can do so right here.

Hi,

Do I need to connect to a JTAG connector to get the serial log? Can you point be to a wiki that describes how to get the log information.

John.

No, JTAG is a separate connection (usually 6 pins in a single row on RDC devices). The serial connector would be the other one:
http://wiki.openwrt.org/OpenWrtDocs/Cus … al_Console
You will need something that uses 3.3V serial communications. (If your computer has a serial port, its specs are ±25V, not 3.3V.)

Thanks for your help, I'll take a look tomorrow.

Hi, I've still not managed to open up the case to find my serial connection. However I have noted that the external DHCP isn't required. Just connecting the WAN port to a LAN port is enough to start the ping response on 192.168.1.1 during boot. Still no joy with reflashing.

:-(

Hi,

here is my serial output - thanks for your patience. Can you see what is amiss?

John.

ð+Ethernet eth0: MAC address 00:00:01:02:03:04
IP: 192.168.1.1/255.255.255.0, Gateway: 192.168.1.254
Default server: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version v2_0 - built 18:31:11, Aug  4 2005

Platform: PC (I386)
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x000f0000, 0x00072ed0-0x000a0000 available
ver 00:0003  05-24-05

<press Ctrl+C to enter prompt mode>

# Activate RDC-Keilven's RS232 Patch V2
RedBoot>
# Kernel size = 758676 bytes
# FW size = 786432 bytes

# fwcheck: base = 0x00400000, size = 0x00000400
# Firmware Checksum O.K
# Kernel copying......BEGIN
# Kernel copying......FINISH

mem_size: 1000000
Uncompressing Linux
Done, booting
Linux version 2.6.24.7 (andy@devsandbox.padded-cell.net) (gcc version 4.1.2) #2
Wed Oct 15 19:12:19 PDT 2008
BIOS-provided physical RAM map:
BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
BIOS-e801: 0000000000100000 - 0000000001000000 (usable)
16MB LOWMEM available.
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->     4096
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->     4096
DMI not present or invalid.
Allocating PCI resources starting at 10000000 (gap: 01000000:ff000000)
Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 4064
Kernel command line: console=ttyS0,38400 root=/dev/mtdblock1 noinitrd init=/etc/
preinit
Initializing CPU#0
PID hash table entries: 64 (order: 6, 256 bytes)
console [ttyS0] enabled
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 13948k/16384k available (1272k kernel code, 2048k reserved, 340k data, 1
32k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xffffa000 - 0xfffff000   (  20 kB)
    vmalloc : 0xc1800000 - 0xffff8000   ( 999 MB)
    lowmem  : 0xc0000000 - 0xc1000000   (  16 MB)
      .init : 0xc0296000 - 0xc02b7000   ( 132 kB)
      .data : 0xc023e39d - 0xc029349c   ( 340 kB)
      .text : 0xc0100000 - 0xc023e39d   (1272 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512
Compat vDSO mapped to ffffe000.
CPU: 486
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 0k freed
net_namespace: 64 bytes
NET: Registered protocol family 16
PCI: Using configuration type 1
Setting up standard PCI resources
PCI: Probing PCI hardware
Time: pit clocksource has been installed.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
rdc321x: init success
Total HugeTLB memory allocated, 0
squashfs: version 3.0 (2006/03/15) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler cfq registered (default)
Non-volatile memory driver v1.2
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
flash device: 400000 at ffc00000
RDC3210 Flash: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
RDC3210 Flash: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Creating 4 MTD partitions on "RDC3210 Flash":
0x00000000-0x003d0000 : "linux"
0x000c0000-0x003d0000 : "romfs"
0x003d0000-0x003e0000 : "nvram"
0x003e0000-0x00400000 : "bootldr"
Registered led device: rdc321x:dmz
nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
TCP vegas registered
NET: Registered protocol family 1
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
Using IPI Shortcut mode
VFS: Mounted root (jffs2 filesystem).
Freeing unused kernel memory: 132k freed
Please be patient, while OpenWrt loads ...
- preinit -
Press CTRL-C for failsafe
- init -

Please press Enter to activate this console. PPP generic driver version 2.4.2
ip_tables: (C) 2000-2006 Netfilter Core Team
<6>r6040: RDC R6040 NAPI net driver,version 0.19 (16Jun2008)

r6040: debug 0
<6>r6040: RDC R6040 NAPI net driver,version 0.19 (16Jun2008)

r6040: debug 0
br-wan: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
device eth0 entered promiscuous mode
br-wan: port 1(eth0) entering learning state
br-wan: topology change detected, propagating
br-wan: port 1(eth0) entering forwarding state
br-lan: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
device eth1 entered promiscuous mode
br-lan: port 1(eth1) entering learning state
br-lan: topology change detected, propagating
br-lan: port 1(eth1) entering forwarding state
Link Change x9022
device wlan0 entered promiscuous mode
Link Change x9022

-----------------------
I have used redboot to reload the original firmware and the unit is working again.

John.

(Last edited by rascalator on 7 Nov 2008, 20:42)

after upgrade my wrt54gr router is dead. could you please tell the serial and jtag pinout for this router. i want to check whats going on console.

Thanx

Please see reply earlier in the thread...

No, JTAG is a separate connection (usually 6 pins in a single row on RDC devices). The serial connector would be the other one:
http://wiki.openwrt.org/OpenWrtDocs/Cus … al_Console
You will need something that uses 3.3V serial communications. (If your computer has a serial port, its specs are ±25V, not 3.3V.)

(Last edited by rascalator on 20 Nov 2008, 22:40)

hi,

i have homemade R232 to TTL converter but dont know the TX,RX,GND pins on the WRT54GR Board. there are 9 pins on the Board. could you tell me which pin on the board should be connected to which pin on the computer Serial Cable.

rxd - o    o -
      - o    o -
      - o    o -
txd - o     o - gnd
      - o

Hope this helps.

http://wiki.openwrt.org/OpenWrtDocs/Har … 101/AR525W

This model has an unpopulated 9-pin header that exposes a 3.3V serial port.

Board view, component side:

John.

(Last edited by rascalator on 24 Nov 2008, 17:13)

thank you very much. i will try today let you know the results

i have tried but it does not seems to be working. nothing on console.

Here is serial port: