Mainstream Linux BT and BLE - Beacon EmbeddedWorks

Create Account

Create Account

You are here: >> >> >>

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

Forums
Search Forum
Advanced SearchTopicsPosts

Prev Go to previous topic

Go to next topic

Last Post 01 Dec 2017 06:38 PM by Adam Ford

Mainstream Linux BT and BLE

6 Replies

Sort:


You are not authorized to post a reply.

Author

Messages

William Deninger

New Member
Posts:22

02 Nov 2017 05:17 PM
Hello all, Has anyone successfully been able to establish a Bluetooth device under the Mainstream Linux 4.4.x kernel? In particular, I'm targeting BLE, but need to get standard serial BT working first. The process seems quite different than that under 3.0.101, so I could have missed some important steps. Ultimately, I cant seem to find the device. Is there required a modification to the kernel device tree or pins file? Is btwlink.ko missing or is it no longer required under 4.4? Attached are a few log outputs that may provide clues. Suggestions?? -William bt-adapter -l No adapters found lsmod Module Size Used by hci_uart 21284 1 btusb 27597 0 btrtl 3698 1 btusb btbcm 6053 1 btusb btintel 6220 1 btusb bnep 10386 2 arc4 1785 2 wl12xx 52865 0 wlcore 165213 1 wl12xx mac80211 490896 2 wl12xx,wlcore cfg80211 415902 2 mac80211,wlcore bq27xxx_battery 8214 0 snd_soc_omap_twl4030 6636 0 evdev 11569 0 joydev 9208 0 cpufreq_dt 4219 0 leds_gpio 3355 0 led_class 3721 1 leds_gpio gpio_keys 8217 0 thermal_sys 45520 1 cpufreq_dt pwm_omap_dmtimer 3692 1 hwmon 2671 1 thermal_sys pwm_bl 3977 0 w1_bq27000 1184 0 snd_soc_omap_mcbsp 16621 2 snd_soc_omap 3000 1 snd_soc_omap_mcbsp snd_pcm_dmaengine 3083 1 snd_soc_omap omap_wdt 3649 0 omap_hdq 6005 0 wlcore_sdio 5922 0 wire 23391 2 omap_hdq,w1_bq27000 cn 4434 1 w lsmod Module Size Used by hci_uart 21284 1 btusb 27597 0 btrtl 3698 1 btusb btbcm 6053 1 btusb btintel 6220 1 btusb bnep 10386 2 arc4 1785 2 wl12xx 52865 0 wlcore 165213 1 wl12xx mac80211 490896 2 wl12xx,wlcore cfg80211 415902 2 mac80211,wlcore bq27xxx_battery 8214 0 snd_soc_omap_twl4030 6636 0 evdev 11569 0 joydev 9208 0 cpufreq_dt 4219 0 leds_gpio 3355 0 led_class 3721 1 leds_gpio gpio_keys 8217 0 thermal_sys 45520 1 cpufreq_dt pwm_omap_dmtimer 3692 1 hwmon 2671 1 thermal_sys pwm_bl 3977 0 w1_bq27000 1184 0 snd_soc_omap_mcbsp 16621 2 snd_soc_omap 3000 1 snd_soc_omap_mcbsp snd_pcm_dmaengine 3083 1 snd_soc_omap omap_wdt 3649 0 omap_hdq 6005 0 wlcore_sdio 5922 0 wire 23391 2 omap_hdq,w1_bq27000 cn 4434 1 wire twl4030_wdt 2098 0 snd_soc_twl4030 41291 1 snd_soc_core 119530 4 snd_soc_omap_twl4030,snd_soc_omap,snd_soc_omap_mcbsp,snd_soc_twl4030 snd_pcm 75114 5 snd_soc_core,snd_soc_omap,snd_soc_omap_mcbsp,snd_pcm_dmaengine,snd_soc_t0 snd_timer 18744 1 snd_pcm snd 48038 3 snd_soc_core,snd_timer,snd_pcm soundcore 5104 1 snd pwm_twl_led 4103 0 twl4030_pwrbutton 2008 0 pwm_twl 3993 0 ohci_omap3 2346 0 ohci_hcd 28315 1 ohci_omap3 tsc2004 1695 0 tsc200x_core 6021 1 tsc2004 ire twl4030_wdt 2098 0 snd_soc_twl4030 41291 1 snd_soc_core 119530 4 snd_soc_omap_twl4030,snd_soc_omap,snd_soc_omap_mcbsp,snd_soc_twl4030 snd_pcm 75114 5 snd_soc_core,snd_soc_omap,snd_soc_omap_mcbsp,snd_pcm_dmaengine,snd_soc_t0 snd_timer 18744 1 snd_pcm snd 48038 3 snd_soc_core,snd_timer,snd_pcm soundcore 5104 1 snd pwm_twl_led 4103 0 twl4030_pwrbutton 2008 0 pwm_twl 3993 0 ohci_omap3 2346 0 ohci_hcd 28315 1 ohci_omap3 tsc2004 1695 0 tsc200x_core 6021 1 tsc2004 grep -i blue /var/log/messages Jan 1 00:59:16 buildroot user.info kernel: [ 0.565246] Bluetooth: Core ver 2.21 Jan 1 00:59:16 buildroot user.info kernel: [ 0.565368] Bluetooth: HCI device and connection manager d Jan 1 00:59:16 buildroot user.info kernel: [ 0.565399] Bluetooth: HCI socket layer initialized Jan 1 00:59:16 buildroot user.info kernel: [ 0.565399] Bluetooth: L2CAP socket layer initialized Jan 1 00:59:16 buildroot user.info kernel: [ 0.565490] Bluetooth: SCO socket layer initialized Jan 1 01:52:59 buildroot daemon.info bluetoothd[302]: Bluetooth daemon 5.46 Jan 1 01:52:59 buildroot daemon.info bluetoothd[302]: Starting SDP server Jan 1 01:52:59 buildroot user.info kernel: [ 3230.442291] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Jan 1 01:52:59 buildroot user.info kernel: [ 3230.456756] Bluetooth: BNEP filters: protocol multicast Jan 1 01:52:59 buildroot user.info kernel: [ 3230.462341] Bluetooth: BNEP socket layer initialized Jan 1 01:52:59 buildroot daemon.err bluetoothd[302]: Failed to open RFKILL control device Jan 1 01:52:59 buildroot daemon.info bluetoothd[302]: Bluetooth management interface 1.10 initialized Jan 1 01:57:59 buildroot user.info kernel: [ 3530.578674] Bluetooth: HCI UART driver ver 2.3 Jan 1 01:57:59 buildroot user.info kernel: [ 3530.583404] Bluetooth: HCI UART protocol H4 registered Jan 1 01:57:59 buildroot user.info kernel: [ 3530.598358] Bluetooth: HCI UART protocol BCSP registered Jan 1 01:57:59 buildroot user.info kernel: [ 3530.604003] Bluetooth: HCI UART protocol LL registered Jan 1 01:57:59 buildroot user.info kernel: [ 3530.610595] Bluetooth: HCI UART protocol Three-wire (H5) d Jan 1 01:58:01 buildroot user.err kernel: [ 3532.676208] Bluetooth: hci0 command 0x1003 tx timeout Jan 1 01:58:03 buildroot user.err kernel: [ 3534.676208] Bluetooth: hci0 command 0x1001 tx timeout Jan 1 01:58:05 buildroot user.err kernel: [ 3536.676208] Bluetooth: hci0 command 0x1009 tx timeout

