You are here

Nano Bridge M5 xm hardware, reports unsupported hardware

6 posts / 0 new
Last post
w6abj
Nano Bridge M5 xm hardware, reports unsupported hardware
Good Day, 
I flashed my NanoBridge M5 with 3.15.1.0 but according to this it is being reported as a Bullet M, ch.179 is 
not available which is what we are using for our mesh. The question is should I flash it
with the Bullet M firmware ?

Thanks 
Rich, W6ABJ

node: W6ABJ-NB5-Q-1
model: Ubiquiti Bullet M

!!!! UNSUPPORTED DEVICE !!!!
boardid: 0xe235
Device has not been tested. Please file a ticket with your experiences.

eth0   00:15:6D:1D:27:39
eth0.1 00:15:6D:1D:27:39
eth0.2 00:15:6D:1D:27:39
wlan0  00:15:6D:1C:27:39
wlan0-1 00-15-6D-1C-27-39-00-44-00-00-00-00-00-00-00-00

/proc/cpuinfo
system type		: Atheros AR7240 rev 2
machine			: Ubiquiti Bullet M
processor		: 0
cpu model		: MIPS 24Kc V7.4
BogoMIPS		: 259.27
wait instruction	: yes
microsecond timers	: yes
tlb_entries		: 16
extra interrupt vector	: yes
hardware watchpoint	: yes, count: 4, address/irw mask: [0x0000, 0x0ff8, 0x0ff8, 0x0ff8]
isa			: mips1 mips2 mips32r1 mips32r2
ASEs implemented	: mips16
shadow register sets	: 1
kscratch registers	: 0
core			: 0
VCED exceptions		: not available
VCEI exceptions		: not available


nvram
hsmmmesh.settings=settings
hsmmmesh.settings.wifimac=00:15:6d:1c:27:39
hsmmmesh.settings.mac2=28.39.57
hsmmmesh.settings.dtdmac=29.39.57
hsmmmesh.settings.node=W6ABJ-NB5-Q-1
hsmmmesh.settings.config=mesh

Part of the AREDN™ Project. For more details please see here

w6abj
Looking at the source code i
Looking at the source code i think i might have found the problem

1205            '0xe2b5' => {     SHOULD BE '0xe235'   <--------------------------------
1206                'name'            => 'NanoBridge M5',
1207                'comment'         => 'NanoBridge M5',
1208                'supported'       => '1',
1209                'maxpower'        => '22',
1210                'pwroffset'       => '1',
1211                'usechains'       => 1,
1212                'rfband'          => '5800ubntus',


1142            '0xe232' => {
1143                'name'            => 'NanoBridge M2',
1144                'comment'         => 'NanoBridge M2',
1145                'supported'       => '1',
1146                'maxpower'        => '21',
1147                'pwroffset'       => '2',
1148                'usechains'       => 1,
1149                'rfband'          => '2400',
1150             },
1151            '0xe239' => {
1152                'name'            => 'NanoBridge M9',
1153                'comment'         => 'NanoBridge M9',
1154                'supported'       => '1',
1155                'maxpower'        => '22',
1156                'pwroffset'       => '6',
1157                'usechains'       => 1,
1158                'rfband'          => '900',
KG6JEI
This line should not be

This line should not be 0xe235.
Ubiquiti makes periodic adjustments to its hardware line and changes the boardID.  As the page says the devices is unsupported (and is unknown) and needs to go through testing routines and verify the data of the hardware for proper operation. I'm guessing you had this device for a while or it was a 2nd hand purchase?  Being a 0xe235 I suspect its an older run then 0xe2b5 and as such we havne't seen it.

Before this can be started we need a copy of the board.info file. To obtain this install AirOS on the device and then:

1) Set your PC's ip to 192.168.1.2 / 255.255.255.0
2) Telnet/SSH/Putty into the Nanostation (default user is ubnt; password ubnt; default ip 192.168.1.20)
3) Run "cat /etc/board.info
4) Save the results and post it in response to this post.

PS: After you save and reboot one time you *SHOULD* get the extra ham only channels should show up as a frequency as the hardware is reanalyzed.
 

w6abj
XM.v5.5# cat /etc/board.info
XM.v5.5# cat /etc/board.info
board.sysid=0xe235
board.cpurevision=0x000000c2
board.name=NanoBridge M5
board.shortname=NB5
board.subtype=
board.netmodes=7;
board.hwaddr=00156D1EED1F
board.reboot=30
board.upgrade=150
board.phycount=1
board.phy.1.maxmtu=1524
board.phy.2.maxmtu=1524
radio.1.name=
radio.1.shortname=
radio.1.bus=pci
radio.1.subsystemid=0xe235
radio.1.subvendorid=0x0777
radio.1.txpower.max=23
radio.1.txpower.offset=1
radio.1.antennas=3
radio.1.def_antenna=4
radio.1.antenna.1.id=4
radio.1.antenna.1.name=Not specified
radio.1.antenna.1.gain=0
radio.1.antenna.2.id=1
radio.1.antenna.2.name=300
radio.1.antenna.2.gain=22
radio.1.antenna.3.id=2
radio.1.antenna.3.name=400
radio.1.antenna.3.gain=25
AE6XE
AE6XE's picture
Based on this board ID file,
Based on this board ID file, the 2 hardware versions are similar enough.   You could edit-replace "0xe2b5" to be "0xe235" on this device to obtain all the right setup options for channel, etc.  This edit is in file /www/cgi-bin/perfunc.pm per the prior post of the code snippet.  (Note, maxpower is absolute in board.info, and this is a relative from offset in AREDN definition :) .   )

This has missed the cutoff to be in 3.16.1.0 and the next window of opportunity is the next beta release (timing not yet determined).   Please report the results of any testing on 0xe235.
w6abj
So far so good, everything
So far so good, everything seams to be working as expected.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer