Same here. The router didn't seem to reboot after tftp. Had waited 25 mins and the status LED just stayed flashing. If I do the power cycle it will return to original fw. BTW I use FR-54RTR.
rajing wrote:
Stains, did you have to replace the redboot as is needed for the DIR-300 a1? I'm following your steps with the ones for a dir-600 a1 but can't seem to do either. Flashing the firmware via tftp ends up in a non-responsive router until reboot. Trying it the tftp server way, like the dir-300 a1, doesn't do anything - i'm unable to ping the route via the WAN port on 192.168.20.80. Any insight?
Posted: Sun Feb 14, 2010 4:15 Post subject: router switch to 192.168.0.2 after tftp completed
Interestingly, right after all the TFTP packets, router sent a IGMP message (originated from 192.168.0.2 but same MAC). Then it started accepting requests on 192.168.0.2 and everything works the same (still old frys web interface). Once router reset it fell back to 192.168.0.1.
chirho wrote:
Same here. The router didn't seem to reboot after tftp. Had waited 25 mins and the status LED just stayed flashing. If I do the power cycle it will return to original fw. BTW I use FR-54RTR.
rajing wrote:
Stains, did you have to replace the redboot as is needed for the DIR-300 a1? I'm following your steps with the ones for a dir-600 a1 but can't seem to do either. Flashing the firmware via tftp ends up in a non-responsive router until reboot. Trying it the tftp server way, like the dir-300 a1, doesn't do anything - i'm unable to ping the route via the WAN port on 192.168.20.80. Any insight?
Okay, so I made some progress....some bad, but mostly good. If you hold the reset button down for 30 seconds (probably only need to do it for 10) while plugging in the power, you get into this weird boot state. While in this state point a web browser to 192.168.0.1 and you will see a "D-LINK Firmware Upgrade System" page. You have to use Internet Explorer or the upgrade doesn't take. YMMV, but Chrome does not work. STOP HERE!
Neither of the images in the trunk seem to work. If you flash them your router turns into a semi-brick. Turning on the router results in a non-functional state. This is what happened to me. My guess is that there is something wrong with the image. The good thing is holding down the reset button while plugging the power still takes you back to the bootloader state. Since Fry's firmware doesn't seem to be available yet, and I really had nothing to lose, I downloaded the DIR-600 firmware from the US website and tried to flash that, which worked. Well, I can see the admin page again - I haven't gone any farther than that.
I downloaded the OpenWRT source and tried compiling from hand to no avail. Connecting via serial would probably help but I don't know how to go about doing all of that. I might pick up a multimeter tomorrow and figure out the pins. I'd still have to get a serial converter to make the cable I believe. I've never done any of this before but I'm willing to spend some time trying to figure it out. Any pointers?
As mentioned by stains it's the same as DIR600 A1 (FCCID: KA2DIR600A1). I see AR7240 + AR9285 + 4MB winbound flash + 256Mb SDRAM. What confuses me is for some reason the FR-54RTR is marketed as Wireless-G while DIR-600 and 601 are 150-N.
There aren't ready-to-use connectors for UART like some other boards. I can see some tinned connectors but I was not sure. Thanks to another discussion on a different board with same chip http://www.dd-wrt.com/phpBB2/viewtopic.php?p=365012, I compared the pinouts and believed I should use the three round ones, which makes GND, TX and RX. One of them is apparently ground. The other two are measured at 2.5V and 1.25V respectively.
I found some interesting discussion about using cell phone data cable http://www.nslu2-linux.org/wiki/HowTo/AddASerialPort, which reminds me about my 5-year old samsung data cable. Fortunately it only took me 10 mins to dig it up from my trash dump. I pried it open and identified RX by using a jumper wire to short pins and looking closely at my terminal emulator for garbage text. Then I connected ground and RX. Reboot the router and voila, hello BOOTLOADER. After another round of trial and error I got TX too.
I would try loading firmware from TFTP server tomorrow and let you guys know if I can make it.
Quote:
U-Boot 1.1.4 (Apr 17 2009 - 14:44:49)
AP91 (ar7240) U-boot
DRAM:
sri
#### TAP VALUE 1 = 8, 2 = 9
32 MB
Top of RAM usable for U-Boot at: 82000000
Reserving 243k for U-Boot at: 81fc0000
Reserving 192k for malloc() at: 81f90000
Reserving 44 Bytes for Board Info at: 81f8ffd4
Reserving 36 Bytes for Global Data at: 81f8ffb0
Reserving 128k for boot params() at: 81f6ffb0
Stack Pointer at: 81f6ff98
Now running in RAM - U-Boot at: 81fc0000
id read 0x100000ff
flash size 4194304, sector count = 64
Flash: 4 MB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: ag7240_enet_initialize...
Fetching MAC Address from 0x81fe6e50
: cfg1 0xf cfg2 0x7014
eth0: 00:03:7f:e0:09:ab
eth0 up
No valid address in Flash. Using fixed address
: cfg1 0xf cfg2 0x7214
eth1: 00:03:7f:09:0b:ad
ATHRS26: resetting s26
ATHRS26: s26 reset done
eth1 up
eth0, eth1
Hit any key to stop autoboot: 1 0
## Booting image at bf040000 ...
Image Name: Linux Kernel Image
Created: 2009-09-16 3:16:31 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 980513 Bytes = 957.5 kB
Load Address: 80002000
Entry Point: 802b0000
Verifying Checksum ... OK
LZMA Umcompressing Kernel Image ... Image loaded from 80002000-802d8086
OK
No initrd
## Transferring control to Linux (at address 802b0000) ...
## Giving linux memsize in bytes, 33554432
Starting kernel ...
Booting AR7240(Python)...
Linux version 2.6.15--LSDK-7.3.0.260 (root@172.21.65.65) (gcc version 3.4.4) #1 Wed Sep 16 10:43:44 CST 2009
Wed Sep 16 10:58:00 UTC 2009
Entry gpio_ioctl init_module !!
sh: dcc: not found
lan mac = 00:01:23:11:11:11rc is BUSY now!
eth0: Cannot assign requested address
eth1: Cannot assign requested address
dhcpd_enabled::::::
DHCP client start.
domain empty
Failure parsing line 19 of /var/etc/udhcpd.conf
Failure parsing line 20 of /var/etc/udhcpd.conf
Failure parsing line 21 of /var/etc/udhcpd.conf
DHCP server start.
device_lan_ip=192.168.0.1 , device_lan_subnet_mask=255.255.255.0
max_leases value (254) not sane, setting to 100 instead
Unable to open /var/misc/udhcpd.leases for reading
eth0 Link encap:Ethernet HWaddr 00:26:5A:CB:1C:08
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
TFTP main
standard_tftp_server launched on port 69.
Sending discover...
Wed Sep 16 10:58:00 UTC 2009
ERRO: There must be at least 2 Vif's where one is upstream.
wan_ipaddr == NULL, firewall don't start
Start Firewall: Clear iptables
killall: crowdcontrol: no process killed
killall: wakeOnLanProxy: no process killed
Sending discover...
rc is IDLE now!
Sending discover...
wantimer: dhcpc_release (VCT_DISCONNECT)
DHCPC Received SIGUSR2=>DHCPC Release
Performing a DHCPC release
Entering released state
Posted: Tue Feb 16, 2010 1:48 Post subject: Loaded firmware with factory web
Continued from last night. Before trying TFTP server approach, I decided to give the the web upload another shot. As it kept telling me the firmwares (tried openwrt-squash, openwrt-jffs and DIR-601-A1) were bad, I figure the console should print something with the detail cause. It turned out to be mismatched hardware ID.
As I recalled the last step for building the firmware was to append HW ID to the end of squash FS, I brought up two versions of .config files and found their HW IDs to be slightly different: AP91-AR7240-RT-090223-01 vs AP91-AR7240-RT-090223-00. I edited the fw and open-wrt loaded without problem with from factory admin web.
So I guess this is a good news for those who do not want to mess with the hardware. Just use HEX editor to edit the HW ID (at the end of the file) for the favorite FW file of your choice and you are good to go.
So far I can telnet but HTTP returns a message saying "Not Found" at http://192.168.1.1/luci. Still need to learn how to configure open-wrt. I will come back with more info if I can get httpd working.
So far I can telnet but HTTP returns a message saying "Not Found" at http://192.168.1.1/luci. Still need to learn how to configure open-wrt. I will come back with more info if I can get httpd working.
So far I can telnet but HTTP returns a message saying "Not Found" at http://192.168.1.1/luci. Still need to learn how to configure open-wrt. I will come back with more info if I can get httpd working.
Posted: Tue Feb 23, 2010 5:41 Post subject: DD-WRT support for DIR-600 A1
Any idea how long before we see DD-WRT for this router? I need to set up a repeater bridge here in a RV park with Tengo internet. I only get a strong signal in the front of our mobile home. Thanks,
Interesting. I don't have an issue with chained router. But PPPoE is very problematic for me. Once PPP is connected, every time I run a bandwidth check my DSL modem will freeze up. The problem persists even if I restart the router. The only way to recover is to reboot the modem. If I just do web browsing it works fine. So I guess it's just an issue of heavy traffic. I tried to set MTU (before seeing your post) to the 1492, which is the one used by my old router but it didn't help. I will try it again with 1400 tonight.
monte2 wrote:
I upgraded to OpenWRT KAMIKAZE (bleeding edge, r19655), build from 2/17/2010, and I was seeing the same issue.
After trying lots of different configurations with tc and mtu, I'm finding that if I just set MTU=1400 on the wan interface it seems to be stable.
Just add the line: option mtu 1400
Under "config interface wan" in /etc/config/network.
Then reboot the router. (Restarting the network after changing mtu seems to leave the wan interface broken.)
At higher mtu settings I am able to crash the wan interface with a simple ping flood where packet data == MTU.
Posted: Thu Feb 25, 2010 16:40 Post subject: Other open issues
I'm currently using the router as a QOS gateway and it appears to work. Some issues remained:
1) DHCP server never worked. Have to manually assign IPs to client computers.
2) WAN interface problem with PPPoE as mentioned previously.
3) Limited flash capacity: basically I want all three features: luci web admin, madwifi and QOS. But there is never enough space for me to install more than one of the feature listed.