Refer to OpenWrt Actiontec MI424WR page for the bulk of device information.
Notices where I had to deviate from the OpenWrt documentation:
- The UART uses 115200n8.
- When I held down RESET for 10+ seconds and the router rebooted, the web UI offered me to change the router admin password.
- As I had a UART connected and the jungo script was failing, and I had
TFTP working anyway (it is required for the install...) I just downloaded
the new RedBoot image with TFTP from the host, like this:
Wireless Broadband Router> load -u tftp://192.168.1.2/rb-mi424wr-ROM.bin -r 0 - After installing RedBoot it was apparent that only the WAN port is working for downloading kernel and rootfs, so use the WAN port only with RedBoot.
- Created linux and root partitions like this:
fis create -b 0x00080000 -l 0x00400000 -s 0x00400000 -f 0x50040000 -e 0x00080000 -r 0x00080000 -n linux
Files
- rb-mi424wr-ROM.bin - RedBoot flash image for the MI424-WR A/C/D
Getting OpenWRT up on it
Installing OpenWrt currently requires UART serial console access
Kernel TODO
- Enable proper DSA tagging in the KS8995 driver
- 2025-08-22: Add Actiontec MI424-WR device trees using the below added bindings etc.
2025-08-22: Add proper handling of the MMIO GPIO on the expansion bus (merged 2025-08-25)- 2025-08-20: Add IXP4xx UDC bindings this has nothing to do with this device, but was causing DT binding warnings.
2025-08-13: Turn the KS8995 "phy" device into a DSA switch so we can handle this in some reasonable manner (merge 2025-08-19)2025-06-25: Fix up the KS8995 device tree bindings so it is properly using DSA bindings (merged 2025-06-27)