Which version of TomatoUSB for this router (WRT350N v1)?
I tried flashing from Linksys to extras+vpn, and it super-bricked… to where not even the ethernet switch comes up. I'm going to have to go through serial console now.
Hardware is V1. I want to switch from dd-wrt, because dd-wrt tends to lose all its settings.
Yes, you will have to use a serial connection to the router to recover. Tomato will get stuck in an endless reboot loop. I have serial connection through the pad on the inside of the
wan port. I can send details on how to make a rig to use the pins there if you want, found info for this at ddwrt forums.
I achieved a serial console using nothing more than a bit of IDE cable, a pair of nail clippers (to scrape the inner two of the four conductors), and some clips to go to my serial adapter. I scraped the two conductors to expose them, then bent the ribbon around to make the conductors protrude enough for a broken-clip ethernet cable to hold the thing in place. No tinning needed.
Oh, and my old Xilinx board was the only ttl-to-5v sort of adapter I had around. Note that I only connect TX and RX; I get ground by plugging the USB plug from my board into the router.
Anyway, now that I have serial console, but NO ETHERNET LINK… how can I flash back to anything?
Note that doing "modprobe et" results in "no such device".
Okay, I managed to unbrick the thing…. Had to hammer enter to interrupt tomato boot, then manually attach wifi to an open network and netcat the firmware over. Double-checked the md5sum, of course.
Seriously, would it kill them to include zmodem, or kermit, or such, for sending files over serial?
thank you for documenting your steps so well.
where did you get info that the wrt350n is a V1 board?
did you, by any chance, load a modded cfe from the dd-wrt forums, that allows k26 builds?
were you able to get to the cfe by interrupting boot on the serial console? if so, you should be able to configure one of the ethernet ports to 192.168.1.1, and then tftp the original linksys firmware (tftp -i 192.168.1.1 put firmware.bin) from your pc immediately after entering "flash -ctheader : flash1.trx" on the serial console.
i struggled for hours to get a flimsy serial cale connection. could you send a picture of your cable? sounds great!
i might be motivated to try totamto again if i can get the serial connection good.
This router requires bcm57xx switch driver (which is only included into "NO-USB Std" Tomato builds for WRT310N support), and special initialization code - without this Ethernet ports won't work.
I started to work on WRT350N support with slimey, and we partially succeeded in making it to boot up with WAN and LAN ports and wireless working - however there are some unsolved problems left. Recently I got sidetracked, but I'm still going to get back to it eventually - hopefully soon.
ghoffman, I had done the same as danag when it came to making the cable and getting it to stay in the wan port see the first link from ddwrt forums for details. I am including some other links as well to help de-brick the 350n as they can sometimes be stubborn to recover.
Here is a pic of the cable i came up with, works quite nicely.
Tip: Use a nail file to get to the bare wires in the ribbon cable and dab hot glue or some other glue in between the wires to keep them apart from each other to prevent shorts, etc.