Adam Ford

Advanced Member
Posts:794

03 Nov 2017 07:31 AM
There are two patches that were pushed to the kernel later than 4.4 that are intended to support Bluetooth. The 4.4 beta didn't test Bluetooth which is part of the reason it's considered beta. If you look at these two patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/mach-omap2/pdata-quirks.c?h=v4.14-rc7&id=485fa1261f780e8a13d0b25a24673947e6c50953 and https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/mach-omap2/pdata-quirks.c?h=v4.14-rc7&id=a3ac350793d90d1da631c8beeee9352387974ed5 You should be able to add the background necessary for Bluetooth. You will then need to enable the shared transport driver in the kernel under Device Drivers -> Misc devices -> Texas Instrucments shared transport line discipline The BT Wilink driver is iunder: Networking support -> Bluetooth subsystem support -> Bluetooth device drivers -> Texas Instruments WiLink 7 driver Once you have those enabled, you'll need the UIM tool. UIM is located at Target Packages->Hardware Handling-> ti-uim BlueZ is offered in Buildroot. There are a couple options available under Target Packages->Networking Applications. When I did my preliminary testing to see if it worked, I used BlueZ 5 to pair the Torpedo with my cell phone, but I didn't move forward enough to know what/how to do further testing. If you want to try BlueZ 4, we have a document posted for our older BSP that might be useful: http://support.logicpd.co...talid=0&EntryId=2976 Only the Torpedo + Wireless -32 SOM supports BLE from Logic PD. In the stock BSP, there is a BTS file that needs to load. You'll want to copy those files o the firmware/ti-connectivity folder on your new image. When you boot, you'll need to modprobe st_drv then modprobe btwilink. The Bluetooth document I referenced above gives some instructions on how to use UIM, but we haven't fully tested it, so use at your own risk. adam

