They must have some sort of protection in there bootloader, immediately after OpenWRT is put onto the device via TFTP the error "Application terminated, rc=0xFFFFFFFF" shows up. I wonder what it's expecting?
Interestingly enough, there is a 2nd kernel partition ( kernel0 and kernel1 ) It boots into kernel1 if kernel0 fails. Receiving file from 192.168.1.25:53844 Received 3539292 bytes TFTP Transfer Complete. Bytes transferred = 3539292 (36015c hex) ## Starting application at 0x80200020 ... Firmware Version: BZ.qca956x.v6.0.0-OpenWrt-r47065 ## Application terminated, rc = 0xFFFFFFFF ## Starting application at 0x80200020 ... Number of boot partitions = 2 get_mtd_params: name=bs ubnt_flash_read: addr=8023b480, sa=9ff90000, sz=131072 ubnt_get_bootsel: Boot partition selected = 1 Loading Kernel Image @ 81000000, size = 7929856 Verifying 'kernel1' parition:OK ## Application terminated, rc = 0x0 ## Booting image at 9f800000 ... Image Name: MIPS OpenWrt Linux-3.3.8 Created: 2015-09-12 0:03:12 UTC Image Type: MIPS Linux Multi-File Image (lzma compressed) Data Size: 6877256 Bytes = 6.6 MB Load Address: 80060000 Entry Point: 80060000 Contents: Image 0: 6877248 Bytes = 6.6 MB Verifying Checksum at 0x9f800040 ...OK Uncompressing Multi-File Image ... OK No initrd ## Transferring control to Linux (at address 80060000) ... ## Giving linux memsize in bytes, 134217728 Starting kernel ... -- Davey On Tue, Oct 27, 2015 at 4:27 PM, David Hutchison <dhutchi...@bluemesh.net> wrote: > Thank you, > > That indeed helps, I was able to find the header in the UniFi > Controller ( There is a "dl" directory ). TFTP accepts > "BZ.qca956x.v6.0.0-OpenWrt-r47065" > I still haven't had luck getting it to boot yet; definitely getting closer. > > -- Davey > > On Tue, Oct 27, 2015 at 4:20 PM, Jonathan Bither <jonbit...@gmail.com> wrote: >> Hello Davey, >> >> I haven't gotten a chance to mess with one of these yet due to availability, >> but I placed a copy of the binary image for the AP on my web-server for you. >> This came from a 4.7.5 install. >> https://jonbither.com/unifi/firmware/U7PG2/3.4.7.3284/firmware.bin >> >> According to the bundles file both the UAP-AC-LITE and the UAP-AC-LR use the >> same image file. >> 'cat /usr/lib/unifi/dl/firmware/bundles.json | python -m json.tool' >> { >> "U7LR": { >> "display": "UniFi AP-AC-LR", >> "path": "U7PG2/3.4.7.3284/firmware.bin", >> "version": "3.4.7.3284" >> }, >> "U7LT": { >> "display": "UniFi AP-AC-Lite", >> "path": "U7PG2/3.4.7.3284/firmware.bin", >> "version": "3.4.7.3284" >> }, >> } >> >> Hopefully the header will be similar. >> `strings /usr/lib/unifi/dl/firmware/U7PG2/3.4.7.3284/firmware.bin | head >> -n1` >> UBNTBZ.qca956x.v3.4.7.3284.150911.1650 >> >> >> Hope any of this helps. >> -Jonathan >> >> >> >> On 10/26/2015 06:16 PM, David Hutchison wrote: >>> >>> I just got this board and I am looking to port OpenWRT to it. I have >>> taken this board apart and can receive serial, however TX doesn't >>> appear to work ( Maybe there is a GPIO, I need to toggle? ). These two >>> new UniFi-AC boards have the new QCA953x processor in them ( LITE and >>> LR ). This is not the Broadcom 48V UniFi that is already supported; >>> these just came out. >>> >>> I was hoping to reach out to the group who have experience building >>> the image with the proper "MAGIC HEADER". TFTP will not accept the >>> image and think the image is invalid unless the proper header exists. >>> With other board ports I have grabbed the original AirOS firmware, and >>> you could see the header at the top of the .bin. However with UniFi >>> they don't seem to have the image easily downloadable. >>> >>> I am hoping if anyone would have any insight to finding this? Once I >>> can TFTP an image onto it; I can try making an architecture patch for >>> it. >>> >>> Thanks, >>> -- Davey >>> _______________________________________________ >>> openwrt-devel mailing list >>> openwrt-devel@lists.openwrt.org >>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >>> >> _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
