Posted: Sat Nov 13, 2010 21:40 Post subject: Need help with unlisted Router SMC Barricade N
The SMC Barricade N uses Ralink hardware, has a 4MB flash chip, and 4MB RAM. IThe Barricade is not listed on the supported devices, but honestly, I bought it for $20, and it can't do bridge functions like I thought which makes it less than useless for me, so I kind of just want to attempt to flash it and install, with the full understanding that it might brick it. Where can I download the generic Ralink installation?
So the router has 16MB of ram and not 4MB.
Maybe you understand now why you have to detail the chips...
dd-wrt support is possible with that hardware spec, but there is still info missing from you.
I'm not into message ping-pong so do it right this time!
Does the router have a model number or does SMC only manufacture one router?
Does it have an FCC ID? _________________ Kernel panic: Aiee, killing interrupt handler!
There is no generic Ralink version of dd-wrt that you easily can load on the router at this time.
Support for it may appear in the future if someone donates a router to Brainslayer or if some daring user manages to modify a current Ralink build to run on it. _________________ Kernel panic: Aiee, killing interrupt handler!
I have one of these now and it can run dd-wrt but there is no simple way of of getting dd-wrt on the router.
The stock firmware seems to have a check for the linux kernel size and does not accept updates to dd-wrt via the gui.
It is possible though to load the Senao ESR-9752 dd-wrt build with the help of tftp and a serial console connection.
It is a nice little piece of router, very well built.
The only disadvantage I can see and which it shares with other Ralink based routers is the small amount of free ram, 3.5MB with wifi disabled and around 1MB when enabling wifi. _________________ Kernel panic: Aiee, killing interrupt handler!
I can't help you with the serial pinout since I've not got the router here but from what I remember the 5 pins where +3.3V , tx (or rx), rx (or tx), gnd, and unused.
Baudrate was 115200, N, 8, 1 in the bootloader and dd-wrt initializes the port to 57600 later when the firmware is running.
I have saved the log from the flashing session, using ESR-9752 firmware.img from dd-wrt and renamed to test.bin.
My commands are underlined
U-Boot 1.1.3 (Nov 4 2009 - 18:13:51)
Board: Ralink APSoC DRAM: 16 MB
relocate_code Pointer at: 80fb0000
flash_protect ON: from 0xBF000000 to 0xBF01D423
flash_protect ON: from 0xBF030000 to 0xBF030FFF
*** Warning - bad CRC, using default environment
Ralink UBoot Version: 3.3
ASIC 3052_MP2 (Port5<->None)
DRAM component: 128 Mbits SDR
DRAM bus: 16 bit
Total memory: 16 MBytes
Flash component: NOR Flash
1: Load system code to SDRAM via TFTP.
2: Load system code then write to Flash via TFTP.
3: Boot system code via Flash (default).
4: Entr boot command line interface.
9: Load Boot Loader code then write to Flash via TFTP.
You choosed 4
4: System Enter Boot Command Line Interface.
RT3052 # tftpboot
netboot_common, argc= 1
NetTxPacket = 0x80FE5640
KSEG1ADDR(NetTxPacket) = 0xA0FE5640
NetLoop,call eth_halt !
NetLoop,call eth_init !
Trying Eth0 (10/100-M)
Waitting for RX_DMA_BUSY status Start... done
Header Payload scatter function is Disable !!
*** Warning: no boot file name; using 'test.bin'
Using Eth0 (10/100-M) device
TFTP from server 10.10.10.3; our IP address is 10.10.10.123
TIMEOUT_COUNT=10,Load address: 0x80100000
Loading: Got ARP REPLY, set server/gtwy eth addr (00:13:f7:66:1a:49)
Posted: Wed Jan 22, 2014 11:59 Post subject: DD-WRT running on SMC Barricade SMCWBR14S-N4
Thanks to LOM and BobZombiE, I was able to flash dd-wrt firmware.bin for the Senao ES-9752SC onto the SMC Barricade SMCWBR14S-N4, and it is running perfectly.
The firmware: I used BobZombiE's link to download firmware.bin.
1. Remove the four rubber feet and the screws under them.
2. If you put the circuit board on a table so that the WAN and LAN connectors are facing you, power socket on your right, and the antenna on your left, then the 5 pins, from left to right, are Unused, Transmit, Receive, and Vcc (3.3VDC).
3. To connect to my computer's RS-232 DB9 connector, I built my own cable as follows. Connect the Transmit pin to a 2.2K resistor, which is connected to a 1K resistor to ground. The junction between the two resistors is connected to the base of a 2N2222 transistor, whose emitter is grounded, and whose collector is tied to +5VDC via a 1K resistor. The collector is tied to pin 3 of the DB9 RS-232 connector on the back of my computer.
Pin 2 of the DB9 RS-232 connector is connected to the base of another 2N2222 transistor via a 1K resistor. Connect a 1N4148 diode so that a current can flow from ground into the base. Ground the emitter. Tie the collector to +5VDC via a 1.5K resistor, and to ground via a 2.2K resistor. The collector is connected to the Receive pin on the SMCWBR14s-N4 board.
Connect the ground pin of the SMCWBR14s-N4 board to the ground of the above transistor circuit.
3. I connected an ethernet cable from my WinXP computer to a LAN port on the SMC.
The software for my WinXP computer:
1. I used HyperSerialPort as a terminal emulator, and set baud rate at 115200, 8 bits, no parity, 1 stop bit, flow control none, no echoing of characters. (In the Settings tab, you have the option of "Append line feeds to incoming line ends". I found that if I selected this, the terminal display is more readable but then I cannot use my keyboard to enter a "2", needed to flash.)
2. I downloaded Tftpd32 and installed it. When you run Tftpd32, the "Current Directory" should be the folder in which you put the firmware.bin of Senao ES-9752SC, and for the "Server Interfaces" I selected my network card. In "Settings", GLOBAL tab, I unchecked DHCP server (since the SMC will assign IP addresses), and under the TFTP tab, Base Directory should point to the same folder where firmware.bin is.
How to flash firmware.bin onto the SMC:
1. Test the RS-232 connection. Hit the reset button on the SMC. In HyperSerialPort terminal, you should see the SMC booting itself up. After a while, it will begin to listen to the LAN port. At that point, it is fully booted up.
2. Hit the reset button again, and immediately it the "2" key on your keyboard once. (I found that if I hit "2" multiple times, the SMC booted into the default option "3" instead.)
3. The HyperSerialPort terminal should read "Are you sure?(Y/N)". Type Y (and return).
4. When it shows "Input device IP (10.10.10.123) ==:10.10.10.123, I hit backspace multiple times, each time the terminal echoed a black symbol on the screen. I kept hitting backspace until it stopped echoing the black symbol. Then I typed 192.168.2.1 (the default IP address of the SMC) and hit return.
5. For Input server IP (10.10.10.3) ==:10.10.10.3, I did the same backspacing, then typed 192.168.2.100 (the IP address of my computer as assigned by the SMC). As a quick check, the Server Interfaces for Tftpd32 should show the same.
6. When HyperSerialPort terminal asked for Input Linux Kernel filename ()==:, I typed firmware.bin and hit return.
If all goes well, the SMC (as a tftp client) got this firmware.bin from the Tftpd32 server, flashed it onto the SMC, and rebooted the kernel all by itself. (If it gets stuck at "Got it T T T T ...", don't worry. It just means that for some reason, the SMC tftp client cannot read the firmware.bin file from the Tftpd32 server. Just unplug the power from the SMC, and start over after checking the Tftpd32 server settings.)
Once the new kernel rebooted, my terminal screen becomes jibberish because dd-wrt uses a baud rate of 57600. Once I adjusted that, the terminal keeps saying "ra(0) not operational" or something like that (Sorry, I did not write that down) again and again. I unplugged power from the SMC, waited 5 seconds, plugged it back, and voila! DD-WRT ran successfully.
On my WinXP machine, I rebooted the network card (because before it was assigned an IP address of 192.168.2.100 by the stock SMC firmware. Now, dd-wrt assigns 192.168.1.137 to it).
I launched Firefox web browser, set URL to 192.168.1.1, and saw that dd-wrt was asking me to change password.
In conclusion, thank you, LOM, thank you BobZombiE.