Modify

Opened 4 years ago

Last modified 2 years ago

#16796 new enhancement

Ubiquiti NanoBeam

Reported by: gregorprivat@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: toolchain Version: Trunk
Keywords: Cc:

Description

The UBNT NanoBeam is the successor of NanoBridge (whis is end of life). No current UBNT image works since this uses another SoC/flash layout.

U-Boot 1.1.4-s751 (Aug 21 2013 - 12:06:27)

Board: Ubiquiti Networks AR9342 board (e4e5-24.1122.0030)
Reset: Normal
DRAM:  64 MB
Flash:  8 MB (0xc2, 0x20, 0x17)
Net:   AR8035
eth0
Radio: 0777:e4e5
Hit any key to stop autoboot:  0 
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.32.60
   Created:      2013-08-30  13:24:09 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1000716 Bytes = 977.3 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Booting Atheros AR934x

Flashing the only other UBNT AR9342 image (UAP-Pro) via TFTP fails:

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
find_mtd_part
Clearing partition 'cfg':
        erasing range 0x9F7B0000..0x9F7EFFFF: .... done
Erased 4 sectors
Waiting for connection: /
Receiving file from 192.168.1.19:49531
Received 7274844 bytes
Firmware Version: BZ.ar934x.v6.0.0-OpenWrt-r40422
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Warning: partition jffs2 not found on flash memory! Skipped.

Firmware update complete.

This is the flash layout:

ar7240> mtdparts

device nor0 <ath-nor0>, # parts = 6
 #: name                        size            offset          mask_flags
 0: u-boot                      0x00040000      0x00000000      0
 1: u-boot-env                  0x00010000      0x00040000      0
 2: kernel                      0x00100000      0x00050000      0
 3: rootfs                      0x00660000      0x00150000      0
 4: cfg                         0x00040000      0x007b0000      0
 5: EEPROM                      0x00010000      0x007f0000      0

active partition: nor0,0 - (u-boot) 0x00040000 @ 0x00000000

defaults:
mtdids  : nor0=ath-nor0
mtdparts: mtdparts=ath-nor0:256k(u-boot),64k(u-boot-env),1024k(kernel),6528k(rootfs),256k(cfg),64k(EEPROM)

Attachments (0)

Change History (21)

comment:1 follow-up: Changed 4 years ago by valent@…

And there are few devices on Wiki that have AR9342, so support is not impossible to do. What needs to be done?

comment:2 Changed 4 years ago by mmitar@…

CCing.

comment:3 in reply to: ↑ 1 Changed 4 years ago by gregorprivat@…

Replying to valent@…:

And there are few devices on Wiki that have AR9342, so support is not impossible to do. What needs to be done?

A new device needs to be created inside the toolchain with the correct flash layout. Sadly i don´t know where to do this...

comment:4 Changed 4 years ago by valent.turkovic@…

Ubiquiti has renamed NanoBeam line to PowerBeam line and added few new devices, most powerful model is PBE-5AC-500, radio chip is 801.11ac and antenna is 27dBi.

comment:5 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:6 Changed 3 years ago by openwrt@…

Hi,

I received a new NanoBeam NBE-M5-19 and, of course, the first thing I did was to try to install OpenWrt.

I could flash the "openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-sysupgrade.bin" image from the original firmware (fwupdate.real tool) and from rescue mode via TFTP, but after that I couldn't access the device (no ping, no telnet).

The NanoBeam uses the same AirOs firmware as the new NanoStation M5 (they have the same, or very similar chip) which is supported by OpenWrt. Maybe only a small modification needs to be made to make it work with the NanoBeam too.

I posted some info and logs here: http://wiki.openwrt.org/toh/ubiquiti/nanobeam . I'll add more info as the device gets support.

Regards,

comment:7 follow-up: Changed 3 years ago by anonymous

By the way, it seems that the device enters failsafe mode using the button method, but there again it does not respond to any network command (ping, telnet).

comment:8 follow-up: Changed 3 years ago by valentt

But does terminal via serial work as expected?

comment:9 in reply to: ↑ 7 Changed 3 years ago by anonymous

