This commit adds support for the Meraki Z3C "Teleworker" device with 802.11ac, LTE Cat 3 modem, and an integrated 5 port Gigabit switch. Port 5 has POE output (802.3af). The WAN port is used for tftp booting in U-Boot. This device ships with secure boot, and cannot be flashed without an external programmer. ||| |--|--| |Model|Z3C| |CPU|Qualcomm Atheros IPQ4029| |Flash MB|128 NAND| |RAM MB|512| |WLAN Hardware|Qualcomm Atheros IPQ4029| |WLAN 2.4GHz|b/g/n 2x2| |WLAN 5.0GHz|a/n/ac 2x2| |WWAN|LTE Cat 3| |Ethernet 1Gbit ports|5| The LAN/WiFi MAC addresses are sourced from an internal I2C EEPROM. Z3C-HW-NA (NA: North America) supports LTE bands: 2,4,5,13,17 Z3C-HW-WW (WW: World-wide) supports LTE bands: 1,3,7,8,20 Disassembly: Remove the four T8 screws on the bottom of the device under the rubber feet. Using a guitar pick or similar plastic tool, insert it on the side between the bottom case and the side, pry up gently. The plastic bottom has 18 latches around the perimeter (but none on the rear by the Ethernet ports). Remember to remove the SIM tray! Gently remove the metal RF shield on the bottom of the PCB. The TSOP48 NAND flash (U30, Spansion S34ML01G200TFV00) is located on the bottom side of the PCB (facing you as you remove the bottom plastic). To flash, you will need to desolder the TSOP48. Attempts to flash in-circuit using a 360 clip were unsuccessful. The SOIC8 I2C EEPROM (U32, Atmel 24C64) is located on the bottom side of the PCB under a metal RF shield. It can be flashed in circuit using a chip clip. You may have to bend the RF shield up to fit the chip clip. The UART header is on the top (opposite) side of the PCB. You do not need to remove any more screws to remove the PCB. The PCB has some thermal interface material for heat dissipation and will be slightly difficult to remove the first time. Gently pry up on the green PCB from one of the front corners until the thermal pads break contact with the top case. You can then lift out the entire PCB, including the attached LTE/WiFi antennas. Installation: The dumps to flash can be found in this repository: https://github.com/halmartin/meraki-openwrt-docs/tree/main/z3c The device has the following flash layout (offsets with OOB data): ``` 0x000000000000-0x000000100000 : "sbl1" 0x000000100000-0x000000200000 : "mibib" 0x000000200000-0x000000300000 : "bootconfig" 0x000000300000-0x000000400000 : "qsee" 0x000000400000-0x000000500000 : "qsee_alt" 0x000000500000-0x000000580000 : "cdt" 0x000000580000-0x000000600000 : "cdt_alt" 0x000000600000-0x000000680000 : "ddrparams" 0x000000700000-0x000000900000 : "u-boot" 0x000000900000-0x000000b00000 : "u-boot-backup" 0x000000b00000-0x000000b80000 : "ART" 0x000000c00000-0x000007c00000 : "ubi" ``` * Dump your original NAND (if using nanddump, include OOB data). * Decompress `u-boot.bin.gz` dump (contains OOB data) and overwrite the `u-boot` portion of NAND from `0x738000-0x948000` (length `0x210000`). * Decompress `ubi.bin.gz` dump (contains OOB data) and overwrite the `ubi` portion of NAND from `0xc60000-0x8400000` (length `0x77a0000`). * Dump your original EEPROM. Change the byte at offset `0x49` to `0x1e` (originally `0x2a`). Remember to re-write the EEPROM with the modified data. * This can be done on Linux via the following command: `printf "\x1e" | dd of=/tmp/eeprom.bin bs=1 seek=$((0x49)) conv=notrunc` **Note**: the device will not boot if you modify the board major number and have not yet overwritten the `ubi` and `u-boot` regions of NAND. * Resolder the NAND after overwriting the `u-boot` and `ubi` regions. OpenWrt Installation: * After flashing NAND and EEPROM with external programmers. Plug in an Ethernet cable and power up the device. * The new U-Boot build uses the space character `" "` (without quotes) to interrupt boot. * Interrupt U-Boot and `tftpboot` the OpenWrt initramfs image from your tftp server ``` dhcp setenv serverip <your_tftp> tftpboot openwrt-ipq40xx-generic-meraki_z3c-initramfs-uImage.itb ``` * Once booted into the OpenWrt initramfs, created the `ART` ubivol with the WiFi radio calibration from the mtd partition: ``` cat /dev/mtd10 > /tmp/ART.bin ubiupdatevol /dev/ubi0_1 /tmp/ART.bin ``` * `scp` the `sysupgrade` image to the device and run the normal `sysupgrade` procedure: ``` scp -O openwrt-ipq40xx-generic-meraki_z3c-squashfs-sysupgrade.bin root@192.168.1.1:/tmp/ ssh root@192.168.1.1 "sysupgrade -n /tmp/openwrt-ipq40xx-generic-meraki_z3c-squashfs-sysupgrade.bin" ``` * OpenWrt should now be installed on the device. * Note: To use the LTE modem as a WWAN, you must install `modemmanager` (you probably also want `luci-proto-modemmanager`) and then configure the modem for your provider. Due to OpenWrt policies these packages are not included in the initramfs/sysupgrade image. Signed-off-by: Hal Martin <hal.martin@gmail.com> Link: https://github.com/openwrt/openwrt/pull/23307 Signed-off-by: Robert Marko <robimarko@gmail.com>
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.7+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0
