Meraki MR26 Using OpenWrt

Hi Everyone, I have a Meraki MR26 which I would like to flash with OpenWrt.
I have found the below information but I cannot find where to download the firmware;a=commit;h=e37ba80633c30ff179df92e8826ba52ff00b2a66

Based on the date in that commit, the image is available in snapshots:

Unless you're fine with WebUI-less barebones installation, I'd recommend you use the Image Builder from the link above and create images containing all the packages you may ever need in the future, as snapshots change and you may not be able to install certain packages without updating firmware in the future.

@tmomas @bobafetthotmail @richb-hanover the MR26 page needs to be updated:

Thanks, I will look into the Image Builder, I am very new to using OpenWrt.
I see there are notes of issues with this model not sure if it is even worth doing if it only supports 802.11bg

The instructions say.

  1. Before connecting the power, get ready flood the serial console program
    with the magic: xyzzy . This is necessary in order to get into the
    u-boot prompt. Once Ready: connect power cable.

what does this mean by the term xyzzy?

1 Like

ask @chunkeey who authored the commit.

1 Like

Some lovely vendors password protect access to u-boot, in this case the password seems to be "xyzzy". Combined with a short autoboot value, you really need to be prepared and enter this password many times in succession, in order to have it ready just at the right time frame during which the bootloader is listening for it.

Aren't these vendors just great in their eternal wisdom?!


Even given that restriction, there may be people willing to take these devices off your hands and cover shipping, for tinkering or adding an 802.11bg AP to their network.

In the instructions, it advises to download openwrt-meraki-mr26 initramfs file from can someone please point me to the location for this file

That xyzzy-thingy is a magic string.

In case of many Merakis (MR26, MR32, MR33, ...) it's the configured CONFIG_AUTOBOOT_STOP_STR for this very board.

For the (missing) initramfs-images: These are sadly not provided by the build-bot. Big issue here is that the builder generates one big initramfs for the whole target and these are usually too big and uboot stumbles.

Yes, this is unfortunately more magic. The best option is to generate one yourself. You need to download openwrt sources and compile the image with CONFIG_TARGET_ROOTFS_INITRAMFS option set (In OpenWrt's menuconfig => select Target Images => ramdisk. (If the generated u-boot doesn't boot, see if enabling the compression option under the ramdisk entry - set it to lzma or xz) helps.


This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.