You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I am working with Yocto on a Raspberry Pi 3 Model B V1.2, using the scarthgap branch. I am encountering issues with getting the Broadcom Wi-Fi and Bluetooth hardware to work properly. Despite setting up the necessary drivers and firmware, neither Wi-Fi nor Bluetooth is being detected or initialized. Below are the details of my configuration, the troubleshooting steps I’ve taken, and the results observed. Configuration and Environment
Verified that the required firmware files (brcmfmac43430-sdio.bin and brcmfmac43455-sdio.bin) are present in /lib/firmware/brcm/. The brcmfmac and brcmutil drivers are visible on the system. But are not loaded automatically. Below is my dmesg output: and my lsmod output dmesg.txt lsmod.txt
When loaded manually with modprobe brcmfmac and modprobe brcmutil, they do not automatically detect or initialize a Wi-Fi interface. Running ip link show reveals that wlan0 is not created.
here is my dmesg after attempting to manually load the drivers:
There is no further output indicating Wi-Fi initialization or issues. This is true even after enabling the SDIO bus support for FullMAC drivers in the kernel configuration.
Bluetooth Behavior:
Bluetooth is also non-functional. Running hciconfig -a shows no BD address (all zeros).
The Bluetooth-related firmware packages are installed, but no hci0 device is created or recognized, and Bluetooth tools (hciconfig) do not detect the hardware.
I also attempted to add dtoverlay=sdio in /boot/config.txt to force SDIO initialization, but this did not help. The SDIO device remains undetected on both Wi-Fi and Bluetooth.
Questions and Support Needed Could you provide guidance on the following points?
Driver Initialization: Are there known dependencies or configurations needed to ensure that brcmfmac and brcmutil automatically initialize wlan0 and detect Bluetooth ?
Bluetooth Setup: Are additional configurations required to properly initialize Bluetooth hardware and prevent the BD address from being set to all zeros?
Any help or insights would be greatly appreciated, as this is my first time working with Yocto on the Raspberry Pi, and I am encountering challenges in detecting and initializing both Wi-Fi and Bluetooth.
Thanks in advance
JosephMS,
The text was updated successfully, but these errors were encountered:
In the same situation. I can add a little more info. I am using the rpi 4.
linux-firmware-rpidistro installs the needed firmware to /lib/firmware but the symbolic links are broken again. There is/was a patch file for this but it does not look to be working (not sure, need to look into it) brcmfmac will try to load it and fail to find it. You can fix that by adding the needed symbolic link to cyfmac43455-sdio-standard.bin.
brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin -> cypress/cyfmac43455-sdio.bin
# But cypress/cyfmac43455-sdio.bin does not exist.
brcmfmac needs brcmfmac-wcc, brcmfmac-wcc is a kernel module but does now show up in menuconfig (I don't know why) but it will be built if brcmfmac is built. Add these two lines to your local.conf:
You may also encounter a regulatory database loading error, you need to ensure that the needed files get added into the image, add this line to your local.conf:
IMAGE_INSTALL:append = " wireless-regdb-static"
You should now see wlan0 under ifconfig -a. Unfortunately, I have not been able to get NetworkManager to work, and don't have and time to investigate further.
Description:
I am working with Yocto on a Raspberry Pi 3 Model B V1.2, using the scarthgap branch. I am encountering issues with getting the Broadcom Wi-Fi and Bluetooth hardware to work properly. Despite setting up the necessary drivers and firmware, neither Wi-Fi nor Bluetooth is being detected or initialized. Below are the details of my configuration, the troubleshooting steps I’ve taken, and the results observed.
Configuration and Environment
here is my local.conf
Other Firmware/Driver Packages: In MACHINE_EXTRA_RRECOMMENDS, includes the following packages in raspberrypi3.conf:
Observations and Steps Taken
Driver Loading:
Verified that the required firmware files (brcmfmac43430-sdio.bin and brcmfmac43455-sdio.bin) are present in /lib/firmware/brcm/. The brcmfmac and brcmutil drivers are visible on the system. But are not loaded automatically. Below is my dmesg output: and my lsmod output
dmesg.txt
lsmod.txt
When loaded manually with modprobe brcmfmac and modprobe brcmutil, they do not automatically detect or initialize a Wi-Fi interface. Running ip link show reveals that wlan0 is not created.
here is my dmesg after attempting to manually load the drivers:
There is no further output indicating Wi-Fi initialization or issues. This is true even after enabling the SDIO bus support for FullMAC drivers in the kernel configuration.
Bluetooth Behavior:
Bluetooth is also non-functional. Running hciconfig -a shows no BD address (all zeros).
The Bluetooth-related firmware packages are installed, but no hci0 device is created or recognized, and Bluetooth tools (hciconfig) do not detect the hardware.
I also attempted to add dtoverlay=sdio in /boot/config.txt to force SDIO initialization, but this did not help. The SDIO device remains undetected on both Wi-Fi and Bluetooth.
Questions and Support Needed
Could you provide guidance on the following points?
Driver Initialization: Are there known dependencies or configurations needed to ensure that brcmfmac and brcmutil automatically initialize wlan0 and detect Bluetooth ?
Bluetooth Setup: Are additional configurations required to properly initialize Bluetooth hardware and prevent the BD address from being set to all zeros?
Any help or insights would be greatly appreciated, as this is my first time working with Yocto on the Raspberry Pi, and I am encountering challenges in detecting and initializing both Wi-Fi and Bluetooth.
Thanks in advance
JosephMS,
The text was updated successfully, but these errors were encountered: