<div dir="ltr"><div>the timeout problem is from the noflow syntax. The problem cause is the generation of the bluetooth BDADDR (IP) to be used<br><br></div>I rebooted the machine and tried the following :<br><div><br>this syntax causes timeout:<br>hciattach /dev/ttyAMA0 bcm43xx 921600 noflow -<br><br>this syntax binds well, inspired by Raspbian:<br>hciattach /dev/ttyAMA0 bcm43xx 3000000 flow - b8:27:eb:c2:e4:41<br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 17, 2017 at 9:06 AM, Sherif Omran <span dir="ltr"><<a href="mailto:sherifomran2000@gmail.com" target="_blank">sherifomran2000@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>i got it now working .. <br></div>remove the -n in the hciattach command and use 3000000 as speed. This is what raspbian is using.<br></div>but this means that there are missing drivers that were needed .. <br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 17, 2017 at 8:14 AM, Sherif Omran <span dir="ltr"><<a href="mailto:sherifomran2000@gmail.com" target="_blank">sherifomran2000@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>hi Dengke,<br><br></div>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 <br></div>I copied the following files from raspbian<br><br>copied from raspbian <br>/lib/firmware/*<br>/lib/firmware/br*/*<br>usr/bin/hciattach -> this is a newer version<br>usr/bin/hcitool     <br><br>I gave the hciattach command -><br>   bcm43xx_ini<br>   flash firmware /lib/firmware/BCM32320A1.hcd<br>   Set Controller UART speed to 921600 bit/s<br>   Device Setup Complete<br><br>Ctrl+c<br><br><br></div>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<br></div>since then i get now time out when i give hciattach again ..<br><br></div>but when i start the raspbian, it works normally, it seems for me there is something else to do to initialize it now.<br><br></div>regards,<br></div>Sherif<br></div><div class="m_-6585438958413313471HOEnZb"><div class="m_-6585438958413313471h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 16, 2017 at 11:29 AM, Sherif Omran <span dir="ltr"><<a href="mailto:sherifomran2000@gmail.com" target="_blank">sherifomran2000@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>I tried to duplicate at the least the same error and followed what the colleague mentioned in the link<br><br></div>here is my configuration in local.conf<br><br>CORE_IMAGE_EXTRA_INSTALL += " rsync "<br>#sensorhub -> still need to be downloaded<br>IMAGE_INSTALL_append += "nodejs nodejs-npm bluez5 networkmanager linux-firmware-bcm43430"<br># config systemd" -> no config found. Lets use system V for now<br>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"<br>DISTRO_FEATURES_append += " bluez5 bluetooth wifi systemd"<br><br><br><br><br></div>my results so far: the folder etc/firmware is missing.<br><br></div><div>hciattach - n /dev .... <br></div><div>bcm43xx_init<br></div><div>can not open directory '/etc/firmware' no file or directory<br><br><br></div></div><div class="m_-6585438958413313471m_2579498067636292709HOEnZb"><div class="m_-6585438958413313471m_2579498067636292709h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 15, 2017 at 7:00 AM, Dengke Du <span dir="ltr"><<a href="mailto:dengke.du@windriver.com" target="_blank">dengke.du@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span>
<br>
<br>
<div class="m_-6585438958413313471m_2579498067636292709m_-3172265992085223685m_7546131904444986684moz-cite-prefix">On 2017年12月15日 13:55, Sherif Omran
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>when i do hciattach, i get initialization timeout.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br></span>
This is a bug for initialization timeout:<br>
<br>
   <a class="m_-6585438958413313471m_2579498067636292709m_-3172265992085223685m_7546131904444986684moz-txt-link-freetext" href="https://github.com/agherzan/meta-raspberrypi/issues/148" target="_blank">https://github.com/agherzan/me<wbr>ta-raspberrypi/issues/148</a><br>
<br>
Sometimes it works, sometimes it would not work. Still need research
on it.<span><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>could it be a branch related? <br>
</div>
</div>
</div>
</blockquote>
<br></span>
Not branch related.<span><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>I am using the morty branch<br>
</div>
meta-yocto-bsp: morty<br>
</div>
meta-raspberrypi: morty<br>
<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Dec 15, 2017 at 6:30 AM, Dengke
Du <span dir="ltr"><<a href="mailto:dengke.du@windriver.com" target="_blank">dengke.du@windriver.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>You should attach the bluez stack with the raspberry
firmware bcm43xx:</p>
<p>Â Â Â hciattact -n /dev/ttyAMA0 bcm43xx 921600 noflow -</p>
<p>or if you use systemd:</p>
<p>Â Â Â systemctl restart brcm43438.service</p>
<p>Now you can see the the device:</p>
<p>Â Â Â rfkill list all</p>
<p>Enable it:</p>
<p>Â Â Â rfkill unblock all</p>
<p>Â Â Â hciconfig hci0 up</p>
<p>Checking the bluetooth:</p>
<p>Â Â Â hciconfig -a<br>
</p>
<div>
<div class="m_-6585438958413313471m_2579498067636292709m_-3172265992085223685m_7546131904444986684h5"> <br>
<div class="m_-6585438958413313471m_2579498067636292709m_-3172265992085223685m_7546131904444986684m_5036739186136312151moz-cite-prefix">On
2017年12月15日 12:43, Sherif Omran wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>hello<br>
<br>
</div>
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.<br>
<br>
</div>
Any body had similar issue and got it to solve?<br>
</div>
<br>
<fieldset class="m_-6585438958413313471m_2579498067636292709m_-3172265992085223685m_7546131904444986684m_5036739186136312151mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</span></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>