Linksys WRT350N v1.0

This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram.
DO NOT BUY DEVICES WITH 4MB FLASH / 32MB RAM if you intend to flash an up-to-date and secure OpenWrt version onto it! See 4/32 warning for details.

1) This device does not have sufficient resources (flash and/or RAM) to provide secure and reliable operation.
This means that even setting a password or changing simple network settings might not be possible any more, rendering the device effectively useless. See OpenWrt on 4/32 devices what you can do now.

2) OpenWrt support for this device has ended in 2022.
19.07.10 was the last official build for 4/32 devices.

Useful for identifying shrinkwrapped units. The S/N can be found on the box, below the UPC barcode.

Model S/N
WRT350N v1.0 -- Not available in Europe? CNQ01
WRT350N v2.0 -- Only available in Europe? SNQ00

Flashing the pre-built openwrt-wrt350n_v1-squashfs.bin from could very well disable all ethernet ports on the router, forcing you to install a serial port to recover. Search the forums and you'll see that happened to a bunch of people.

It is possible to run an older kamikaze bcrm-2.4 version of OpenWrt on the v1.0 hardware. You may need to build this yourself to enable the required drivers.

Support for the wrt350n v1.0 was added to SVN with changesets 11466-11471 (broadcom 2.4 build). In order to use the device, make sure the bcm57xx package is included in your image (selected as * in menuconfig). Without this package installed, the switch will not come up and you'll have to use a serial console to recover.

Wireless works as long as kmod-brcm-wl-mimo is installed. USB also works with kmod-usb-ohci, I have tested it as a print server with p9100d.

The switch in the wrt350n v1 is a little different from the older switch chips. By default, it will forward packets between the LAN and WAN, much like a normal switch. This is a problem during bootup because boot_wait will activate the switch to wait for an image. The only way I could find to make the switch not forward packets on bootup was to set the following NVRAM variables:

Disabling boot_wait is a bad idea, so make sure you really need it off before doing so.

nvram set boot_wait=off
nvram set manual_boot_nv=1
nvram unset disabled_57xx
nvram commit

The CFE bootloader brings up the ethernet with IP and listens for a TFTP “put” for a few seconds. If a file is uploaded via TFTP, the header is read and the board type and checksum is validated before it is programmed into flash. The default firmware image from OpenWrt may not have the required header. This can be dealt with via the serial port like so:

Start sending the firmware from a linux computer on the same network:

echo -e "binary\nrexmt 1\ntimeout 60\ntrace\nput openwrt-wrt350n_v1-squashfs.bin\n" | tftp

Receive the firmware file and program it to flash:

flash -ctheader : flash1.trx

The WRT350N v1.0 is based on the Broadcom 4785 r2 running at 300MHz cpu. It has 8 MB flash and 32 MB SDRAM. The wireless NIC is a Broadcom Cardbus card with maybe a BCM5397 Chipset on the switch. The WRT350N runs 802.11 B, G, and Draft N wireless protocols. It provides 4 gigabit LAN ports, 1 WAN port and a USB 'storage link' port.

The silver panels on the top and bottom are snapped into place at the rear of the unit only. They have a slide fitting at the front of the unit, so don't pry them apart at the front. The font of the case slides forward and off. Removing the silver covers reveals the screws, which are Torx T10. Once these are removed, the case come apart easily.

Connector JB3 has TTL 3.3v UART

Pin Function
1 3.3v
2 Tx
3 Rx
4 unknown
This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2024/02/12 08:58
  • by