openwrt-6.x/target/linux/mediatek
Roland Reinl 300335f1ff mediatek: filogic: add support for Cudy WR3000E v1
The WR3000E has the same board layout as the WR3000S. Differences:
- Different flash chip
- LEDs with red/blue colour intead of white

Hardware:
- MediaTek MT7981 WiSoC
- 256MB DDR3 RAM
- 128MB SPI-NAND (F50L1G41LB)
- MediaTek MT7981 2x2 DBDC 802.11ax 2T2R (2.4 / 5)

MAC Addresses in OEM firmware:
- There is one on the label, e.g. AA:BB:CC:DD:EE:FF
- WLAN (2.4G) uses the same as on the label
- WLAN (5G) is the one on the label but
  - first byte (e.g. AA) + 2
  - fourth byte (e.g. DD) - 0x40
- WAN is the one on the label + 1
- LAN is the one on the label

MAC Addresses in OpenWrt:
- Same handling as in WR3000s is used

GPIO:
- 2 Buttons (all low active):
  - WPS on GPIO 0
  - Reset on GPIO 1
- 6 LEDs (all low active):
  - Power: Blue on GPIO 8, no red LED
  - WPS: Blue on GPIO 10, Red on GPIO 4
  - Internet: Blue on GPIO 11, no red LED
  - LAN: Blue on GPIO 9, Red on GPIO 5
  - WiFi 2.4G: Blue on GPIO 6, no red LED
  - WiFi 5G: Blue on GPIO 7, no red LED

Disassembly:
- Remove the 4 screws at the bottom of the case
- Cover is clipped to the bottom part of the case with clips in the front and the back

UART:
- UART pins are accessible on the bottom of the board
- The connector with the square shape is TX
- Pins: [ ] TX, ( ) RX, ( ) GND, ( ) VCC
- Settings: 115200 8N1 3.3V

Migration to OpenWrt via OEM firmware:
- There should be a migration image available from Cudy as soon as there is official OpenWrt support
- Download the migration image via OEM web interface
- After flashing, OpenWrt is accessible via 192.168.1.1
- Flash the official OpenWrt image

Migration to OpenWrt using TFTP:
- Connect UART as described above
- Press the reset button while powering on the device
- U-Boot will now try to load a recovery.bin via TFTP, this must be ignored
- After detecting a timeout, the U-Boot console is available via UART
- Set up a TFTP server on IP 192.168.1.88 and connect it to one of the LAN ports
- Provide the initramfs image via TFTP as cudy3000e.bin
- Run the following command in U-Boot: tftpboot 0x46000000 cudy3000e.bin; bootm 0x46000000
- OpenWrt initramfs image is now booting and accessible via 192.168.1.1
- Flash the sysupgrade image

Revert back to OEM:
- Set up a TFTP server on IP 192.168.1.88 and connect it to one of the LAN ports
- Provide the Cudy firmware via TFTP as recovery.bin
- Press the reset button while powering on the device
- Recovery process will start now
- After recovery is done, the OEM firmware is available at 192.168.10.1 again

Signed-off-by: Roland Reinl <reinlroland+github@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/18609
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2025-06-07 18:07:03 +02:00
..
base-files mediatek: add ubootmod layout for cudy tr3000 v1 2025-05-27 19:56:55 +08:00
dts mediatek: filogic: add support for Cudy WR3000E v1 2025-06-07 18:07:03 +02:00
files/drivers mediatek: mt7622: prepare legacy rtl8367c driver for Linux 6.12 2025-05-26 16:58:03 +01:00
files-6.6 kernel/mediatek: Restore kernel files for v6.6 2025-05-26 16:58:04 +01:00
files-6.12 kernel/mediatek: 6.12: replace downstream files by patches 2025-05-26 16:58:04 +01:00
filogic mediatek: filogic: add support for Cudy WR3000E v1 2025-06-07 18:07:03 +02:00
image mediatek: filogic: add support for Cudy WR3000E v1 2025-06-07 18:07:03 +02:00
mt7622 mediatek: mt7622: update config-6.12 2025-05-26 16:58:04 +01:00
mt7623 mediatek: mt7623: update config-6.12 2025-05-26 16:58:04 +01:00
mt7629 mediatek: mt7629: add the missing symbol CONFIG_LEDS_SMARTRG_LED 2025-05-29 23:05:02 +02:00
patches-6.6 kernel/mediatek: Restore kernel files for v6.6 2025-05-26 16:58:04 +01:00
patches-6.12 kernel: bump 6.12 to 6.12.31 2025-05-31 17:35:29 +02:00
Makefile mediatek: enable testing kernel 6.12 2025-05-26 16:58:04 +01:00
modules.mk kernel: kmod-btmtk: Extract btmtk.ko into own package 2025-02-26 23:31:36 +01:00