At a guess,, the name of the firmware is not right,
you do know, I hope, that all wifi has to load firmware to work?
You could check,,, dmesg |grep -i firmware
It is not entirely clear, I think these are correct names
/lib/firmware/brcm/brcmfmac43456-sdio.{bin clm.blob pine64,pinebookpro.txt}
The newer pbp have a different chip, if it is less than 1 y old?
Anyway, the name is too long, has to renamed or linked
as to sd boot failure....
If you don't care about sleep, tow-boot, the binaries are hidden within the tgz, do a normal dd
hidden within binaries/ (v5)
-rw-rw-r-- 1 d d 168816 Oct 27 2020 idbloader.img (offset 64 sectors,,, seek=64)
-rw-rw-r-- 1 d d 1388952 Oct 27 2020 spi.img --->don't use this, for spi
-rw-rw-r-- 1 d d 995736 Oct 27 2020 u-boot.itb (offset 8M,,, bs=1M seek=8)
you do know, I hope, that all wifi has to load firmware to work?
You could check,,, dmesg |grep -i firmware
It is not entirely clear, I think these are correct names
/lib/firmware/brcm/brcmfmac43456-sdio.{bin clm.blob pine64,pinebookpro.txt}
The newer pbp have a different chip, if it is less than 1 y old?
Anyway, the name is too long, has to renamed or linked
as to sd boot failure....
If you don't care about sleep, tow-boot, the binaries are hidden within the tgz, do a normal dd
hidden within binaries/ (v5)
-rw-rw-r-- 1 d d 168816 Oct 27 2020 idbloader.img (offset 64 sectors,,, seek=64)
-rw-rw-r-- 1 d d 1388952 Oct 27 2020 spi.img --->don't use this, for spi
-rw-rw-r-- 1 d d 995736 Oct 27 2020 u-boot.itb (offset 8M,,, bs=1M seek=8)