You are here

"Untested Hardware" Nanostation M2 and 3.20.3.0

11 posts / 0 new
Last post
ng1p
ng1p's picture
"Untested Hardware" Nanostation M2 and 3.20.3.0

I got a Nanostation M2 on eBay and tried to load 3.20.2.0 and got the ​"Untested Hardware" banner. I then loaded 3.19.3.0 and it worked fine.

I have attached the support data file for this Nanostation M2 (XM) version. I'd like to get this device on the latest firmware if possible.

Thank you Bill NG1P

 

Support File Attachment: 
N3XKD
Willing to bet that it's

Willing to bet that it's because that's the XM version "​AREDN Stable, but, NOT recommended for new deployments.  (Low memory or non-MIMO device)" but I'm no expert, maybe one of the main guys will chime in.

nc8q
nc8q's picture
tried to load 3.20.2.0 and got the ​"Untested Hardware"

Hi, Bill:

Did you try the TFTP method?

https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#ubiquiti-first-install-process

Now that you have 3.19.3.0 loaded, can you upgrade using 3.20.3.0 sysupgrade?

Chuck

ng1p
ng1p's picture
No luck

Yes I first tried the tftp method using 3.20.3.0 and got the "untested hardware" I then did the tftp method and went to 3.19.3.0 and that worked fine. I just tried upgrading from 3.19.3.0 to 3.20.3.0 using the sysupgrade and no luck. The LAN LED will not light and its not giving out a IP address so its worst. 

AE6XE
AE6XE's picture
the support dump is from 3.19

the support dump is from 3.19.3.0.  If you reload 3.20.3.0, back and receive "Untested hardware" again, capture the support data.

Joe AE6XE 

ng1p
ng1p's picture
3.20.3.0 Support file


Also what is interesting is after the update the main port and secondary port will not provide a DHCP address. Setting my PC to a 192,168,1,x address I can then get into the Nanostaition on 192.168.1.1 but only using the secondary port the main port doesnt work at all. Also the LAN LED's dont light up.

Attached is the support file for 3.20.3.0

Thank you!

Support File Attachments: 
AE6XE
AE6XE's picture
NG1P,  

NG1P,  

Can you confirm which image you have loaded?

A) ​http://downloads.arednmesh.org/releases/3/20/3.20.3.0/targets/ath79/gene...
B) ​http://downloads.arednmesh.org/releases/3/20/3.20.3.0/targets/ar71xx/gen...

For some reason, the ubqiuiti board ID information is not found, hence untested message.  I'd expect this to occur regardless of which image is uloaded.  can you access with command line and send back the output of these 2 commands?:

1) ​cat /sys/devices/pci0000:00/0000:00:00.0/subsystem_device
2) ​dd if=/dev/mtd7 bs=1 skip=12 count=2 2>/dev/null | hexdump -v -n 4 -e '1/1 "%02x"'

On Ubiquiti, option 1 is tried first, if that doesn't exist, then option 2 is supposed to work.    It's finding 0xFFFF on your device, just want to make sure which command is returning this value.

for the network ports, the LAN is bridged across these 2 ports.   Something odd:

[ 1.567771] ag71xx 1a000000.eth: connected to PHY at fixed-0:00 [uid=00000000, driver=Generic PHY] <- uid shouldn't be 0s 
[   27.954049] eth0: link up (1000Mbps/Full duplex)    <-  hmmm,  I don't believe the main port is a gigabit port...

If you have loaded the ath79 image, try the ar71xx image to see if this issue resolves?  I suspect there may be some minor variations in the NS M2 hardware and the new ath79 images only work on one flavor.

Joe AE6XE
 

ng1p
ng1p's picture
No luck yet

Here is the results:
I was trying the ath79 image, I tried the ar71 image but got received ERROR <code=2, msg=Firmware check failed>
Error code 2: Firmware check failed. So the ar71 image would not even load.

This is the results from the command line: on ath79 image:
root@NOCALL:~# cat /sys/devices/pci0000:00/0000:00:00.0/subsystem_device
0x0000

root@NOCALL:~# dd if=/dev/mtd7 bs=1 skip=12 count=2 2>/dev/null | hexdump -v -n 4 -e '1/1
"%02x"'
ffffroot@NOCALL:~#

Just for fun I did the same commands from the working 3.19.3.0 image:
root@NOCALL:~# cat /sys/devices/pci0000:00/0000:00:00.0/subsystem_device
0xe012

root@NOCALL:~# dd if=/dev/mtd7 bs=1 skip=12 count=2 2>/dev/null | hexdump -v -n 4 -e '1/1
"%02x"'
ffffroot@NOCALL:~#

 

AE6XE
AE6XE's picture
just in case, if you tried to

just in case, if you tried to use the ar71xx image, be sure to use the "sysupgrade" version to switch back and forth between aredn versions.   The earlier links are the 'factory' flavor to use when tftp or from AirOS firmware.   there is a way to load the ar71xx image for Nanostations XMs.

Joe AE6XE

ng1p
ng1p's picture
Upgrade

I was using the factory images and doing them both from the tftp method. l was not able to upgrade using the 3.20.3.0 as I could never save the config becouse it could not determine the hardware or know what band it was for. Should I try 3.19.3.0 again and upgrade using the ar71xx 3.20,3.0 sysupgrade image? 

ng1p
ng1p's picture
Success

I installed 3.19.3.0 again and then did the upgrade using aredn-3.20.3.0-ar71xx-ubnt-nano-m-sysupgrade.bin. And that worked. using the factory version of this image and tftp will not load at all. Loading the old 3.19.3.0 first then upgrading using aredn-3.20.3.0-ar71xx-ubnt-nano-m-sysupgrade.bin working fine...

Interesting??? Must be a bug in the factory bin? I added the support file just incase that might help.

Thank you
Bill NG1P

 

Support File Attachments: 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer