GatoNetworks GDSP

abgn+ac+ax (AX1800)
wireless router
3rd Party Firmware
dd-wrt	Status Unknown
OpenWrt	Supported
Tomato any flavor	Incompatible
Gargoyle	Status Unknown
Platform
Brand • Model • Rev	GatoNetworks GDSP
FCC ID	none specified
Type	wireless router
CPU1 Y	MediaTek MT7981BA
CPU1 Type	ARM Cortex-A53
CPU1 Speed	1.3 GHz ( 2 cores ) 64-bit
Flash1 Chip	Winbond W25Q256
Flash1 Size	32 MiB 33,554,432 B <br />262,144 Kib <br />32,768 KiB <br />256 Mib <br />0.0313 GiB <br /> (SPI NOR)
RAM1 Size	256 MiB 268,435,456 B <br />2,097,152 Kib <br />262,144 KiB <br />2,048 Mib <br />0.25 GiB <br />
RAM1 Chip	Brand? Model?
ETH chip1	MediaTek MT7981BA
Switch	MediaTek MT7531AE
Ethernet Port Count	1-1GbE-WAN 4-1GbE-LAN
Wired Standard	IEEE 802.3i/3u/3ab
802dot11 OUI: none specified
Stock bootloader	U-Boot
Expansion IF types	none specified
Power	48 VDC, ? A
Serial Port (UART)	yes, 3.3V TTL, (115200 8N1)
Other
3rd Party Firmware Support	OpenWrt • (List | Dev | DLs)
Radio 1
Chip1	MediaTek MT7981BA
Chip2	MediaTek MT7976CN
Wireless interface OUI	none specified
Antenna Connector Type	none specified
MIMO status	2x2:2
Wireless Standard	IEEE 802.11b/g/n/ax
802.11ax	up to 574 Mbps
802.11n	up to 300 Mbps
802.11g	up to 54 Mbps
802.11b	up to 11 Mbps
WiFi Operating Frequency	2.4 GHz
Radio 2
Chip1	MediaTek MT7981BA
Chip2	MediaTek MT7976CN
Wireless interface OUI	none specified
Antenna Connector Type	none specified
MIMO status	3x3:2
Wireless Standard	IEEE 802.11a/n/ac/ax
802.11ax	up to 1201 Mbps
802.11ac	up to 867 Mbps
802.11n	up to 300 Mbps
802.11a	up to 54 Mbps
WiFi Operating Frequency	5 GHz

For a list of all currently documented MediaTek chipsets with specifications, see MediaTek.

• 574 Mbps - 2SS 2.4GHz 802.11ax (40MHz chan., 256-QAM),

• 1201 Mbps - 2SS 5GHz 802.11ax (80MHz chan., 1024-QAM) = AX1800 class

Flashing

Flashing OpenWrt

On the OpenWrt ToH (techdata entry)

Target: mediatek
Subtarget: filogic
Package architecture: aarch64_cortex-a53
Supported Since Commit
Support started version: 24.10.0
Current supported version: 24.10.4

LAN Hardware: MediaTek MT7531AE
WLAN Hardware: MediaTek MT7981BA, MediaTek MT7976CN
Installation method(s):
see devicepage
Recovery method(s):
see devicepage

git • >>

mediatek: filogic: add support for GatoNetworks GDSP The GatoNetworks GDSP is a re-branded version of the R5000 5G Industrial router from Yinghua Technologies. The re-branded device comes with OpenWrt preinstalled, and an OpenWrt-based U-Boot bootloader version. While the flash layout has been kept compatible with the OpenWrt version found on the stock device (see [5]), the image format changed, making a bootloader upgrade necessary. Specifications: SoC: Mediatek MT7981BA RAM: 256MB Flash: SPI-NOR 32 MiB (Winbond W25Q256) WLAN: MT7976CN DBDC AX Wi-Fi Switch: MT7531AE (4x LAN Gigabit ports, 1x WAN Gigabit port) 5G: Quectel RM520N modem Watchdog: an external WDT connected to GPIO 6 is present and always running; the built-in Mediatek watchdog is also present and effective, but not used at the moment. This porting has been tested only with 1x 5G modems installed (the device supports up to two). Installation: Installation is possible via sysupgrade both in the stock device and re-branded version. However, in the former case, updating the bootloader is required. OpenWrt-based U-Boot Bootloader installation -------------------------------------------- The firmware flashed in the re-branded device at manifacturing time will flash an OpenWrt-based U-Boot bootloader with some extra recovery features (see [1]) at first boot. To update the bootloader, you need to install the mtd-rw module and insmod it: insmod mtd-rw i_want_a_brick=1 Then update relevant flash partitions: mtd erase u-boot-env mtd erase BL2 mtd erase FIP mtd write openwrt-mediatek-filogic-gatonetworks_gdsp-preloader.bin BL2 mtd write openwrt-mediatek-filogic-gatonetworks_gdsp-bl31-uboot.fip FIP And reboot, making sure all previous commands ran succesfully. If something goes wrong, you can recover your device via the mtk_uartboot tool. In my testing, it was possible to start the process even without (un)-plugging the device, may be handy for remote recovery. Installation from stock device and firmware ------------------------------------------- To install vanilla OpenWrt in the stock device (R5000 5G Industrial router from Yinghua Technologies) running the stock vendor firmware, you will need to update your bootloader as described in previous section. Remember to use -F (force upgrade) and -n (not keeping settings). U-Boot Recovery --------------- This procedure has been tested only with the OpenWrt-based U-boot bootloader. Assign your system static IP address 192.168.1.1 and start a TFTP server. The device will look for an initramfs image named openwrt-mediatek-filogic-gatonetworks_gdsp-initramfs-kernel.bin (so you may use openwrt/bin/targets/mediatek/filogic as root dir for your TFTP server). Power on the device while keeping the reset button pressed, until you see a TFTP request from 192.168.1.10. Your environment will be restored to it's default state. MAC addresses assignment ------------------------ MAC addresses are assigned slightly differently than in stock firmware. In particular, the 5 GHz Wi-Fi uses 2.4 GHZ MAC + 1, rather than reusing it with LA bit set as done in stock firmware. This MAC address is allocated to the device, so it can be used. The 2.4 GHz Wi-Fi MAC address is the label MAC. LAN MAC is used to set the special U-Boot environment ethaddr variable. device MAC address U-Boot env variable factory partition offset 2.4 GHz Wi-Fi :84 wifi_mac 0x4 5.8 GHz Wi-Fi :85 not present not present WAN :86 wan_mac 0x24 LAN :87 lan_mac 0x2A Notes ----- [1]: the OpenWrt-based U-Boot bootloader you will find installed in the re-branded device is configured to request for the initramfs image via TFTP for $gdsp_tftp_tries times before trying normal boot from NOR flash. Setting this U-Boot environment variable to 0x0 will disable the feature, which is not implemented in this patch. [2]: the exposed UART port is connected to ttyS1; the ttyS0 console port is not exposed. [3]: the provided bootloader environment has no provision for operating on BL2 and the FIP partitions. This is an intentional choice to make it (slightly) more difficult to brick the device. [4]: it seems GPIO 6 is used both for the "SYS" LED and external WDT. [5] BL2 expects to find FIP payload at a fixed offset, so some constraints apply.