William Deninger

New Member
Posts:22

17 Nov 2017 05:35 PM
Hello, After several full rebuild attempts of buildroot using 2011.08-rc3 and 2011.11-rc2, I still have had no success at BT functionality. The two patches to which you referred: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/mach-omap2/pdata-quirks.c?h=v4.14-rc7&id=485fa1261f780e8a13d0b25a24673947e6c50953 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/mach-omap2/pdata-quirks.c?h=v4.14-rc7&id=a3ac350793d90d1da631c8beeee9352387974ed5 contain a bit of duplication that result in compiler errors. However, I resolved the conflicts into one patch: diff --git a/arch/arm/mach-omap2/pdata-quirks.c b/arch/arm/mach-omap2/pdata-quirks.c index 1dfe346..cd9775a 100644 --- a/arch/arm/mach-omap2/pdata-quirks.c +++ b/arch/arm/mach-omap2/pdata-quirks.c @@ -153,6 +153,21 @@ static struct platform_device wl18xx_device = { } }; +static struct ti_st_plat_data wilink7_pdata = { + .nshutdown_gpio = 162, + .dev_name = "/dev/ttyO1", + .flow_cntrl = 1, + .baud_rate = 300000, +}; + +static struct platform_device wl128x_device = { + .name = "kim", + .id = -1, + .dev = { + .platform_data = &wilink7_pdata, + } +}; + static struct platform_device btwilink_device = { .name = "btwilink", .id = -1, @@ -279,6 +294,13 @@ static void __init omap3_tao3530_legacy_init(void) hsmmc2_internal_input_clk(); } +static void __init omap3_logicpd_torpedo_init(void) +{ + omap3_gpio126_127_129(); + platform_device_register(&wl128x_device); + platform_device_register(&btwilink_device); +} + /* omap3pandora legacy devices */ #define PANDORA_WIFI_IRQ_GPIO 21 #define PANDORA_WIFI_NRESET_GPIO 23 @@ -529,7 +551,7 @@ static struct pdata_init pdata_quirks[] __initdata = { { "nokia,omap3-n950", hsmmc2_internal_input_clk, }, { "isee,omap3-igep0020-rev-f", omap3_igep0020_rev_f_legacy_init, }, { "isee,omap3-igep0030-rev-g", omap3_igep0030_rev_g_legacy_init, }, - { "logicpd,dm3730-torpedo-devkit", omap3_gpio126_127_129, }, + { "logicpd,dm3730-torpedo-devkit", omap3_logicpd_torpedo_init, }, { "logicpd,dm3730-som-lv-devkit", omap3_som_lv_init, }, { "ti,omap3-evm-37xx", omap3_evm_legacy_init, }, { "ti,am3517-evm", am3517_evm_legacy_init, }, Upon boot, a number of BT kernel errors appear in the /var/log/messages shown below. Jan 2 01:29:08 buildroot user.info kernel: [ 196.430419] Bluetooth: Core ver 2.21 Jan 2 01:29:08 buildroot user.info kernel: [ 196.456146] NET: Registered protocol family 31 Jan 2 01:29:08 buildroot user.info kernel: [ 196.460876] Bluetooth: HCI device and connection manager initialized Jan 2 01:29:08 buildroot user.info kernel: [ 196.470214] Bluetooth: HCI socket layer initialized Jan 2 01:29:08 buildroot user.info kernel: [ 196.475402] Bluetooth: L2CAP socket layer initialized Jan 2 01:29:08 buildroot user.info kernel: [ 196.481994] Bluetooth: SCO socket layer initialized Jan 2 01:29:08 buildroot daemon.info bluetoothd[197]: Bluetooth daemon 5.47 Jan 2 01:29:08 buildroot daemon.err bluetoothd[197]: GLib: g_error_new_literal: assertion 'message != NULL' failed Jan 2 01:29:25 buildroot user.info kernel: [ 213.448150] (stk) :sysfs entries created Jan 2 01:29:27 buildroot daemon.info bluetoothd[203]: Bluetooth daemon 5.47 Jan 2 01:29:27 buildroot daemon.err bluetoothd[203]: GLib: g_error_new_literal: assertion 'message != NULL' failed Jan 2 01:29:35 buildroot daemon.info bluetoothd[204]: Bluetooth daemon 5.47 Jan 2 01:29:35 buildroot daemon.err bluetoothd[204]: GLib: g_error_new_literal: assertion 'message != NULL' failed Jan 2 01:29:53 buildroot user.info kernel: [ 242.075988] (stc): chnl_id list empty :4 Jan 2 01:29:54 buildroot user.info kernel: [ 242.080322] (stk) : st_kim_start(stk) :ldisc_install = 1 Jan 2 01:29:54 buildroot user.info kernel: [ 242.249725] (stc): st_tty_open (stk) :line discipline installed Jan 2 01:29:54 buildroot user.info kernel: [ 242.264343] (stk) :ti-connectivity/TIInit_10.6.15.bts<4>[ 242.274230] kim kim: Direct firmware load for ti Jan 2 01:29:54 buildroot user.err kernel: [ 242.284057] (stk) : request_firmware failed(errno -2) for ti-connectivity/TIInit_10.6.15.bts Jan 2 01:29:54 buildroot user.err kernel: [ 242.292846] (stk) :download firmware failed(stk) :ldisc_install = 0 Jan 2 01:29:54 buildroot user.info kernel: [ 242.300811] (stc): st_tty_close (stk) :ldisc_install = 1 (The last 5 lines repeat many times in an apparent attempt at reinitialization) It almost seems that BT_EN (gpio_162) is not enabled. Do you have any suggestions?