Replying to anonymous:

By the way, it seems that the device enters failsafe mode using the button method, but there again it does not respond to any network command (ping, telnet).

I have nanobeam M2-400, If I change kernel boot parameter to root=31:04 and xw-squashfs works fine.
But I get problem with 802.1q over wlan0 - no rx frames on other side. Seems ubnt uses it's own wireless driver based on madwifi and in ubnt firmware vlan over wlan works. I need many vlans and Multi-SSID not suitable for me.

comment:10 in reply to: ↑ 8 Changed 3 years ago by openwrt@…

Replying to valentt:

But does terminal via serial work as expected?

I don't dare to disassemble the device. Unlike the NanoStations, I don't see any screw or anything to open it without breaking it.

Replying to anonymous:

I have nanobeam M2-400, If I change kernel boot parameter to root=31:04 and xw-squashfs works fine.

Where do you make such change?

comment:11 Changed 3 years ago by Muzer

Has anyone attempted installation on a PowerBeam PBE-5AC-500? We are considering purchasing one but only if it is definitely possible to install OpenWRT (it's a bit pricey to just hope).

comment:12 Changed 3 years ago by Brian

The NanoBeam M5 19 still doesn't work with any image. Mostly I could ping IPv6, but not IPv4. Roger from qMp suspects that switching from kernel 3.10 to 3.14 in OpenWrt may have broken support.

The NanoBeam M5 16 does work with one image, the 3.1 "openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin".

The M5 19 doesn't work with any image at all.

Last edited 3 years ago by Brian (previous) (diff)

comment:13 Changed 3 years ago by valentt

I have tested both "ubnt-loco" and "ubnt-nano" XW trunk images [1] [2] two days ago, and they both worked.

Only issue with "ubnt-nano" image is that is expects both eth0 and eth1 ports but NanoBeam M5 device has only one port, so you need you need to replace eth0 and eth1 ports in /etc/config/network config file.

I have tested speeds between two NanoBeam M5-16 devices and got maximum of 60 Mbps (two 30 MBps duplex streams) which is much lower than with original firmware.

When testing original firmware I got over 160 Mbps (around 100 + 60 Mbps in duplex) and 150 Mbps (simplex one way traffic).

[1] https://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
[2] https://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin

comment:14 Changed 3 years ago by valentt

Can anybody test and confirm speeds with their own benchmarks?

comment:15 Changed 3 years ago by Mitar

What about NBE-5AC-19? That one looks really cool. Gigabit Ethernet, 450 Mbit connections. But they are AC, so I am not sure what is support for that in ath9k?

Datasheet: http://dl.ubnt.com/datasheets/NanoBeam_ac/NanoBeam_ac_DS.pdf

comment:16 follow-up: Changed 3 years ago by valentt

If anybody sends a pair of NBE-5AC-19 to me I'll gladly test them and report back how they work with OpenWrt.

comment:17 follow-ups: Changed 3 years ago by mjc

NBE-M5-300 is supported by trunk loco-m-xw image [1] (Pre-built trunk images do not come with any web interface or GUI), downgrade to 14.07 via sysupgrade is possible with nano-m-xw image [2] (without preserving the settings)

I don't have other NanoBeams, so I can't test them. But I think it will also work for the NBE-M2-400, NBE-M5-400 and NBE-M5-620.

I have not tested the maximum throughput, yet. Maybe I test in the next days...

[1] https://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin
[2] https://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin

comment:20 in reply to: ↑ 16 Changed 3 years ago by anonymous

Replying to valentt:

If anybody sends a pair of NBE-5AC-19 to me I'll gladly test them and report back how they work with OpenWrt.

I bought 1, I have not tested the transfer speeds but it is not backward compatible, if you are planing to buy 1 to use with older equipment don't.

comment:21 Changed 2 years ago by endoedgarjunior@…

I have one NBE-M5-400 and I tried every single firmware from this page but every single firmware fails the same way.
I can flash the firmware but afterwards I don't have access to the Web Admin, SSH, ping, telnet, etc

Where can we find a solution?

Thnx

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.