that's great news. I had started thinking whether I have to buy one just to get rid of questions for it. Sounds like you solved that for me
Regarding the LED: I would expect that they used a similar aproch like for the ISP. A small extra controller that is controlled via SPI. I wrote a driver for this controller some time back. It has been merged to upstream Linux. Only problem left: When using the driver a bit more I noted that the SPI speed is too high and I haven't been able to reduce it. That would need another patch to Linux but creating that patch isn't simple without having a big performance impact on a lot of other systems.
A new target profile is available: airCube AC, select it and also select firmware -> ath10k-firmware-qca988x-ct-htt.
Almost everything work as expected but not flashing LED. There is also a strange bug with switch port counters not reported (only ???). I've tested changing registers values without luck. If someone find this one, I would be grateful.
Finally, I never made a contribution to OpenWRT, if someone can guide me to create a contribution, that would be great.
hi,
since there is no activity for the last 16 days and i am interested in getting it merged upstream (openwrt), would it be acceptable to pick where it is left to get device support merged?
it currently has LED blinking at all times due to obvious reasons stated above but the same applies to AirCube ISP (acb-isp)
i tested building for aircube-ac on trunk and last stable release and it seem to be working fine.
upgrade to 2.5.0 (or downgrade via tftp) and people could flash device from stock firmware following same procedure as for AirCube ISP (acb-isp).
maybe we could share common configuration for both of them and even wiki page?
No problem with that. Feel free to adapt anything that is necessary and makes sense. You can ask me anything about the AirCube ISP and I can also support that activity. But you have to talk mainly to @davidb2111 regarding the AirCube AC patches. I don't have an AirCube AC here so I can't really test anything related to that.
hello, thanks everyone for the great work done with these devices i was wondering if anyone can upload the file openwrt-ath79-generic-ubnt_acb-isp-squashfs-factory.bin, it is no longer found at https://openwrt.org/toh/ubiquiti/ubiquiti_aircube_isp, thanks in advance
@Prim Here it is, factory image for the aircube isp Including luci for easy config. Make sure to follow the guide. As downgrading firmware isn't possible through the web interface, you need to:
download firmware 2.5.0 from ubiquiti
connect with lan cable to your router (not on the blue wan port, it wont work for openwrt afterwards)
unplug it and press a paper clip down the reset hole on the bottom
plug power back in and hold the clip in place for a while
let go of the reset pin, send the ubiquiti firmware through tftp (set your ip to 192.168.1.2, gateway to 192.168.1.1 and subnet to 255.255.255.0, use a tftp program and connect to 192.168.1.1, set transfer to binary and send the file, just like in the guide)
let it turn back on again, upload the modified config file
upload the factory image as a new firmware.
[sorry my hosting is broken will reupload very soon]
(8. log in through ssh at root@192.168.1.1 and sysupgrade to the openwrt-supplied upgrade system if you want, but mine should be fine)
For everyone else: I have it running on my aircube ac, works great. Compiled from the @davidb2111 github and followed his instructions on adding the wifi firmware, as well as luci.
Thanks for your work with the aircube, that is what I was looking for
But I have problems with installing OpenWRT on my Aircube-ISP
I did the downgrade to V2.8.3 as described on the UI Website
The file I found there is ACB.ar934x.v2.8.3.f1a1344.210726.1457.bin
The downgrade works I can log in etc etc.
I uploaded the configuration file aircube_isp_remove_signaturecheck_config_firmware_2.8.3.tgz
but if after uploading the open wrt image - openwrt-22.03.0-ath79-generic-ubnt_aircube-isp-squashfs-sysupgrade.bin - using the WebUi
i got the error verification failed
What can I try now?
Hm. The lua script is all as expected. The fwupdate.real has the correct md5 sum. And I'm quite sure that I have seen a downgrade from 2.8.5 somewhere already in the past.
Background to what Borromini said: The images have a different structure. For some routers it can be a completely different file format. In this case it's only a relatively small difference in the headers because the Ubiquity Firmware is based on an old OpenWRT version. But it's still different enough that you can't use the sysupgrade directly.