Adam Ford

Advanced Member
Posts:794

20 Nov 2017 05:54 AM
It looks like I forgot to point you to a 3rd patch. My apologizes. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/arm/boot/dts/logicpd-torpedo-som.dtsi?h=v4.9.63&id=9ff502f58a2b723b6226cf13b2daf931d1d20c37 This patch will pinmux the UART2 pins as well as the the GPIO enable. adam

Adam Ford

Advanced Member
Posts:794

20 Nov 2017 08:03 AM
In the original BSP 2.4-4 based on the 3.0 kernel, you'll also want to take the .BTS file from that kernel which corrsponds to whichever device you have. For example, we have a Torpedo + Wireless -30, -31 and -32. Those are found in the model number of the SOM. Each of those have a corresponding BTS file. You'll need to take the BTS file from the original BSP and copy it to your /lib/firmware/ti-connectivity directory with the name TIInit_10.6.15.bts Looking at your error, it appears is if that file is missing. adam

William Deninger

New Member
Posts:22

01 Dec 2017 02:00 PM
Hi Adam, Thank you for your help. I've been able to get the mainstream Linux 4.4.y blue-tooth functioning using the mainboard with SOM. However, I seem to still have a problem when the SOM is inserted into our hardware. I've verified that GPIO_162 and BT_EN (J1:83 and J2:64 respectively in 1026857A_DM3730_Torpedo_Wireless_SOM_Schematic.pdf) are not connected to anything on our hardware. And 802.11 wireless seems to function without problem. Are there any other IO hardware pins that might impact the blue-tooth operation? Below are two shell outputs. The first is from the bt kernel running on the baseboard. The second on our target hardware. Baseboard based SOM successful blue-tooth functionality # modprobe st_drv [ 161.728698] (stk) :sysfs entries created # uim & # uim:@ main uim:install = /sys/devices/platform/kim/install uim:dev_name = /sys/devices/platform/kim/dev_name uim:baud_rate = /sys/devices/platform/kim/baud_rate uim:flow_cntrl = /sys/devices/platform/kim/flow_cntrl uim:begin polling... modprobe btwilink [ 170.490325] Bluetooth: Core ver 2.21 [ 170.507629] NET: Registered protocol family 31 [ 170.523315] Bluetooth: HCI device and connection manager initialized [ 170.534790] Bluetooth: HCI socket layer initialized [ 170.544219] Bluetooth: L2CAP socket layer initialized [ 170.551300] Bluetooth: SCO socket layer initialized # [ 170.615692] (stc): chnl_id list empty :4 [ 170.620269] (stk) : st_kim_start(stk) :ldisc_install = 1uim:poll broke due to event 10(PRI:2/ERR:8) uim:read 1 from install uim:@ st_uart_config uim: signal received, opening /dev/ttyO1 uim:@ set_baud_rate uim:set_baud_rate() done uim:Setting speed to 300000 uim:@ read_command_complete uim: Command complete started uim:@ read_hci_event uim: read_hci_event uim:Command complete done uim:Speed changi ng to 300000, 1 uim:@ set_custom_baud_rate [ 170.798431] (stc): st_tty_open (stk) :line discipline installeduim:Installed N_TI_WL Line displine [ 170.816101] (stk) :ti-connectivity/TIInit_10.6.15.btsuim:begin polling... [ 172.624877] (stc): add_channel_to_table: id 4 [ 172.630035] (stc): add_channel_to_table: id 2 [ 172.634979] (stc): add_channel_to_table: id 3 # # [ 174.685638] (stc): remove_channel_from_table: id 3 [ 174.691070] (stc): remove_channel_from_table: id 2 [ 174.697418] (stc): remove_channel_from_table: id 4 [ 174.702758] (stc): all chnl_ids unregistered [ 174.707702] (stk) :ldisc_install = 0uim:poll broke due to event 10(PRI:2/ERR:8)(stc): st_tty_close uim:read 0 from install uim:@ st_uart_config uim:Un-Installed N_TI_WL Line displine uim:begin polling... # hciconfig hci0: Type: Primary Bus: UART BD Address: 60:64:05:88:04:DD ACL MTU: 1021:4 SCO MTU: 180:4 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:398 acl:0 sco:0 commands:30 errors:0 Target hardware based SOM blue-tooth failure # modprobe st_drv # uim & # uim:@ main uim:install = /sys/devices/platform/kim/install uim:dev_name = /sys/devices/platform/kim/dev_name uim:baud_rate = /sys/devices/platform/kim/baud_rate uim:flow_cntrl = /sys/devices/platform/kim/flow_cntrl uim:begin polling... modprobe btwilink # uim:poll broke due to event 10(PRI:2/ERR:8) uim:read 1 from install uim:@ st_uart_config uim: signal received, opening /dev/ttyO1 uim:@ set_baud_rate uim:set_baud_rate() done uim:Setting speed to 300000 uim:@ read_command_complete uim: Command complete started uim:@ read_hci_event uim: read_hci_event uim:Invalid response uim:begin polling... uim:poll broke due to event 10(PRI:2/ERR:8) uim:read 0 from install uim:@ st_uart_config uim:Un-Installed N_TI_WL Line displine uim:begin polling... , , , < repeats many time> , , # hciconfig hci0: Type: Primary Bus: UART BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:0 errors:0 From /var/log/messages: Jul 1 00:04:54 buildroot user.info kernel: [ 307.015472] Bluetooth: Core ver 2.21 Jul 1 00:04:54 buildroot user.info kernel: [ 307.042083] NET: Registered protocol family 31 Jul 1 00:04:54 buildroot user.info kernel: [ 307.064208] Bluetooth: HCI device and connection manager initialized Jul 1 00:04:54 buildroot user.info kernel: [ 307.084167] Bluetooth: HCI socket layer initialized Jul 1 00:04:54 buildroot user.info kernel: [ 307.096160] Bluetooth: L2CAP socket layer initialized Jul 1 00:04:54 buildroot user.info kernel: [ 307.112731] Bluetooth: SCO socket layer initialized Jul 1 00:04:54 buildroot user.info kernel: [ 307.196044] (stc): chnl_id list empty :4 Jul 1 00:04:55 buildroot user.info kernel: [ 307.200592] (stk) : st_kim_start(stk) :ldisc_install = 1 Jul 1 00:04:56 buildroot user.err kernel: [ 308.355804] (stk) :ldisc installation timeout(stk) :ldisc_install = 0 Jul 1 00:04:57 buildroot user.err kernel: [ 309.355621] (stk) : timed out waiting for ldisc to be un-installed(stk) :ldisc_install = 1 Jul 1 00:04:58 buildroot user.err kernel: [ 310.506134] (stk) :ldisc installation timeout(stk) :ldisc_install = 0 Jul 1 00:04:59 buildroot user.err kernel: [ 311.505981] (stk) : timed out waiting for ldisc to be un-installed(stk) :ldisc_install = 1 Jul 1 00:05:00 buildroot user.err kernel: [ 312.675781] (stk) :ldisc installation timeout(stk) :ldisc_install = 0 Jul 1 00:05:02 buildroot user.err kernel: [ 313.675781] (stk) : timed out waiting for ldisc to be un-installed(stk) :ldisc_install = 1 Jul 1 00:05:03 buildroot user.err kernel: [ 314.825775] (stk) :ldisc installation timeout(stk) :ldisc_install = 0 Jul 1 00:05:04 buildroot user.err kernel: [ 315.825775] (stk) : timed out waiting for ldisc to be un-installed(stk) :ldisc_install = 1 Jul 1 00:05:05 buildroot user.err kernel: [ 316.985809] (stk) :ldisc installation timeout(stk) :ldisc_install = 0 Jul 1 00:05:06 buildroot user.err kernel: [ 317.985931] (stk) : timed out waiting for ldisc to be un-installed(stk) :ldisc_install = 1 Jul 1 00:05:07 buildroot user.err kernel: [ 319.145812] (stk) :ldisc installation timeout(stk) :ldisc_install = 0 Jul 1 00:05:07 buildroot user.err kernel: [ 320.145690] (stk) : timed out waiting for ldisc to be un-installed<3>[ 320.155517] Bluetooth: st_register failed Jul 1 00:08:27 buildroot authpriv.info dropbear[296]: Exit (root): Disconnect received Any and all thoughts are greatly appreciated. -William

Adam Ford

Advanced Member
Posts:794

01 Dec 2017 06:38 PM
If you're seeing issues on your board but not on the development board, I would look at the uP_UARTC pins that connect to J2.76, J2.74, J2.72 and J2.88 on the SOM. The Bluetooth module uses the UARTC (uart2) for transmitting data back and forth. Anything on those lines may interfere, especially at 3M baud. adam

You are not authorized to post a reply.

Forums Texas Instruments SOMs and Development Kits OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit