i got it now working ..
remove the -n in the hciattach command and use 300 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
wrote:
> hi Dengke,
>
> i could go one step further, as i told
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 gav
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-firm
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 bran
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 hc
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
