Hello,
please can you add support for Cudy AP3000 (indoor):
Model Version: AP3000 1.0
CPU Chipset: MT7981BA
CPU Details: 1.3 GHz Dual-Core CPU
Memory/Storage: Flash/ROM 256 MB (2 Gbit) NAND
DDR/RAM: 512 MB (4 Gbit) DDR4
It has 2.5GB ethernet port like TR3000 (https://github.com/openwrt/openwrt/pull/15214)
There is work in this area, openwrt work but cudy dev team didn't released transit image, they didn't make even recovery possible for it ( no ethernet communication in uboot). Only way is to send i itramfs by kermit serial and then flash with sysupgrade. Until cudy dev team do theyr's job there is no support.
Glad I am not the only one.
I guess Cudy team will provide intermediate firmware as soon as there is some workin OpenWRT image available. Is there any PR opened?
BTW in TR3000 PR there is something about not working ethernet in the recovery (https://github.com/openwrt/openwrt/pull/15214#issuecomment-2067691783). Can it be the answer to your issue?
Nope, gready chinese folks cheaped few dollars for rj45 port, transformer and few resistors to put built in eth gig interface which is supported in bootloader for recovery etc... I hate them for this...
I see. Then can we create a PR in OpenWRT to get Cudy AP3000 officially supported? If you already have working firmware it could be a quick process. Then I can ask Cudy team for the intermediate firmware.
https://forum.openwrt.org/u/chkdsk88 You can ask this guy, he added the ap3000 outdoor and also was working by indoor and sent them email for intermediate firmware.
Will do so.
So you are using AP3000-outdoor OpenWRT inside indoor unit? All works well? How about partition size which is different than in outdoor?
Nope, i was planning to hang one outdoor but after all resign with this plan, i have indoor but i'm waiting for official support, i had zyxel nwa50ax pro but it went rma, it was working very nice. I'm playing with two bpi r4 and one dead bpi r4.
Hi guys,
I prepared preliminary support for AP3000 V1 some time ago:
BUT:
I don't have the device and I can't test it. Does anyone could test if everything is ok?
Thank you!!!
I am not able to do tests with serial access because I am not able to disasemble the device to use serial console.
So M10, please can you test using serial?
I will ask Cudy to provide the intermediate firmware.
Did they gave someone intermediate firmware? Mine is hanging on ceiling now, so far works good on cudy fw.
August 26, 2024 Cudy's support stated:
For now, We don’t have recovery method of AP3000. The AP can not be recovered if there is a problem with the firmware. So we can’t offer you the intermediate firmware. We will add the recovery method in next firmware update and then we can offer the intermediate firmware. Please wait patiently.
Septemper 20, 2024
New firmware 2.2.7 released - AP3000-R49-2.2.7-20240911-151101-sysupgrade.zip
So I believe Cudy will provide intermediate firmware soon.
Cudy's support page:
I was able to compile an initramfs and sysupgrade from your commit with minimal changes @CHKDSK88, but I haven't been able to boot it yet.
U-boot doesn't negotiate the ethernet link, and loadx also times out after a while. So I'm out of options for copying initramfs image to the device. The new vendor firmware from last week doesn't seem to update U-boot, it's still a build from Sep 01 2023. But at least I have a writable console.
Can you think of other options?
I managed to boot and flash it, using screen, loadx and exec !! sx initramfs.bin, then sysupgrade.
So far it looks good, but it is fixed to 2.5 Gbps and doesn't negotiate down to 1 Gbps. But this is a very good basis to work on!
(For anyone else who wants to try, remove the stray underscore in led_status_ in the DTS from @CHKDSK88's commit, or the OpenWrt build will fail.)
The 2.5 Gbps thing seems to be similar to this problem with the same RTL8221B PHY: MTK830 + RTL8221B-VB-CG 2.5G question - it can work as a 1 Gbps PHY if set to SGMII.
It's probably the same problem here: https://github.com/openwrt/openwrt/issues/14504
The good news is: The issue was just fixed a day ago (you can scroll to the bottom and see it)
Ah man that's perfect. @CHKDSK88 do you mind if I test this further, make the LED colors work, and go ahead with pull request?
Cudy made broken Ethernet support in u-boot. You found the only known method with serial transfer.
I will fix it.
Rebase to current master will be enough to fix phy issues?
Please tell me what exactly is wrong. I don't have the hardware.
My plan is simple:
EDIT:
Please try:
No luck with that Realtek patch unfortunately 
I applied your device commit on top of today's main branch.
Regarding the LEDs, it has three, but only red seems to be used.
Reset button during runtime works (results in firstboot+reboot), but reset button during boot (failsafe) doesn't seem to react. It seems like it continues to boot (2.5-per-second blink), and then it seems to reboot. (?) I can check that out with serial, just dont have the USB adapter with me today.
Here's logread from today, the vendor logread, and bootloader log: https://gist.github.com/pktpls/a51c61194f8036d173b04a699e1f3ced
I didn't have the presence of mind to also grab the vendor DTS, would that be useful? I have a second device that i can open up.