What is the symptom you face? And does WiFi work if you disable Bluetooth?
Are there more logs from the brcmfmac driver, particularly which firmware blob it is actually looking for? They are all present in the armbian-firmware package, but it seem to look for the wrong filename:
lrwxrwxrwx 1 root root 79 Sep 23 05:21 BCM4345C0.amlogic,sm1.hcd -> BCM4345C0_003.001.025.0162.0000_Generic_UART_37_4MHz_wlbga_ref_iLNA_iTR_eLG.hcd
lrwxrwxrwx 1 root root 79 Sep 23 05:21 BCM4345C0.firefly,rk3566-roc-pc.hcd -> BCM4345C0_003.001.025.0162.0000_Generic_UART_37_4MHz_wlbga_ref_iLNA_iTR_eLG.hcd
lrwxrwxrwx 1 root root 79 Sep 23 05:21 BCM4345C0.radxa,zero2.hcd -> BCM4345C0_003.001.025.0162.0000_Generic_UART_37_4MHz_wlbga_ref_iLNA_iTR_eLG.hcd
-rw-rw-r-- 1 root root 57K Sep 23 05:21 BCM4345C0.raspberrypi,4-compute-module.hcd
-rw-rw-r-- 1 root root 56K Sep 23 05:21 BCM4345C0_003.001.025.0162.0000_Generic_UART_37_4MHz_wlbga_ref_iLNA_iTR_eLG.hcd
...
lrwxrwxrwx 1 root root 31 Sep 23 05:21 brcmfmac43455-sdio.amlogic,sm1.bin -> ../cypress/cyfmac43455-sdio.bin
lrwxrwxrwx 1 root root 22 Sep 23 05:21 brcmfmac43455-sdio.amlogic,sm1.txt -> brcmfmac43455-sdio.txt
-rw-rw-r-- 1 root root 472K Sep 23 05:21 brcmfmac43455-sdio.bin
-rw-rw-r-- 1 root root 14K Sep 23 05:21 brcmfmac43455-sdio.clm_blob
lrwxrwxrwx 1 root root 22 Sep 23 05:21 brcmfmac43455-sdio.firefly,rk3566-roc-pc.bin -> brcmfmac43455-sdio.bin
lrwxrwxrwx 1 root root 22 Sep 23 05:21 brcmfmac43455-sdio.firefly,rk3566-roc-pc.txt -> brcmfmac43455-sdio.txt
lrwxrwxrwx 1 root root 22 Sep 23 05:21 brcmfmac43455-sdio.radxa,zero2.bin -> brcmfmac43455-sdio.bin
lrwxrwxrwx 1 root root 22 Sep 23 05:21 brcmfmac43455-sdio.radxa,zero2.txt -> brcmfmac43455-sdio.txt
lrwxrwxrwx 1 root root 22 Sep 23 05:21 brcmfmac43455-sdio.raspberrypi,3-model-b-plus.bin -> brcmfmac43455-sdio.bin
lrwxrwxrwx 1 root root 22 Sep 23 05:21 brcmfmac43455-sdio.raspberrypi,4-compute-module.bin -> brcmfmac43455-sdio.bin
-rw-rw-r-- 1 root root 1.9K Sep 23 05:21 brcmfmac43455-sdio.raspberrypi,4-compute-module.txt
lrwxrwxrwx 1 root root 22 Sep 23 05:21 brcmfmac43455-sdio.raspberrypi,4-model-b.bin -> brcmfmac43455-sdio.bin
-rw-rw-r-- 1 root root 1.9K Sep 23 05:21 brcmfmac43455-sdio.raspberrypi,4-model-b.txt
lrwxrwxrwx 1 root root 22 Sep 23 05:21 brcmfmac43455-sdio.raspberrypi,5-model-b.bin -> brcmfmac43455-sdio.bin
lrwxrwxrwx 1 root root 27 Sep 23 05:21 brcmfmac43455-sdio.raspberrypi,5-model-b.clm_blob -> brcmfmac43455-sdio.clm_blob
lrwxrwxrwx 1 root root 22 Sep 23 05:21 brcmfmac43455-sdio.raspberrypi,5-model-b.txt -> brcmfmac43455-sdio.txt
-rw-rw-r-- 1 root root 1.7K Sep 23 05:21 brcmfmac43455-sdio.txt
So a symlink should solve it. For Bluetooth we see which names it is looking for. Let’s create the more generic one:
sudo ln -s BCM4345C0_003.001.025.0162.0000_Generic_UART_37_4MHz_wlbga_ref_iLNA_iTR_eLG.hcd /lib/firmware/brcm/BCM4345C0.hcd
Just weird that this was no problem earlier. There is no recent change in the device tree, and I do not see something related in driver commits either: Making sure you're not a bot!
Here is the part for (WiFi) firmware detection: Making sure you're not a bot!
BRCMF_FW_CLM_DEF(43455, "brcmfmac43455-sdio");
...
BRCMF_FW_ENTRY(BRCM_CC_4345_CHIP_ID, 0xFFFFFDC0, 43455),
BRCMF_FW_ENTRY(BRCM_CC_43454_CHIP_ID, 0x00000040, 43455),
...
struct brcmf_fw_name fwnames[] = {
{ ".bin", bus->sdiodev->fw_name },
{ ".txt", bus->sdiodev->nvram_name },
{ ".clm_blob", bus->sdiodev->clm_name },
};
So that existing /lib/firmware/brcm/brcmfmac43455-sdio.* files should be used. But maybe this no txcap_blob available is not related to the 3 common files and probably not even relevant.
EDIT: Other report about using the ROCK 4C+ as WiFi AP: AP on Rock Pi 4C+
Not sure yet whether this means that WiFi in general works there, just AP mode not, or whether AP does not work because WiFi itself does not.
, but I had to reinstall the image on the microSD (perhaps I had done something wrong during the configuration phase)