Hi all,
I'm building OpenWrt for the ZLT X28, a 5G CPE with a MediaTek MT6890 (4x Cortex-A55). It's at the point where I use it as my actual router, so I want to introduce it here and ask a few things before I publish it the wrong way.
What it is
OpenWrt 23.05.5 userspace (armsr/armv8, fw3 with iptables-legacy) on the vendor 4.19.205 kernel. There's no mainline support for this SoC, so this isn't a clean port. The idea is a normal OpenWrt box that you manage in LuCI and UCI, not a copy of the vendor web UI.
What's done (all on my own unit)
- Boots from slot A of the A/B layout. Slot B (stock) is untouched for now, so there's still a way back.
- 5G data. The modem is a normal netifd interface (
proto x28_mipc) with its own LuCI protocol page. IPv4, IPv6, IPv4v6, and the APN comes from the SIM if you leave it empty. The IPv6 prefix goes to the LAN. - LAN switch (MT7531), DHCP and DNS, firewall and NAT. A Linksys router now sits behind it as a client.
- Wi-Fi on the MT7915 dual band through the vendor driver, with a netifd handler so it shows up under Network > Wireless. Both radios come up with WPA2. I haven't done real throughput or client testing yet.
- Front panel LEDs follow radio, signal and WAN state.
- Settings survive reboots. Root starts with an empty password like stock OpenWrt, and SSH is key-only on port 22, LAN only.
- The modem stack starts by itself at boot.
- It runs cool: around 40 C idle on the SoC, and the CPU is almost fully idle. Stock sat around 65 C idle without a fan, and about 46 C with a 12 V fan.
- Flashing tools that check every write (hashes, neighbouring partitions, the other slot) and a boot counter that behaves like stock's. I lost a lot of time on that one: the preloader adds a try on every boot, stock resets it after a good one, and my first image didn't.
Where I'm taking it: a stable release with a recovery slot
Right now both slots hold a full firmware. The plan is to stop doing that:
- Slot A: stable OpenWrt, the thing you actually run.
- Slot B: becomes the recovery slot, a small kernel and recovery path whose job is to rescue the box and install or reinstall OpenWrt on slot A.
- A way back to the stock firmware from that recovery path, so nobody is stuck with mine.
That way I don't have to keep two full firmwares in flash, which frees up storage, and recovery no longer depends on the download agent and a UART. That's the path to a stable release for me.
Other things on the list:
- A stable tagged release (every merge to main already gets a 0.x pre-release tag).
- Proper Wi-Fi and throughput testing, and checking more LED states.
- Fan control from LuCI. Right now the fan just runs flat out.
- Local SMS and voice, which is what I originally wanted this box for.
- Own kernel. I have the SDK of a sibling device with the same SoC (Fibocom FG360, 4.19). I haven't tried building a kernel from it, and I won't until the router itself is finished. If it works, I could publish a matching kmod feed, turn on nftables and namespaces, and move to a newer OpenWrt userland.
- sysupgrade for the new layout.
What's not great
- The modem side needs the vendor userspace daemons and libraries, which are closed binaries. I can't put them in a public image. My build script copies them from your own stock firmware dump. So what I can publish is the build tooling and the packages, not a ready-to-flash image.
- Kernel limits come from the vendor 4.19.205 build: the official feeds' kernel modules don't load (they're built for 5.15), there's no nf_tables so I'm on fw3 and iptables-legacy, and no namespaces so no ujail. Userspace packages from the 23.05.5 feeds install fine.
- Slot A isn't marked as confirmed in the boot control record. I only reset the tries counter after each good boot, which stops it running out and keeps the fallback to stock B for now.
- One unit, one SIM, one carrier.
What I need help with
- What does a wiki device page or a Table of Hardware entry need for a device that isn't in a release? Is a page for a custom build on a vendor kernel acceptable, and what should it say?
- How do other projects publish firmware that needs blobs the user has to extract themselves? Is there a convention?
- Has anyone done a recovery slot like this on an A/B NAND device with UBI and a preloader that picks the slot? What did you use for the recovery side, and how did you handle sysupgrade?
- Does anyone else have this box, or a rebrand of it (MT6890 + MT7915 + MT7531)? I'd like to compare notes.
Repo: https://github.com/mralinp/zlt-x28-openwrt
I can post logs, the partition layout and the boot flow if that helps.