Mediatek/filogic: add support for Cudy M3000 v2

For Developers
1

Description

The Cudy M3000 v2 is a newer hardware revision that is currently unable to flash either stock Cudy or OpenWrt images due to a board-ID mismatch in U-Boot checks. All attempts (stock web-UI, sysupgrade, or OpenWrt factory images) end with “Not applicable” or “installation failed” errors, indicating that no V2 board definition exists in the OpenWrt tree

Hardware Details

  • Model: Cudy M3000 v2
  • SoC: MediaTek MT7981BA (A53-based)
  • RAM/Flash: 256 MB RAM, 256 MB SPI NAND
  • Ethernet: 1×2.5 Gbit WAN + 3×1 Gbit LAN
  • Wi-Fi: 2×2 802.11ax (2.4 + 5 GHz)

Current Support Status

  • OpenWrt support only exists for M3000 v1
  • Attempts to flash V2 via the stock web UI fail
  • OpenWrt factory images likewise refuse to install

Please let me know any further hardware IDs or logs needed to complete the V2 board support PR.
Thank you!

2

You will likely need to do most of the work yourself since you have a unit in hand. You can follow this guide, and feel free to ask questions if/when you get stuck.

1 Like
3

Have you tried the initramfs for the M3000 v1 over tftpboot?

4

Ugh I thought Cudy was someone who would just have one revision. I hope this is the only change.

5

Apologies, but I don’t feel confident enough to do this on my own

6

Sorry, I am not sure what that is or how to do it

7

From what I can see on the specification difference, the main thing is the V1 has 128 nand and the V2 has 256 nand.

Therefore if you can connect UART following the V1 instructions you should be able to boot the V1 initramfs kernel bin file via tftpboot and confirm if everything works apart from the storage space.

Click the supported since link for details

1 Like
8

I also picked these M3000 V2 due to the color (I prefer white with no red on top) but apparently they don't even have a Cuddy OpenWRT firmware available. Wasn't expecting that. AX3000 all have the same CPU (WR3000, M3000, and so on) so I was not expecting this outcome. Let's wait a bit until/if Cudy releases this firmware and OpenWRT as well.

9

Sorry I don't think you understand, someone with the hardware needs to test and add the device.

Openwrt is developed by volunteers, so if you're not willing to add the device, it's not going to be added until someone with the hardware decides to get it done.

10

I understand and am aware of that. The thing is just because I have the hardware does not necessarily mean I have the time and knowledge to do what is needed to Add this new device. I think I can help with some tasks but doubt it I will be able to develop it myself.
I believe the first step would come from Cudy: if they can create the first OpenWRT firmware that allows the vanilla version of OpenWRT it would simplify the firmware change. I already sent a comment on Cudy website regarding that.