[yocto] Bluetooth

[Sherif Omran]

i got it now working ..
remove the -n in the hciattach command and use 3000000 as speed. This is
what raspbian is using.
but this means that there are missing drivers that were needed ..

On Sun, Dec 17, 2017 at 8:14 AM, Sherif Omran <sherifomran2000 at gmail.com>
wrote:

> hi Dengke,
>
> i could go one step further, as i told you there is a firmware that has to
> be written to the chip to change the speed
> I copied the following files from raspbian
>
> copied from raspbian
> /lib/firmware/*
> /lib/firmware/br*/*
> usr/bin/hciattach  -> this is a newer version
> usr/bin/hcitool
>
> I gave the  hciattach command ->
>     bcm43xx_ini
>     flash firmware /lib/firmware/BCM32320A1.hcd
>     Set Controller UART speed to 921600 bit/s
>     Device Setup Complete
>
> Ctrl+c
>
>
> as you see, i got device setup complete but there was no feedback from the
> command and i was not on the command line, so i made ctrl+c
> since then i get now time out when i give hciattach again ..
>
> but when i start the raspbian, it works normally, it seems for me there is
> something else to do to initialize it now.
>
> regards,
> Sherif
>
> On Sat, Dec 16, 2017 at 11:29 AM, Sherif Omran <sherifomran2000 at gmail.com>
> wrote:
>
>> 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/20171217/1e134fb8/attachment.html>