Cudy AP3000 Indoor AKA Jupiter 2 and OpenWRT: Difference between revisions

(2 intermediate revisions by the same user not shown)

Line 1:

=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

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?

~~Anyway, that's out, so what about a~~ TTY / Serial session via Ethernet? ~~Not~~ a ~~chance~~. ~~Why~~? ~~Well~~: ethernet@15100000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! It appears that the u-boot image is busted in 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)

===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' (not the Indoor, naturally, since it is the same MediaTek SoC, but a minor Ethernet difference). 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.

Line 83:

Line 91:

</syntaxhighlight>

[[File:Putty Command Prompt for Cudy AP3000 upgrade.png|alt=Putty Command Prompt for Cudy AP3000 upgrade|left|thumb|Putty Command Prompt for Cudy AP3000 upgrade]]

And it will wait, slowly printing out CCCC

And it will wait, slowly printing out CCCC<br />

<br />

===On Host PC (on Linux)===

Sorry guys, there is no equivalent command in Windows, unless you're running a Linux sub-system.

Line 93:

Line 100:

</syntaxhighlight>...but first download the "InitRAMFS" File from OpenWRT: https://downloads.openwrt.org/releases/24.10.0/targets/mediatek/filogic/ (look for Cudy AP3000, without the 'outdoor' reference, but notice it is the same size file, so probably the same file with a different name)

[[File:Command Prompt Showing Transfer of File for Cudy AP 3000.png|alt=Command Prompt Showing Transfer of File for Cudy AP 3000|thumb|Command Prompt Showing Transfer of File for Cudy AP 3000]]

Now wait. And wait, and wait. Yes, the file is under 9 MB, but look up a couple of sentences and notice the speed things are transferring at. The SX Command will show "Progress". There will be no indication on the Serial / TTL session that anything is happening at all (but if your Serial USB device has LEDs, then they'll be blinking really fast or almost on solid showing a high transfer rate).

Now wait. And wait, and wait. Yes, the file is under 9 MB, but look up a couple of sentences and notice the speed things are transferring at. Oh, and remember the 'count-up' is in KB, not Bytes, so it's not going that slow. The SX Command will show "Progress". There will be no indication on the Serial / TTL session that anything is happening at all (but if your Serial USB device has LEDs, then they'll be blinking really fast or almost on solid showing a high transfer rate).

===Image Inspection in U-Boot===

@@ Line 1: / Line 1: @@
 =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
 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?
-Anyway, that's out, so what about a TTY / Serial session via Ethernet?  Not a chance.  Why?  Well: ethernet@15100000 Waiting for PHY auto negotiation to complete......... TIMEOUT !  It appears that the u-boot image is busted in 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)
+===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' (not the Indoor, naturally, since it is the same MediaTek SoC, but a minor Ethernet difference).  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.
@@ Line 83: / Line 91: @@
 </syntaxhighlight>
 [[File:Putty Command Prompt for Cudy AP3000 upgrade.png|alt=Putty Command Prompt for Cudy AP3000 upgrade|left|thumb|Putty Command Prompt for Cudy AP3000 upgrade]]
-And it will wait, slowly printing out CCCC
+And it will wait, slowly printing out CCCC<br />
-<br />
 ===On Host PC (on Linux)===
 Sorry guys, there is no equivalent command in Windows, unless you're running a Linux sub-system.
@@ Line 93: / Line 100: @@
 </syntaxhighlight>...but first download the "InitRAMFS" File from OpenWRT: https://downloads.openwrt.org/releases/24.10.0/targets/mediatek/filogic/ (look for Cudy AP3000, without the 'outdoor' reference, but notice it is the same size file, so probably the same file with a different name)
 [[File:Command Prompt Showing Transfer of File for Cudy AP 3000.png|alt=Command Prompt Showing Transfer of File for Cudy AP 3000|thumb|Command Prompt Showing Transfer of File for Cudy AP 3000]]
-Now wait.  And wait, and wait.  Yes, the file is under 9 MB, but look up a couple of sentences and notice the speed things are transferring at.  The SX Command will show "Progress".  There will be no indication on the Serial / TTL session that anything is happening at all (but if your Serial USB device has LEDs, then they'll be blinking really fast or almost on solid showing a high transfer rate).
+Now wait.  And wait, and wait.  Yes, the file is under 9 MB, but look up a couple of sentences and notice the speed things are transferring at.  Oh, and remember the 'count-up' is in KB, not Bytes, so it's not going that slow.  The SX Command will show "Progress".  There will be no indication on the Serial / TTL session that anything is happening at all (but if your Serial USB device has LEDs, then they'll be blinking really fast or almost on solid showing a high transfer rate).
 ===Image Inspection in U-Boot===