staging/nbd/package/boot, branch master

ramips: add support for actiontec web7200

2026-02-15T09:45:40Z

Signed-off-by: John Crispin

qualcommax: ipq807x: add Zyxel NWA110AX support

2026-02-13T20:35:49Z

The Zyxel NWA110AX is a dual band 2x2:2 802.11ax wireless access point with PoE. The device is very similar to the NWA210AX except for being 2x2 instead of 4x4 in the 5GHz band and not having the 2.5GbE ethernet port. This commit factors out a common DTS and device definition and reuses it for both devices. Hardware: * SoC: Qualcomm IPQ8070A * RAM: 1GiB 1x Samsung K4A8G165WC-BCTD * Flash: 8MiB Winbond W25Q64DW SPI-NOR, 256MiB Winbond W29N02GZ SPI-NAND * WLAN 2.4GHz: QCN5024 2x2:2 802.11b/g/n/ax * WLAN 5GHz: QCN5054 2x2:2 802.11n/ac/ax * Ethernet: 1x 1GbE with AR8033 PHY * Serial Config: 3.3V TTL 115200-8-N-1, externally accessible * Serial Layout: GND TX RX 3.3V (don't connect, marked with triangle) * LEDs: 1x red, 1x green, 1x blue, 1x white * Buttons: 1x reset MAC addresses: * Uplink: base address on label * 2.4GHz WLAN: base + 1 * 5GHZ WLAN: base + 2 Flashing Notes: The device uses a dual-image setup and OpenWrt can only be installed as image 0. When the currently running stock firmware is image 0, OpenWrt will be installed as image 1, fail to boot and the device returns to stock firmware. If this happens, install any version of stock firmware so that it runs as image 1, before installing OpenWrt. Alternatively, if there already is a valid stock firmware in image 1, the "debug dual-image show" and "debug dual-image set boot-image image1" commands can be used in the stock CLI via serial/SSH/telnet to switch to image 1. Flashing with Stock Web Interface: * Get the OpenWrt factory image and rename it to a shorter name, for example "openwrt.bin" (the stock firmware has a character limit) * In the web interface, go to "Maintenance" -> "File Manager" -> "Firmware Package" (or click the link next to "Firmware Version" under "Device Information" on the dashboard) * Under "Upload File" browse to the renamed OpenWrt factory image and click on "Upload" Switch Boot Image: * OpenWrt to stock: "zyxel-bootconfig-ipq807x set image1" * Stock to OpenWrt: "debug dual-image set boot-image image0" Unbrick / Revert to Stock with the Boot Module: * Disconnect the device from power * Configure your machine to 192.168.1.103/24 and start a TFTP server * Put the stock firmware image into the TFTP server root and rename it to "ZLD-current" * Establish a serial connection to the device through the console port * Connect the device to power * When prompted, press a key to abort automatic boot and enter debug mode * Use the "atnz" command to flash the firmware image * Use the "atgo" command to boot from the newly flashed image Signed-off-by: Michael Lotz Link: https://github.com/openwrt/openwrt/pull/21849 Signed-off-by: Robert Marko

qualcommax: ipq60xx: add Netgear RBx350 support

2026-02-13T20:32:15Z

Netgear RBx350 are dual band 4 stream 802.11ax mesh devices from the Orbi series. The RBR350 is a router with a WAN and 3 LAN ports. The RBS350 is a satellite without WAN port, only 2 LAN ports and half the flash. The hardware is otherwise identical. They were sold in kits as RBK352, RBK353, RBK354 or RBK355, with one router and 1-4 satellites. Hardware: * SoC: Qualcomm IPQ6018 * RAM: 512MiB 1x Nanya NT5CC256M16ER-EK * Flash: 512MiB Winbond W29N04GZ or 256MiB Winbond W29N02GZ * WLAN 2.4GHz: QCN5022 2x2:2 b/g/n/ax * WLAN 5GHz: QCN5052 2x2:2 a/n/ac/ax * Ethernet: QCA8075 switch with 1 WAN and 3 LAN ports or 2 LAN ports * Serial Config: 3.3V TTL 115200-8-N-1, internal populated header * Serial Layout: 3.3V (don't connect, marked with dot) RX TX GND * LEDs: green/red power, white/red/green/blue status * Buttons: 1x Reset, 1x WPS MAC addresses: * LAN1: base address on label, stored in boarddata partition at 0x8 * LAN2: base + 1 * LAN3: base + 2 * WAN: base + 3 * 2.4GHz WLAN: base + 1 * 5GHz WLAN: base + 2 Flashing Notes: The stock firmware images are signed. Both the bootloader and the stock web interface check the signature and will fail to boot/flash. The bootloader automatically does NMRP when a gigabit LAN connection is present. The stock and factory images contain a U-Boot script that is executed when flashing using NMRP. This is used to alter and persist the U-Boot env with a boot command that works with unsigned firmware. Install OpenWrt: * Get the nmrpflash utility [0] and OpenWrt factory image * Find network interface to use: nmrpflash -L * Start nmrpflash: nmrpflash -i interface -f openwrt-...-factory.img * Connect the device LAN port closest to the power jack to the same network using gigabit * Plug the device in and wait for the bootloader to flash * Unplug and replug the device once the power LED blinks amber Revert to Stock: The boot command needs to be reverted before flashing the stock firmware, otherwise it will fail to boot and get stuck in recovery mode (red power LED flashing). * Run: fw_setenv bootcmd bootipq * Restart the device * Flash the stock firmware RBx350-Va.b.c.d.img using nmrpflash [0]: https://github.com/jclehner/nmrpflash Signed-off-by: Michael Lotz Link: https://github.com/openwrt/openwrt/pull/21656 Signed-off-by: Robert Marko

qualcommax: ipq807x: add Netgear RBx750 support

2026-02-13T20:27:16Z

Netgear RBx750 are tri band, 2.4GHz and 2x 5GHz, 8 stream 802.11ax mesh devices from the Orbi series. The RBR750 is a router with a WAN and 3 LAN ports. The RBS750 is a satellite without WAN port, only 2 LAN ports and half the flash. The hardware is otherwise identical. They were sold in kits as RBK752-RBK757, with one router and 1-6 satellites. Hardware: * SoC: Qualcomm IPQ8074 * RAM: 1GiB 1x Samsung * Flash: 512MiB Winbond W29N04GZ or 256MiB Winbond W29N02GZ * WLAN 2.4GHz: QCN5024 2x2:2 b/g/n/ax * WLAN 5GHz Low Band: QCN5054 2x2:2 a/n/ac/ax 5180-5320MHz * WLAN 5GHz High Band: QCN5054 4x4:4 a/n/ac/ax 5500-5700MHz * Ethernet: QCA8075 switch with 1 WAN and 3 LAN ports or 2 LAN ports * Serial Config: 3.3V TTL 115200-8-N-1, internal populated header * Serial Layout: Bottom <- RX, TX, GND, 3.3V (don't connect) -> Top * LEDs: green/red power, white/red/green/blue status * Buttons: 1x Reset, 1x WPS MAC addresses: LAN1: base address on label LAN2: base + 1 LAN3: base + 2 WAN: base + 1 2.4GHz: base + 2 5GHz-Low: base + 3 5GHz-High: base + 4 Flashing Notes: The stock firmware images are signed. Both the bootloader and the stock web interface check the signature and will fail to boot/flash. The bootloader automatically does NMRP when a gigabit LAN connection is present. The stock and factory images contain a U-Boot script that is executed when flashing using NMRP. This is used to alter and persist the U-Boot env with a boot command that works with unsigned firmware. Install OpenWrt: * Get the nmrpflash utility [0] and OpenWrt factory image * Find network interface to use: nmrpflash -L * Start nmrpflash: nmrpflash -i interface -f openwrt-...-factory.img * Connect the device LAN port closest to the power jack to the same network using gigabit * Plug the device in and wait for the bootloader to flash * Unplug and replug the device once the power LED blinks amber Revert to Stock: The boot command needs to be reverted before flashing the stock firmware, otherwise it will fail to boot and get stuck in recovery mode (red power LED flashing). * Run: fw_setenv bootcmd bootipq * Restart the device * Flash the stock firmware RBx750-Va.b.c.d.img using nmrpflash [0]: https://github.com/jclehner/nmrpflash Signed-off-by: Michael Lotz Link: https://github.com/openwrt/openwrt/pull/21938 Signed-off-by: Robert Marko

mediatek: add support for netis NX32U

2026-02-12T22:02:05Z

This PR adds support for netis NX32U router. Specification ------------- - SoC : MediaTek MT7981BA dual-core ARM Cortex-A53 1.3 GHz - RAM : 256 MiB DDR3 - Flash : SPI-NAND 128 MiB (ESMT) - WLAN : MediaTek MT7976CN dual-band WiFi 6 - 2.4 GHz : b/g/n/ax, MIMO 2x2 - 5 GHz : a/n/ac/ax, MIMO 2x2 - Ethernet : 10/100/1000 Mbps x3 (LAN, MediaTek MT7531AE) 10/100/1000 Mbps x1 (WAN, SoC internal phy) - USB : 3.0 - Buttons : Mesh, Reset - LEDs : 1x Power (green), unmanaged 1x Internet (green), gpio-controlled 1x WPS (green), gpio-controlled 1x WiFi 2.4 GHz (green), gpio-controlled 1x WiFi 5 GHz (green), gpio-controlled 1x LAN activity (green), switch-controlled 1x WAN activity (green), switch-controlled 1x USB (green), gpio-controlled - Power : 12 VDC, 1 A Installation ------------ 1. Connect to the router using ssh (user: admin, pass: web interface password) 2. Backup: ``` cat /dev/mtd0 | gzip -1 -c > /tmp/mtd0_spi0.0.bin.gz cat /dev/mtd1 | gzip -1 -c > /tmp/mtd1_BL2.bin.gz cat /dev/mtd2 | gzip -1 -c > /tmp/mtd2_u-boot-env.bin.gz cat /dev/mtd3 | gzip -1 -c > /tmp/mtd3_Factory.bin.gz cat /dev/mtd4 | gzip -1 -c > /tmp/mtd4_FIP.bin.gz cat /dev/mtd5 | gzip -1 -c > /tmp/mtd5_ubi.bin.gz ``` 3. Download mtd backup from the /tmp dir of the router to your PC using scp protocol 4. Upload OpenWrt 'bl31-uboot.fip', 'preloader.bin' images to the /tmp dir of the router using scp protocol 5. Write FIP and BL2 (replace bootloader): ``` mtd write /tmp/openwrt-mediatek-filogic-netis_nx32u-bl31-uboot.fip FIP mtd write /tmp/openwrt-mediatek-filogic-netis_nx32u-preloader.bin BL2 ``` 6. Place OpenWrt 'openwrt-mediatek-filogic-netis_nx32u-initramfs-recovery.itb' image on the tftp server (IP: 192.168.1.254) 7. Erase 'ubi' partition and reboot the router: mtd erase ubi reboot 8. U-Boot automatically boot OpenWrt recovery image from tftp server to the RAM 9. Upload OpenWrt 'sysupgrade.itb' image to the /tmp dir of the router (IP: 192.168.1.1) using scp protocol 10. Connect to the router using ssh and run: ``` ubidetach -p /dev/mtd4; ubiformat /dev/mtd4 -y; ubiattach -p /dev/mtd4 ubimkvol /dev/ubi0 -n 0 -N ubootenv -s 128KiB ubimkvol /dev/ubi0 -n 1 -N ubootenv2 -s 128KiB sysupgrade -n openwrt-mediatek-filogic-netis_nx32u-squashfs-sysupgrade.itb ``` Recovery -------- 1. Place OpenWrt 'openwrt-mediatek-filogic-netis_nx32u-initramfs-recovery.itb' image on the tftp server (IP: 192.168.1.254) 2. Press “Reset” button and power on the router. After ~10 sec release the button. 3. Use OpenWrt initramfs system for recovery +---------+-------------------+-----------+ | | MAC | Algorithm | +---------+-------------------+-----------+ | LAN | dc:xx:xx:d1:xx:18 | label | | WAN | dc:xx:xx:d1:xx:1a | label+2 | | WLAN 2g | de:xx:xx:11:xx:19 | | | WLAN 5g | de:xx:xx:71:xx:19 | | +---------+-------------------+-----------+ The LAN MAC was found in 'Factory', 0x1fef20 The WAN MAC was found in 'Factory', 0x1fef26 The WLAN 2g/5g MAC prototype was found in 'Factory', 0x4 Signed-off-by: Fil Dunsky Link: https://github.com/openwrt/openwrt/pull/21368 Signed-off-by: Hauke Mehrtens

mvebu: add support for RIPE Atlas Probe v5

2026-02-12T21:21:51Z

RIPE Atlas Probe v5 is a network measurement device based on Turris MOX. u-boot bootscript supports booting both from the original Turris BTRFS layout and default OpenWrt ext4 boot + root partition layout. Specifications: * SoC: Marvell ARMADA 3720 * RAM: 512 MiB, DDR3 * eMMC: 4G * Ethernet: 1x 1GbE MAC: LAN MAC: label on board Flash instructions: * For using the default ext4 layout, boot into a live system using tftpboot in u-boot and flash an OpenWrt SD image onto /dev/mmcblk0. * For the Turris layout, put the new rootfs into subvolume '@', not forgetting to add Image, device tree, and boot.scr to /boot. Misc: * USB connection is only for power. For UART access use the pin header: 1: GND 2: +1.8V 5: TX 6: RX * Flashing the image onto Turris Shield won't work. Use Turris MOX image instead. Signed-off-by: Tomáš Macholda Link: https://github.com/openwrt/openwrt/pull/20031 Signed-off-by: Hauke Mehrtens

mediatek: filogic: gl-mt2500 fix compatibles PHY variants

2026-02-10T23:03:05Z

These devices share the same "compatible" in device tree causing some incompatibilities (sysupgrades, ASU profile identification), assign a unique "compatible" and "model" to each variant. Context: Commit [1] added each variant's dts compatible to the SUPPORTED_DEVICES field of the other variant to make easy sysupgrades between these physically indistinguishable devices variants possible. But there were found three issues which does not allow this: - the sysupgrade's stricter check still used in some sysupgrade paths(this check is being replaced(and redundant) with the newer fwtool's SUPPORTED_DEVICES check using the info in images METADATA), this check will fail when sysupgrading from a different board_name(compatible dts) that the image was created for (image profile name).[2] - ASU needs unique "dts compatible" to identify the devices profile. - and an ASU's profile identification limitation when several devices from a common target share SUPPORTED_DEVICES entries.[3] There is a proposal for these issues but not yet implemented [4][3]. Until these issues are fixed we won't allow "easy" sysupgrades between these two device variants. Commit [5] avoided the ASU profile identification limitation but missed the required two unique dts compatibles in order to make the two variants fully work, although not allowing easy sysupgrade between them. [1]: https://github.com/openwrt/openwrt/commit/8d30e07180367cdeb4affd79adead6e1025355c9 [2]: sysupgrade stricter check https://github.com/openwrt/openwrt/issues/20566#issuecomment-3583555482 [3]: ASU proposal https://github.com/openwrt/asu/pull/1533 [4]: allow easy sysupgrade proposal https://github.com/openwrt/openwrt/pull/20947 [5]: https://github.com/openwrt/openwrt/commit/b71f4665cda10c284c9460409ae30fb9b0beecf8 Fixes: b71f466 ("mediatek: filogic: fix supported_devices list for gl-mt2500") Fixes: 8d30e07 ("mediatek: filogic: fix for new GL.iNet GL-MT2500/GL-MT2500A hardware revision") Fixes: https://github.com/openwrt/openwrt/issues/20566 Fixes: https://github.com/openwrt/asu/issues/1525 Signed-off-by: Mario Andrés Pérez Link: https://github.com/openwrt/openwrt/pull/21842 Signed-off-by: Hauke Mehrtens

uboot-envtools: fix meraki mr24 definition

2026-02-08T17:37:43Z

These two are redundant definitions according to dts. A value of 4 (CRC no redundancy) makes no sense. Signed-off-by: Rosen Penev Link: https://github.com/openwrt/openwrt/pull/16618 Signed-off-by: Robert Marko

uboot-envtools: fix meraki mx60 definition

2026-02-08T17:37:43Z

There are two redundant sections. One at 0x0 and the other at 0x80000. Signed-off-by: Rosen Penev Link: https://github.com/openwrt/openwrt/pull/16618 Signed-off-by: Robert Marko

uboot-sunxi: bump to 2025.10

2026-02-07T23:56:16Z

Compile-tested: all targets Runtime-tested: - Linksprite pcDuino v2 (A10) - Banana Pro (A20) - Banana Pi M2 Berry (V40) - Banana Pi P2 Zero (H2+) - Pine64+ (A64) Patches refreshed as required. Signed-off-by: Zoltan HERPAI