Is 3.22.12.0 the final release for ar71xx devices ( https://downloads.arednmesh.org/releases/3/22/3.22.12.0/targets/ )? I have a number of Ubiquiti RM5-GPS units that run great on 3.22.12.0, but do not have the ability to be upgraded to the ath79 releases. I tried many different sysupgrades and factory firmware images of the ath79 releases but no joy. It's not imperative that they be upgraded, I just finally got a chance to do it.
And the Mikrotik ac2 and ac3 use another driver type - ipq40xx
And it's not clear to me if your RM5-GPS is still supported. I've asked.
Orv W6BI
Exactly which sysupgrade.bin(s) did you try.
Please further define 'no joy'.
73, Chuck
All gave a similar result as recorded in this series of screenshots:
https://drive.google.com/file/d/1vKXeE4MtMg0v7-TlcaD6a-RN9Onzdas8/view?usp=drive_link
Attached is the support data file for this particular flashing attempt session.
The "no joy" part is that the units never go through the second boot enabling the mesh networking, so they are forever stuck having a 192.168.1.x address. Forced reboots do nothing to get past this issue.
aredn-20240618-8d4eade-ath79-generic-ubnt_rocket-m-squashfs-sysupgrade.bin
Since your screen captures don't show the errors you get, what errors are you seeing?
It successfully was able to complete the second reboot, so it seems subsequent factory.bin versions either are not picking up the signal to reboot a second time to wake up as an AREDN node, or the final ar71xx does something strange on these RM5-GPS units to keep something in memory to block any new factory.bin from taking hold. Now on to replicate the steps that were successful for me: