OpenWrt Forum Archive

Topic: How to build openwrt for asus rt-n16

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

Hello, Everyone, sorry for trouble you.

Now I'm trying to build openwrt for asus rt-n16 which is using bcm4718.

The steps I did is

get the sources from openwrt svn server, and run

./scripts/feeds update -a 
./scripts/feeds install -a 
make menuconfig

But problem comes out when doing the config, I found that there is no profile named bcm47xx or rt-n16.

The only broadcom profiles that I found is BCM2708/BCM2835, BCM63XX, and BCM947XX/BCM953XX

So How can I do the menuconfig to finish the config for rt-n16?

Thanks.

Well several have because I am running it on one. Sorry I assumed there was enough info there for you. I used a binary image for mine. Ask on that thread?

coolspace04 wrote:

But problem comes out when doing the config, I found that there is no profile named bcm47xx or rt-n16.

The only broadcom profiles that I found is BCM2708/BCM2835, BCM63XX, and BCM947XX/BCM953XX

So How can I do the menuconfig to finish the config for rt-n16?

BCM947xx/BCM953XX is the correct one because = brcm47xx branch
and brcm47xx supports the BCM4718A1 CPU on the Asus RT-N16

The brcm47xx boards all share one image as "sysupgrade" ( openwrt-brcm47xx-squashfs.trx ) and different  images for (native web ui) flashing (named images, with headers that contain ID because flashing is verified).

Named images are created by makefile see:
https://dev.openwrt.org/browser/trunk/t … e/Makefile

zloop wrote:
coolspace04 wrote:

But problem comes out when doing the config, I found that there is no profile named bcm47xx or rt-n16.

The only broadcom profiles that I found is BCM2708/BCM2835, BCM63XX, and BCM947XX/BCM953XX

So How can I do the menuconfig to finish the config for rt-n16?

BCM947xx/BCM953XX is the correct one because = brcm47xx branch
and brcm47xx supports the BCM4718A1 CPU on the Asus RT-N16

The brcm47xx boards all share one image as "sysupgrade" ( openwrt-brcm47xx-squashfs.trx ) and different  images for (native web ui) flashing (named images, with headers that contain ID because flashing is verified).

Named images are created by makefile see:
https://dev.openwrt.org/browser/trunk/t … e/Makefile


Thanks zloop.

So could you please share a detailed steps for building openwrt for rt-n16?

As I tried select BCM947XX/BCM953XX, but later in the second selection, there are only bcm43xx profiles, no bcm47xx profile.

Thanks

Problem solved.

I after spend several hours building the package, I found that just select BCM947XX and let all others to be default settings. then doing the build process, bcm47xx image can come out.

Thanks all for the help!

Hello! I installed the firmware openwrt (http://openwrt.razvi.ro/barrier_braker_ … uashfs.trx) on my router ASUS RT-N16. Everything still works, but does not light up the LED wi-fi on the case, although the wi-fi network is working. This is as it should be or somehow fix?

Non working LEDs is a minor bug.  File a ticket or edit source :

LED logic is in package broadcom-diag ( see https://dev.openwrt.org/browser/trunk/p … src/diag.c )
afaik there is a way to test the LEDs which are attached to GPIO pins with some simple commands via /proc (echo 1>/proc/...gpio_pin_that_controls_led/ ) maybe look at some wiki page

Who is connected to the asus rt-n16 flash drive? How to do it correctly, as the mount, which packages should be installed? I want to stick out to ftp server, or simply disable shared access.

xzsdre wrote:

Hello! I installed the firmware openwrt (http://openwrt.razvi.ro/barrier_braker_ … uashfs.trx) on my router ASUS RT-N16. Everything still works, but does not light up the LED wi-fi on the case, although the wi-fi network is working. This is as it should be or somehow fix?

http://www.znau.edu.ua/temp/asus-rt-n16 … README.txt

If you have wifi led constantly off try following to get it working (reboot when done):
nvram set sb/1/leddc=0x5A000A
nvram set wl0gpio7=8
nvram commit

sash-kan, thank you for advice
If you have wifi led constantly off try following to get it working (reboot when done):
nvram set sb/1/leddc=0x5A000A
nvram set wl0gpio7=8
nvram commit
Its working!:-)

Hi,
I build an image from trunk for the Asus RT-N-16 with Target System "Broadcom BCM947xx/953xx" and Target Profile "Broadcom SoC, all Ethernet, BCM43xx WiFi (wl, proprietary)". The image was building fine and I put it onto the box. Everything is working except wireless 802.11n. I had a look at openwrt's broadcom page (http://wiki.openwrt.org/doc/hardware/soc/soc.broadcom.bcm47xx ) and tried to configure the wifi device with the "wl" utility, but the utility itself allowed only to set rates up to 54 MBit. I can set the 40 Mhz channel width, but no higher rates than 54 MBit. Did anyone get wireless 802.11n working with the proprietary "wl" broadcom-wl driver?

xzsdre wrote:

sash-kan, thank you for advice
If you have wifi led constantly off try following to get it working (reboot when done):
nvram set sb/1/leddc=0x5A000A
nvram set wl0gpio7=8
nvram commit
Its working!:-)

Is this safe to do? Does it not mess up your NVRAM? Were you succesful too? In that case I will try it and add it to the wiki.

I think you can already download the sdk from Asus website. They developed a sdk called AsusRT which is actually based on openwrt source code.
http://www.asus.com/Networking/RTN16/#support

(Last edited by vubvub on 8 Oct 2013, 16:09)

Grabbel wrote:
xzsdre wrote:

sash-kan, thank you for advice
If you have wifi led constantly off try following to get it working (reboot when done):
nvram set sb/1/leddc=0x5A000A
nvram set wl0gpio7=8
nvram commit
Its working!:-)

Is this safe to do? Does it not mess up your NVRAM? Were you succesful too? In that case I will try it and add it to the wiki.

Yes, I have it working :-) I do not know anything specifically about the NVRAM, and how it should work. I'm just after installing OpenWRT did not work LED Wi-Fi. Asked here, people have pointed to the source of solutions problemmy. Did - works :-)

The discussion might have continued from here.