Lost wireless interface after downgrade 21.02 to 19.07

Installing and Using OpenWrt
1

Hello experts,

I lost all wireless interface on Meraki MR33 after downgrading OpenWRT from 21.02 to 19.07. I see the similar error logs as below during system booting.

Thu Jun  9 23:19:11 2022 kern.info kernel: [   18.320525] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
Thu Jun  9 23:19:11 2022 kern.info kernel: [   18.327006] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Thu Jun  9 23:19:11 2022 kern.info kernel: [   20.060182] ath10k_pci 0000:01:00.0: qca9887 hw1.0 target 0x4100016d chip_id 0x004000ff sub 0000:0000
Thu Jun  9 23:19:11 2022 kern.info kernel: [   20.060238] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
Thu Jun  9 23:19:11 2022 kern.info kernel: [   20.070276] 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
Thu Jun  9 23:19:11 2022 kern.info kernel: [   20.197474] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 546cca0d
Thu Jun  9 23:19:11 2022 kern.err kernel: [   20.198037] ath10k_pci 0000:01:00.0: failed to read device EEPROM at 0000
Thu Jun  9 23:19:11 2022 kern.warn kernel: [   20.203731] ath10k_pci 0000:01:00.0: failed to read calibration data from EEPROM: -22
Thu Jun  9 23:19:11 2022 kern.err kernel: [   20.238607] ath10k_pci 0000:01:00.0: otp calibration failed: 2
Thu Jun  9 23:19:11 2022 kern.err kernel: [   20.238654] ath10k_pci 0000:01:00.0: failed to run otp: -22 (download-cal-data)
Thu Jun  9 23:19:11 2022 kern.err kernel: [   20.243423] ath10k_pci 0000:01:00.0: could not init core (-22)
Thu Jun  9 23:19:11 2022 kern.err kernel: [   20.250727] ath10k_pci 0000:01:00.0: could not probe fw (-22)
Thu Jun  9 23:19:11 2022 kern.info kernel: [   21.559596] ath10k_ahb a000000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003900ff sub 0000:0000
Thu Jun  9 23:19:11 2022 kern.info kernel: [   21.559654] ath10k_ahb a000000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
Thu Jun  9 23:19:11 2022 kern.info kernel: [   21.572451] 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
Thu Jun  9 23:19:11 2022 kern.err kernel: [   21.650540] 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
Thu Jun  9 23:19:11 2022 kern.err kernel: [   21.698362] ath10k_ahb a000000.wifi: failed to fetch board-2.bin or board.bin from ath10k/QCA4019/hw1.0
Thu Jun  9 23:19:11 2022 kern.err kernel: [   21.698419] ath10k_ahb a000000.wifi: failed to fetch board file: -12
Thu Jun  9 23:19:11 2022 kern.err kernel: [   21.706904] ath10k_ahb a000000.wifi: could not probe fw (-12)
Thu Jun  9 23:19:11 2022 kern.info kernel: [   22.911417] ath10k_ahb a800000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003900ff sub 0000:0000
Thu Jun  9 23:19:11 2022 kern.info kernel: [   22.911474] ath10k_ahb a800000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
Thu Jun  9 23:19:11 2022 kern.info kernel: [   22.924252] 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
Thu Jun  9 23:19:11 2022 kern.err kernel: [   22.955212] 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
Thu Jun  9 23:19:11 2022 kern.err kernel: [   23.050161] ath10k_ahb a800000.wifi: failed to fetch board-2.bin or board.bin from ath10k/QCA4019/hw1.0
Thu Jun  9 23:19:11 2022 kern.err kernel: [   23.050218] ath10k_ahb a800000.wifi: failed to fetch board file: -12
Thu Jun  9 23:19:11 2022 kern.err kernel: [   23.058612] ath10k_ahb a800000.wifi: could not probe fw (-12)

Does anyone has the experience for this?

Regards

2

Reset your router to defaults and configure from scratch. The config files are not compatible between versions.

It also looks like your EEPROM, which contains the factory calibration data, may be corrupted -- if that is the case, it is game over.

1 Like
3

Hello psherman,

Thanks for your quick help. I tried to reset the device via WebUI many times but no effect. Did I miss an important step on this?

For more additional information, even if I upgraded the software back to 21.02, the wireless still didn't come back.

Regards

4

Yeah, from the logs and the problem description, your EEPROM has been corrupted or overwritten. It is hard to say specifically what caused this without knowing how you were working with OpenWrt and the upgrade process, but if you manually wrote to the wrong partition, that would certainly cause the issue you're seeing.

Because the missing information is from the factory and is unique to your specific unit, you're not going to be able to recover that calibration data (you can't substitute the data from another device, as that may cause problems with the radio performance and may even cause it to operate out of the regulatory limits).

This means that the unit is, unfortunately, a brick (at least as far as wifi goes). You could use it as a single-physical-port OpenWrt device for non-wifi purposes, but otherwise it's dead.

5

What a sad story. I have another 3 MR33. I need to test different OpenWRT builds for the wireless roaming and 802.11 kvr performance. May I have a way to avoid this situation occurring again?

6

How did you perform the upgrade?

7

Just upload the sysupgrade.bin file via web UI without saving configuration file.

8

I don't have experience with this device to directly help you with the process, but did you follow all of the instructions on the device info page?