Mikrotik RB952Ui-5ac2nD

21.02.x is done and dusted, apart from bugfixes, nothing is going to happen there.
22.03.x is branched and in its -rc phase, that /might/ still allow in (easy-) new device additions, but if you do want anything you to happen, someone (which might end up being you, yourself) will have to provide a patch set against master/ snapshots. Only master accepts new devices additions, only once it's been added there, it /might/ be backported to 22.03.x, but chances for 21.02.x are essentially zero at this point.

Already have run it successfully on 21.02.3. Thnx.)

What can be done - and what stands a chance for backporting to the official 21.02.x are two different pairs of shoes. The precondition is always to go through master, from there are still quite reasonable chances for 22.03.x, but only minimal ones for 22.02.x.

Hello expert,

I also see this problem on my Meraki MR33 platform. The error message as below:

Thu Jun  9 23:19:11 2022 kern.info kernel: [   18.319701] ath10k 5.15 driver, optimized for CT firmware, probing pci device: 0x50.
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)
Thu Jun  9 23:19:11 2022 user.info kernel: [   23.078074] kmodloader: done loading kernel modules from /etc/modules.d/*

Now I am compiling the code and hope it works well.

Regards