I am having trouble getting Bluetooth running. Sometimes it boots, then it
does not, depending on the kernel version
On 4.9 it will run all the time:
=====================
hci0: Type: Primary Bus: UART
BD Address: 98:84:E3:DE:06:6C ACL MTU: 1021:6 SCO MTU: 180:4
UP RUNNING PSCAN
RX bytes:1284 acl:0 sco:0 events:51 errors:0
TX bytes:2727 acl:0 sco:0 commands:51 errors:0
Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'woodyamsterdam0'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.1 (0x7) Revision: 0x0
LMP Version: 4.1 (0x7) Subversion: 0xac7c
Manufacturer: Texas Instruments Inc. (13)
=====================
=====================
model:[TI_AM335x_BeagleBone_Black_Wireless]
dogtag:[BeagleBoard.org Debian Image 2017-10-10]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2018.01-rc3-00002-gb33224]
kernel:[4.9.76-ti-r91]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20180104.0-0rcnee1~stretch+20180104]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~stretch+20180104]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
dmesg | grep pinctrl-single
[ 1.459498] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size
568
END
=====================
on 4.4 it runs from time to time:
=====================
hci0: Type: Primary Bus: UART
BD Address: 98:84:E3:DE:06:6C ACL MTU: 1021:6 SCO MTU: 180:4
UP RUNNING PSCAN
RX bytes:1272 acl:0 sco:0 events:49 errors:0
TX bytes:1814 acl:0 sco:0 commands:49 errors:0
Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'woodyamsterdam0'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.1 (0x7) Revision: 0x0
LMP Version: 4.1 (0x7) Subversion: 0xac7c
Manufacturer: Texas Instruments Inc. (13)
=====================
On 4.14 I could not get it running.
I wondered if I by mistake have taken out the communication to the onboard
wl connection, as I noticed that, when it is working, it seems to use UART
communication. Are there any pins I should avoid?
These are the current configs on 4.4 and 4.14
=====================
git:/opt/scripts/:[b372df3221bb67a9a09c6b89df5110ca32a9e482]
eeprom:[A335BNLTBWA51712EW005264]
model:[TI_AM335x_BeagleBone_Black_Wireless]
dogtag:[BeagleBoard.org Debian Image 2017-10-10]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2018.01-rc3-00002-gb33224]
kernel:[4.4.110-ti-r142]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20180104.0-0rcnee1~stretch+20180104]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~stretch+20180104]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
dmesg | grep pinctrl-single
[ 1.220116] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size
568
END
=====================
=====================
model:[TI_AM335x_BeagleBone_Black_Wireless]
dogtag:[BeagleBoard.org Debian Image 2017-10-10]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2018.01-rc3-00002-gb33224]
kernel:[4.14.13-ti-r25]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20180104.0-0rcnee1~stretch+20180104]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~stretch+20180104]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
=====================
If I connect a USB bluetooth connector, I can see it with bluetoothctl or
hciconfig on all kernels:
on 4.9:
~# hciconfig -a
=====================
hci1: Type: Primary Bus: USB
BD Address: 00:15:83:6A:2F:C3 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:646 acl:0 sco:0 events:42 errors:0
TX bytes:2169 acl:0 sco:0 commands:41 errors:0
Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'woodyamsterdam0 #2'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.0 (0x6) Revision: 0x1d86
LMP Version: 4.0 (0x6) Subversion: 0x1d86
Manufacturer: Cambridge Silicon Radio (10)
=====================
on 4.14:
=====================
hci0: Type: Primary Bus: USB
BD Address: 00:15:83:6A:2F:C3 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:658 acl:0 sco:0 events:44 errors:0
TX bytes:2664 acl:0 sco:0 commands:43 errors:0
Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'woodyamsterdam0'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.0 (0x6) Revision: 0x1d86
LMP Version: 4.0 (0x6) Subversion: 0x1d86
Manufacturer: Cambridge Silicon Radio (10)
=====================
on 4.4:
=====================
hci0: Type: Primary Bus: USB
BD Address: 00:15:83:6A:2F:C3 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1232 acl:0 sco:0 events:74 errors:0
TX bytes:2858 acl:0 sco:0 commands:74 errors:0
Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'woodyamsterdam0 #1'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.0 (0x6) Revision: 0x1d86
LMP Version: 4.0 (0x6) Subversion: 0x1d86
Manufacturer: Cambridge Silicon Radio (10)
=====================
Kind Regards,
Johan Henselmans
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/d63ebff3-e0e2-49d5-ac36-b3a9fb448877%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
