I have the same issue as this thread: https://www.arednmesh.org/content/untested-hardware-nanostation-m2-and-32030
I'm using two identical units. Both were flashed with aredn a few years back and were working as recently as last week. Decided to upgrade to latest version. First one went off without a problem. Used sysupgrade and upgraded to 3.22.1 (aredn-3.22.1.0-ath79-generic-ubnt_nanostation-m-squashfs-sysupgrade). It works fine.
When I did the second one, the RF did not come back on and I knew there was an issue. I finally found it at 192.168.1.1 with the "untested hardware" banner. Here is the support dump:
node:
model: Ubiquiti Nanostation M
!!!! UNSUPPORTED DEVICE !!!!
boardid: 0xffff
Device has not been tested. Please file a ticket with your experiences.
br-dtdlink 02:27:22:07:84:96
br-lan 02:27:22:07:84:96
br-wan 02:27:22:07:84:96
eth0 02:27:22:07:84:96
eth0.1 02:27:22:07:84:96
eth0.2 02:27:22:07:84:96
eth1 00:27:22:07:84:96
eth1.1 00:27:22:07:84:96
eth1.2 00:27:22:07:84:96
tunl0 00-00-00-00-00-00-00-44-00-00-00-00-00-00-00-00
/proc/cpuinfo
system type : Atheros AR7240 rev 2
machine : Ubiquiti Nanostation 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: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented : mips16
Options implemented : tlb 4kex 4k_cache prefetch mcheck ejtag llsc dc_aliases perf_cntr_intr_bit nan_legacy nan_2008 perf
shadow register sets : 1
kscratch registers : 0
package : 0
core : 0
VCED exceptions : not available
VCEI exceptions : not available
nvram
hsmmmesh.settings=settings
I eventually used TFTP to take it back to aredn-3.19.3.0-ubnt-nano-m-factory.bin and it recognized the board and worked as expected. However, if I tried to upgrade via sysupgrade it produced the same issue (board unrecognized).
One option, and this would be a test, is to reload AirOS to the device. Then from AirOS UI reload AirOS again. This 2nd step will update more things in the flash, including the boot loader. Then reload AREDN firmware. Something is not right with the flash data on this device, but we're in uncharted territory if, or how, this vender information in flash can be recovered. In the prior instance, we never really knew why it suddenly started working.
Joe AE6XE