[yocto] Bluetooth

[Sherif Omran]

I tried to duplicate at the least the same error and followed what the
colleague mentioned in the link

here is my configuration in local.conf

CORE_IMAGE_EXTRA_INSTALL += " rsync "
#sensorhub -> still need to be downloaded
IMAGE_INSTALL_append += "nodejs nodejs-npm bluez5 networkmanager
linux-firmware-bcm43430"
# config systemd" -> no config found. Lets use system V for now
IMAGE_INSTALL_append += " crda i2c-tools hostapd linux-firmware-bcm43430
linux-firmware-ralink linux-firmware-rtl8192ce linux-firmware-rtl8192cu
linux-firmware-rtl8192su wireless-tools dhcp-client iw wpa-supplicant"
DISTRO_FEATURES_append += " bluez5 bluetooth wifi systemd"




my results so far: the folder etc/firmware is missing.

hciattach  - n /dev ....
bcm43xx_init
can not open directory '/etc/firmware' no file or directory



On Fri, Dec 15, 2017 at 7:00 AM, Dengke Du <dengke.du at windriver.com> wrote:

>
>
> On 2017年12月15日 13:55, Sherif Omran wrote:
>
> when i do hciattach, i get initialization timeout.
>
>
> This is a bug for initialization timeout:
>
>     https://github.com/agherzan/meta-raspberrypi/issues/148
>
> Sometimes it works, sometimes it would not work. Still need research on it.
>
> could it be a branch related?
>
>
> Not branch related.
>
> I am using the morty branch
> meta-yocto-bsp: morty
> meta-raspberrypi: morty
>
>
> On Fri, Dec 15, 2017 at 6:30 AM, Dengke Du <dengke.du at windriver.com>
> wrote:
>
>> You should attach the bluez stack with the raspberry firmware bcm43xx:
>>
>>     hciattact -n /dev/ttyAMA0 bcm43xx 921600 noflow -
>>
>> or if you use systemd:
>>
>>     systemctl restart brcm43438.service
>>
>> Now you can see the the device:
>>
>>     rfkill list all
>>
>> Enable it:
>>
>>     rfkill unblock all
>>
>>     hciconfig hci0 up
>>
>> Checking the bluetooth:
>>
>>     hciconfig -a
>>
>> On 2017年12月15日 12:43, Sherif Omran wrote:
>>
>> hello
>>
>> i ve been strugggeling since couple of days with raspberry pi 0 board and
>> can not figure out how to enable the chip, whether it is enabled by default
>> or it needs some intervention. I generated the rpi-basic-image and tested
>> with the hiconfigure -a but the chip is not detected.
>>
>> Any body had similar issue and got it to solve?
>>
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20171216/c95be062/attachment.html>