I would really hold off on the WRT320n untill DD-WRT supports it.
I upgraded from a WRT54Gs running DD-WRT to a WRT320n because i needed the higher throughput (testing a 50mbps connection for work) but the WAN speed decreases gradually untill a reset is required. Verified the issue is the router and not the modem. Linksys has not fixed the issue as yet.
Just bricked (no cfe, power light blinks constantly) my wrt320n, while I was attempting to tftp rescue it from a too ambitious modification of the stock firmware.
I have serial and JTAG cables in the mail, but am not entirely sure where to hook them up. Strongly suspect the 2x7 holes labeled JP1 is the JTAG header, and JP3 on the underside of the PCB is the serial port. The exact pin layout of either are a mystery to me, so if anyone, Kellerweis?, figured them out please share. ;)
Edit: 15 minutes later, I notice it has labeled serial pads in the wan port like on the wrt610n. And 4 pads barely exposed in LAN port 3... wonder what those are for?
I took a chance that the serial pinout was the same as on the wrt610n, and hooked up a Nokia CA-42 clone cable to the pads. The CA-42 has a build in usb serial converter and RS232 to TTL 3.3V signal conversion. Here are the connections I used:
JP3 pin 2 - Pop port pin 7 (TX data)
JP3 pin 3 - Pop port pin 6 (RX data)
JP3 pin 5 - Pop port pin 8 (Data ground) (some cables use pop port pin 2 instead... but it wasn't even present on mine)
But apparently the wrt320n CFE doesn't have a -mem switch to the flash command. Sod... so I ended up installing a tftpd on a pc and putting the firmware in the tftpd's root dir. Then telling CFE to flash with the following command:
This bcm5356 and also bcm4716/4717/4718 are new generation mips32r2 cpus. We have some problems porting dd-wrt to it and not to break support for all other routers.
So please consider it "work in progress". But it surely will be done because most new Broadcom based routers will have this new cpu inside.
If this not work with support for older and other routers, why not making a new sepperate DD-WRT firmware line for this router wrt610n and wrt320n and new coming models with those bcm5356 and also bcm4716/4717/4718 chips.
This makes 2 line's of DD-WRT firmware's comptible for all without breaking others, but the only worse thing we got than,
We only must select the right firmware for the right router :-)
I hope i do not sound stuppid but it can be a solution.
Joined: 17 Apr 2009 Posts: 627 Location: Philadelphia, PA
Posted: Tue Jul 14, 2009 14:15 Post subject:
Hmm, good news! I have a 320n sitting here just waiting! I've read over on the Linksys forums that this unit is basically "broken" with Linksys firmware (slows to a crawl over time). Be interesting to see how it works with DD-WRT!
Great work, Eko - you the man! _________________ 1 x Linksys WRT160n v3
1 x Linksys WRT310n v1
1 x Linksys WRT600n v1.1
1 x Linksys WRT610n v1
1 x Linksys E2500
1 x Netgear WNDR3300
1 x Dlink DIR-825 v1
2 x Asus RT-AC66U
Just a friendly suggestion: these are the kinds of efforts where small personal donations to the DD-WRT project in general or to the developer specifically are most appreciated. _________________ 2x Asus RT-AC68U
If you disable uPNP the speed problems will mostly be fixed, i still have a problem with the internet speeds (not 1Gb) though and when i try to connect to my webserver it takes quite long before the connection is made and when there is a connection the different pages and pictures are loaded very slowly.
You can check for yourselves at http://www.katemoss.nl
I really hope that DD-wrt will come with a new firmware which will fix those problems (so i can enable uPNP again), i don't think linksys will come with a new firmware soon, saddly enough...
the 610N is around £130, so twice the price and all you get extra is a usb port and simulaneous 802.11n and 802.11g, hardly worth it.
Will stick to my WRT54GSv4 until a stable firmware for the 320N is out, wonder what the signal quality is like with no external antennas, anyone compared it to a WRT54G/S?
the 610N is around £130, so twice the price and all you get extra is a usb port and simulaneous 802.11n and 802.11g, hardly worth it.
Will stick to my WRT54GSv4 until a stable firmware for the 320N is out, wonder what the signal quality is like with no external antennas, anyone compared it to a WRT54G/S?
Not compared, but this one is an upgrade for my wrt54gl. Gonna use the wrt320n for the N and router capabilities, will make the wrt54gl a G access point.
I took a chance that the serial pinout was the same as on the wrt610n, and hooked up a Nokia CA-42 clone cable to the pads. The CA-42 has a build in usb serial converter and RS232 to TTL 3.3V signal conversion. Here are the connections I used:
JP3 pin 2 - Pop port pin 7 (TX data)
JP3 pin 3 - Pop port pin 6 (RX data)
JP3 pin 5 - Pop port pin 8 (Data ground) (some cables use pop port pin 2 instead... but it wasn't even present on mine)
But apparently the wrt320n CFE doesn't have a -mem switch to the flash command. Sod... so I ended up installing a tftpd on a pc and putting the firmware in the tftpd's root dir. Then telling CFE to flash with the following command:
This is my first time playing around with ddwrt and my first time on this forum, so if I am posting this in the wrong fashion let me know.
I picked up a WRT320N yesterday and I tried to flash it with one of the latest ddwrt SVN builds onto a few hours ago. Naturally it bricked, much like the post above.
However for these kind of units I would go for a phone jack one, TTL-232R-3V3-AJ or TTL-232R-3V3-WE. Make sure you get TTL level though. Might be cheaper to build out of a MAX232 or a USB chip.. but 16 pounds is quite cheap for the work involed and you get drivers that work with Windows 7 64bit.
Then I tried the method above. That failed for me. However, and I don't know why as this is the first time I see this hardware and/or CFE boot loader, maybe somethign with the TFTP server I used. I did check the TFTP transfer type though, and it was octet.
Instead I did this:
* break into CFE through CTRL-C
* issue "flash -ctheader : flash1.trx"
* upload "WRT320N_v1.0.02_006_US_code.bin" through the tftp2.exe (linksys utility?)
* issue "go"
After I managed to unbrick it this way I tried with the built in TFTP client in Windows 7 64bit, it work nicely too
C:\Users\niclas.lindgren\Downloads\WRT320N>tftp -i 192.168.1.1 put WRT320N_v1.0.02_006_US_code.bin .
Transfer successful: 4776960 bytes in 13 second(s), 367458 bytes/s
I am pretty sure you can push the image to the CFE during boot up if you have boot_wait on. But I don't know how to turn that on without a console of some sort, so it doesn't help those without a serial console.
If I tried with the CFE being the TFTP client against my servern, this happened over and over:
It seems to have to do with "fname=(null)" which should be the place where to flash the image I believe.
Not sure if this helps anyone in the bricking department, but I thought I'd share.
That said, I also have a WRT320N that I can use to help out with testing build. At the moment it seems I can't get the build on at all, not sure what I am doing wrong, or maybe I am using the wrong builds.
I will try setting up a toolchain and build from SVN.
I can confirm indeed that the router WAN speed will slowdown over time until I release and renew my WAN ip or reboot.
Hoping that I can upgrade to DD-WRT soon...
= 807A1726 t1 ($09) = 8073BD98