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
#!/bin/bash
if [ "$(cat /proc/device-tree/aliases/uart0)" = "$(cat /proc/device-tree/aliases/serial1)" ] ; then
if [ "$(wc -c /proc/device-tree/soc/gpio@7e200000/uart0_pins/brcm\,pins | cut -f 1 -d ' ')" = "16" ] ; then
/usr/bin/hciattach /dev/serial1 bcm43xx 3000000 flow -
else
/usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow -
fi
else
/usr/bin/hciattach /dev/serial1 bcm43xx 460800 noflow -
fi
Starting btuart or hciattach:
/usr/bin/btuart: line 3: warning: command substitution: ignored null byte in input
/usr/bin/btuart: line 3: warning: command substitution: ignored null byte in input
bcm43xx_init
Cannot open directory '/etc/firmware': No such file or directory
Patch not found, continue anyway
Set Controller UART speed to 3000000 bit/s
Device setup complete
The package https://github.com/Re4son/re4son-kernel-builder/blob/build-4.14.n/repo/pi-bluetooth_0.1.4%2Bre4son_all.deb provides the btuart bash script.
This script relies on hciattach
Starting
btuart
or hciattach:(seems to search firmware in /etc/firmware)
The dmesg output after starting
btuart
And hcitool:
fix:
The Bluez version used by Kali with your kernel relies on
btattach
After disabling the
hciuart
service (and reboot), this call allows to create a working hci device:Respective
dmesg
output... and
hcitool
outputAdditionally
btattach
deploys thehci_uart
module if needed, this didn't work for me withciattach
.The text was updated successfully, but these errors were encountered: