Adding OpenWrt support for MR74

root@OpenWrt:/# printenv
/bin/ash: printenv: not found
root@OpenWrt:/# 

Might be fw_printenv, etc, no openwrt device access atm, cannot check.

root@OpenWrt:/# fw_printenv
Cannot parse config file '/etc/fw_env.config': No such file or directory
root@OpenWrt:/#

I think this is your issue. Try adding

DEVICE_DTS_CONFIG := config@3

to target/linux/ipq40xx/image/generic.mk. Either put it in the mr33 section or create a new one for the mr74.

I'm not actually building the image. I am using premade images from a mr33 that has openwrt on it. You would have to walk me thru this because I am very new to this level of openwrt and embedded devices

can you try these? You can just flash the sysupgrade over your current installation:
openwrt-ipq40xx-generic-meraki_mr74-initramfs-fit-uImage.itb
openwrt-ipq40xx-generic-meraki_mr74-squashfs-sysupgrade.bin

1 Like

You are my hero! It works! Thank you soooo much! I will do some testing to see what is and isn't working an update from there. You guys are my heros. Thank you all for all the assistance!

1 Like

Would it be safe to say I have the first and only MR74 on OpenWRT?!

Yes it would be fairly safe to say, since there aren't many of these devices around and users wishing to install OpenWrt onto them. Can you confirm if your MR74s were recently connected to Meraki and updated? Also I am assuming that you didn't need to use a NAND clip? If so this may indicate that these devices aren't being locked down like the MR33s.

It was updated and I do have a 360 clip with a NAND flasher. I wish this device wasn't locked down it would make it so much easier. Considering the many uses of the MR74 I would say it is worth the price of a 360 clip and NAND flasher. About the only difference between the MR33 and the MR74 is the frame and the that it uses only one "external" wifi controller.

When you created this image did you use the MR33 base to it? I don't have access to the radios at the moment for some reason

12.251013] ath10k 5.15 driver, optimized for CT firmware, probing pci device: 0x50.
[   12.251935] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
[   12.258446] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[   13.772714] ath10k_pci 0000:01:00.0: qca9887 hw1.0 target 0x4100016d chip_id 0x004000ff sub 0000:0000
[   13.772769] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   13.785849] ath10k_pci 0000:01:00.0: firmware ver 10.1-ct-87-__fW-022-ecad3248 api 2 features wmi-10.x,has-wmi-mgmt-tx,mfp,txstatus-noack,wmi-10.x-CT,ratemask-CT,txrate-CT,get-temp-CT,tx-rc-CT,cust-stats-CT,retry-gt2-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT crc32 61a92df5
[   13.816506] ath10k_pci 0000:01:00.0: Loading BDF type 0
[   14.160411] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 546cca0d
[   14.160980] ath10k_pci 0000:01:00.0: failed to read device EEPROM at 0000
[   14.166545] ath10k_pci 0000:01:00.0: failed to read calibration data from EEPROM: -22
[   14.201478] ath10k_pci 0000:01:00.0: otp calibration failed: 2
[   14.201512] ath10k_pci 0000:01:00.0: failed to run otp: -22 (download-cal-data)
[   14.206210] ath10k_pci 0000:01:00.0: could not init core (-22)
[   14.213511] ath10k_pci 0000:01:00.0: could not probe fw (-22)
[   15.458235] ath10k_ahb a000000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003900ff sub 0000:0000
[   15.458287] ath10k_ahb a000000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   15.470155] ath10k_ahb a000000.wifi: firmware ver 10.4b-ct-4019-fW-13-5ae337bb1 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 6b2b5c5b
[   15.498491] ath10k_ahb a000000.wifi: Loading BDF type 0
[   15.556567] ath10k_ahb a000000.wifi: failed to fetch board data for bus=ahb,vendor=0000,device=0000,subsystem-vendor=0000,subsystem-device=0000,variant=Meraki-MR33 from ath10k/QCA4019/hw1.0/board-2.bin
[   15.775484] ath10k_ahb a000000.wifi: failed to fetch board-2.bin or board.bin from ath10k/QCA4019/hw1.0
[   15.775557] ath10k_ahb a000000.wifi: failed to fetch board file: -12
[   15.784026] ath10k_ahb a000000.wifi: could not probe fw (-12)
[   16.706872] ath10k_ahb a800000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003900ff sub 0000:0000
[   16.706963] ath10k_ahb a800000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   16.720332] ath10k_ahb a800000.wifi: firmware ver 10.4b-ct-4019-fW-13-5ae337bb1 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 6b2b5c5b
[   16.747218] ath10k_ahb a800000.wifi: Loading BDF type 0
[   16.754815] ath10k_ahb a800000.wifi: failed to fetch board data for bus=ahb,vendor=0000,device=0000,subsystem-vendor=0000,subsystem-device=0000,variant=Meraki-MR33 from ath10k/QCA4019/hw1.0/board-2.bin
[   16.977273] ath10k_ahb a800000.wifi: failed to fetch board-2.bin or board.bin from ath10k/QCA4019/hw1.0
[   16.977346] ath10k_ahb a800000.wifi: failed to fetch board file: -12
[   16.985801] ath10k_ahb a800000.wifi: could not probe fw (-12)

Well this maybe a hardware failure issue I have had it in and out of the frame and possibly had little hands all over it.

I made a mistake in the sysupgrade image I sent you. Could you please do the following:

edit file /lib/upgrade/platform.sh using vi
go to line 168

where it says meraki,mr33), change this to look like:

meraki,mr33 |\
meraki,mr74)

and save the file. Here is the diff.

I have updated the images in the box.com URLs. You then need to redownload the sysupgrade from the same URL and flash it. You'll then have wireless working again and be able to upgrade as normal.

Let me know if you have any issues.

1 Like

That did the trick for sure Thanks!

1 Like

Ok so just using the standard bridge seems to work just fine but when I try to do VLAN per SSID it doesn't work.

VLAN support won't work. There is a PR in progress that will rectify this.

Do you know if it is possible to get a page for the MR74 like the MR33 has and have it updated with new firmware as it is released?

Since Meraki's already in the hw list, you should be able to request a wiki account, and add the page yourself.

How would I go about building a new sysupgrade bin for a device?

The MR74 is now included in the development snapshot builds so you might not need to build, depending on your use case. Otherwise you can follow the instructions on Github.