OpenWrt Forum Archive

Topic: Support x Asus RT-N12E B1

The content of this topic has been archived on 17 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

This product is very simila to RT-N14U the same chipset Mediatek MT7620N and Etrontech EM63a165ts-6g.


http://s11.postimg.org/41mrwl85f/Asus_RT_N12_E_B1.jpg



Trying to flash RT-N14U image :


U-Boot 1.1.3 (Apr  3 2014 - 17:08:04)

ASUS PRODUCT bootloader version: 1.0.0.0
Board: Ralink APSoC DRAM:  32 MB
ASUS ASUS PRODUCT gpio init : reset pin
enable ephy clock...done. rf reg 29 = 5
SSC enabled. swing=5000, upperbound=0
Ralink SPI flash driver, SPI clock: 29MHz
spi device id: c2 20 17 c2 20 (2017c220)
find flash: MX25L6405D
raspi_read: from:30000 len:1000
Maximum malloc length: 1024 KBytes
mem_malloc_start/brk/end: 0x81eaf000/81eb1000/81fb0000
*** Warning - bad CRC, using default environment

============================================
Ralink UBoot Version: 4.1.1.0
--------------------------------------------
ASIC 7620_MP (Port5<->None)
DRAM component: 256 Mbits SDR
DRAM bus: 16 bit
Total memory: 32 MBytes
Flash component: SPI Flash
Date:Apr  3 2014  Time:17:08:04
============================================
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768

Please choose the operation:
   0: Load System code then write to Flash via Serial.
   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.
   5: Load Boot Loader code to SDRAM via Serial.
   7: Load Boot Loader code then write to Flash via Serial.
   8: Load Boot Loader code to SDRAM via TFTP.
   9: Load Boot Loader code then write to Flash via TFTP.
0

3: System Boot System code via Flash.
raspi_read: from:4018a len:4

ASUS PRODUCT bootloader version: 1.0.0.0
raspi_read: from:40004 len:6
MAC Address: 1C:B7:2C:7C:98:BC
raspi_read: from:40004 len:6

## Checking 1st firmware at bc050000 ...
raspi_read: from:50000 len:40
   Image Name:   MIPS OpenWrt Linux-3.18.20
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1099985 Bytes =  1 MB
   Load Address: 80000000
   Entry Point:  80000000
raspi_read: from:50040 len:10c8d1
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Giving linux ramsize: 33554432 (32 MB)

Starting kernel ...

(Last edited by madmax on 12 Mar 2016, 13:03)

Up !!!

RT-N12E b1 and RT-N12+ are clones of RT-N11P

you can take n14 dts as a base, but some button and led gpios have to be changed

madmax wrote:

Up !!!

Hi,

I'm trying to get OpenWRT running on a RT-N12E B1. Would you care to provide some more detailed steps of how you got it to work? Is it necessary to access (i.e. solder) the UART?

Unfortunately, I'm not even really sure I'm getting the device to enter rescue mode. When switching on the device while holding the WPS/reset button, the wifi, WAN and ethernet leds start to blink slowly, while the power led is continuously on. I'd assume that means it is in rescue mode, but the ASUS manual states that the power led should blink slowly. Which it doesn't. Might be that ASUS guys don't themselves remember how their devices work...

Anyhow, when the device is in the assumed rescue mode, I'm able to tftp the RTN-14U package to the router, and after the package has been transmitted, the router reboots. However, it just boots its own original firmware, no sign of OpenWRT.

I've also tried to use that ASUS rescue tool on Windows, but that just keeps telling me, that the router is not in rescue mode (though the tool is apparently able to detect the router, since it does not give me that message when the router is not connected at all).

Thanks for any pointers.

J

(Last edited by dev_null on 7 May 2017, 17:50)

could you please assist me with this config...

just a general guideline would help. Thanks

I'm just about to submit a patch for LEDE trunk for RT-N12Eb1 / RT-N11P / RT-N12+. Based on wikidevi and other sources they all share the same board (FCC ID MSQ-RT1901).

Regards,
-w-

The discussion might have continued from here.