[rpi-02w] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)

Description

When using Raspberry Pi Zero 2w with latest Bookworm aarch64, there is error in the log:

[   13.193367] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   13.433772] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[   13.434558] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Jun 14 2023 07:27:45 version 7.45.96.s1 (gf031a129) FWID 01-70bd2af7 es7

I'm not sure what this error means?

Why first message shows using brcm/brcmfmac43430-sdio for chip BCM43430/1 but actually loaded firmware is brcm/brcmfmac43436s-sdio (see version 7.45.96.s1)? And why it logged as Firmware: BCM43430/1? Is this also a bug?

wifi works in client and AP mode, but for some unknown reason don't works in ad-hoc mode when configured through NetworkManager (I already reported it here). Is this error can be the root of cause for not working ad-hoc?

I read that there is some kind of confusion with wifi firmware for rpi02w wifi module.
It appears (correct me if I'm wrong) that rpi02w can use one of 2 module 43436 or 43436s. But actually they are hardware identical to 43430B0 and 43430A1 which are used for Raspberry Pi 3 and they have exactly the same id. I'm confused why there are two names 43436 and 43430B0 for two hardware identical modules with the same id?

And there are two firmwares for the same module - from Synaptics and from Infineon. So, if I understand correctly, in total there are 4 firmwares for 2 wifi modules. And it's not clear how the system selects which firmware to use - Synaptics or Infineon. Is there a way to choose which one will be used?

Steps to reproduce:

1. Install latest Raspberry Pi Bookworm aarch64 on Raspberry Pi Zero 2w.
2. Run sudo apt update && sudo apt upgrade
3. Run dmesg | grep "brcm"

Expected result: no errors

Actual result: brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)

Device (s)

Raspberry Pi Zero 2 W

System

$ cat /etc/rpi-issue
Raspberry Pi reference 2024-03-15
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, f19ee211ddafcae300827f953d143de92a5c6624, stage2

$ vcgencmd version
May 24 2024 15:31:28 
Copyright (c) 2012 Broadcom
version 4942b7633c0ff1af1ee95a51a33b56a9dae47529 (clean) (release) (start)

$ uname -a
Linux rpi02w 6.6.31+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linux

Logs

[   13.193367] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   13.433772] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[   13.434558] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Jun 14 2023 07:27:45 version 7.45.96.s1 (gf031a129) FWID 01-70bd2af7 es7

Additional context

No response

No source file or test is named. Start by reproducing the Raspberry Pi Zero 2 W setup and running the reported dmesg command, then trace the brcmfmac firmware-selection and txcap_blob messages. Done means determining whether the log is an actionable driver bug, explaining the firmware names and selection, and establishing whether it affects ad-hoc mode.