This commit adds support for the Cisco Meraki MR70/Go GR60. The Meraki MR70 is a Cisco 802.11ac/WiFi 5 outdoor AP with 1 Ethernet port. It can be powered by a 12V DC barrel jack (5.5x2.5mm, center positive) or via 802.3af POE. The Meraki Go GR60 (codename: Dungbeetle Omni) is identical to the MR70 (codename: Toe Biter Omni), so this document will refer to both devices as the MR70. MR70 hardware info: * CPU: Qualcomm IPQ4029 * RAM: 256MB DDR3 * Storage: 128 MB (TSOP48 NAND, 3.3V) * Networking: 1 Gigabit Ethernet * WiFi: QCA4019 802.11b/g/n/ac * Serial: Internal header (J10, 2.54mm, unpopulated) This device ships with secure boot, and cannot be flashed without external programmers (TSOP48 NAND and I2C EEPROM)! Disassembly: Note: This is an outdoor device that is ultrasonically welded and glued to weather seal it. Disassembly will compromise the weather seal! Start by removing the product label on the rear metal mounting plate. There are four Torx T8 screws under the sticker, remove the screws and the mounting plate. Remove the two Philips screws under the plate. Using a chisel (or razor blade) and hammer, cut around the circumfrence of the device. You need to cut through approximately 2mm of ultrasonically welded plastic. After cutting through the plastic, heat the device using a hair drier (or similar) to soften the glue. A heatgun is NOT recommended as it will damage the plastic. It is only required to heat the device until warm (~40C-50C). Using a plastic pry tool, insert it along the cut you made around the edge and gently separate. Insert a guitar pick into the opening while gently lifting the front to cut the glue. The device is glued around the entire circumfrence. Once you have removed the plastic front, remove the 4 Philips screws holding down the main PCB. Release the two WiFi antennas by gently bending the antenna PCBs to the middle of the unit and pulling up. Lift the top of the PCB gently while pushing the Ethernet port into the housing to release it. Turn the PCB over and remove the three Philips screws holding the metal heat spreader. The TSOP48 NAND flash (U9, S34ML01G200 or W29N01HV) is located under the metal heat spreader. To flash, you need to desolder the TSOP48 or use a 360 clip. You also need to reprogram the I2C EEPROM (U20, Atmel 24c64). It is not necessary to desolder the I2C EEPROM, a ch341a USB programmer and SOP-8 clip are inexpensive (~$10) and work well. Installation: The dumps to flash can be found in this repository: https://github.com/halmartin/meraki-openwrt-docs/tree/main/mr70_gr60 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 from the GitHub repository above (dump contains OOB data) and overwrite the `u-boot` portion of NAND from `0x738000`-`0x948000` (length `0x210000`). Offsets here include OOB data. * Decompress `ubi.bin.gz` dump from the GitHub repository above (dump contains OOB data) and overwrite the `ubi` portion of NAND from `0xc60000-0x7fe0000` (length `0x7380000`). Offsets here include OOB data. * Dump your original EEPROM. Change the byte at offset `0x49` to `0x1e` (originally `0x2d` or `0x26`). 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_mr70-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_mr70-squashfs-sysupgrade.bin root@192.168.1.1:/tmp/ ssh root@192.168.1.1 "sysupgrade -n /tmp/openwrt-ipq40xx-generic-meraki_mr70-squashfs-sysupgrade.bin" ``` * OpenWrt should now be installed on the device. Signed-off-by: Hal Martin <hal.martin@gmail.com> Link: https://github.com/openwrt/openwrt/pull/22050 Signed-off-by: Robert Marko <robimarko@gmail.com> |
||
|---|---|---|
| .devcontainer/ci-env | ||
| .github | ||
| .vscode | ||
| config | ||
| include | ||
| LICENSES | ||
| package | ||
| scripts | ||
| target | ||
| toolchain | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| BSDmakefile | ||
| Config.in | ||
| COPYING | ||
| feeds.conf.default | ||
| Makefile | ||
| README.md | ||
| rules.mk | ||
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
