Cudy AP3000 Indoor AKA Jupiter 2 and OpenWRT: Difference between revisions
| Line 1: | Line 1: | ||
=Installing OpenWRT on a Cudy AP3000 (Indoor, AKA the Jupiter 2)= | =Installing OpenWRT on a Cudy AP3000 (Indoor, AKA the Jupiter 2)= | ||
==Overview== | ===Overview=== | ||
How about following the instructions on the OpenWRT.org website for a similar device (with the EXACT same CPU, WiFi, etc.): https://openwrt.org/toh/cudy/tr3000 | How about following the instructions on the OpenWRT.org website for a similar device (with the EXACT same CPU, WiFi, etc.): https://openwrt.org/toh/cudy/tr3000 | ||
Nope. Sadly Cudy doesn't make an InitRAMFS BIN file for the AP3000 (Indoor), even though the file for the AP3000 would work it weren't for their gosh darned 'security feature' of having a signed file. Side note: Is there really an instance where this has helped an end user, or is it about manufacturer control? | Nope. Sadly Cudy doesn't make an InitRAMFS BIN file for the AP3000 (Indoor), even though the file for the AP3000 would work it weren't for their gosh darned 'security feature' of having a signed file. Side note: Is there really an instance where this has helped an end user, or is it about manufacturer control? | ||
=== Installing OpenWRT (Try Ethernet / Network Method First) === | |||
A TTY / Serial session via Ethernet? Sure, give it a shot. It has been noticed that there are different version of the Cudy AP3000 Outdoor 'in the wild'. Some will automatically search for a 'recovery.bin' file (where it looks for a TFTP Server at 192.168.1.88, with the Cudy's IP being 192.168.1.112). | |||
* Command to manually upload InitRAMFS: tftpboot 0x42000000 recover.bin (could be named anything, recovery.bin is what it automatically search for) | |||
Final Note on this subject: It seems to work better when connected directly to a computer rather than a switch, so maybe try that too. | |||
=== What if Ethernet Doesn't Work? === | |||
If you get something like: ethernet@15100000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! It appears that the u-boot image might be busted in some versions of the device so that the Ethernet Interface does NOT work. It shows as 'active', but no link light on a switch and it just doesn't work. Blame this guy: U-Boot 2022.07-rc3 (Sep 01 2023 - 07:34:59 +0000), Build: jenkins-AP3000-19 (well, either he did it, didn't know what he did, or was told to do it by his corporate overlords, in any instance, is doesn't help the end owner of the device that wants OpenWRT installed) | |||
But there is a solution: TTY / Serial Communication via a Serial Port and a good 'ole fashion TTL UART Serial Console Port. | But there is a solution: TTY / Serial Communication via a Serial Port and a good 'ole fashion TTL UART Serial Console Port. | ||