RTL8723bs Bluetooth
#21
(02-23-2017, 07:01 AM)xalius Wrote: It's not really a kernel module, the BT/Wifi module has a UART that is connected to ttyS1, and all that project does is provide a way to upload a firmware binary that enables the module to be attached to the BT stack on the Linux side:

/usr/local/sbin/bluetooth/rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5 > /usr/local/sbin/bluetooth/hciattach.txt 2>&1 &

If my understanding is correct it should provide the same functionality even if a little oddly. The package as described will insert the (bin) and set up both pieces required to provide linux functionality at boot time rather then the mechanism via the desktop. Yes it is a bit like the chicken and the egg, you must have bluetooth pre configured to see any benefit. Incremental steps in slaying the dragon... movement toward a fully functional OS on new hardware is always a slow and winding road. Not to mention QA aspect. But we enjoy the ride! Please correct me if my interpretation is erroneous.

Mod edit: Try not to reply inside the quote from another poster!! Wink
  Reply
#22
Hi jhawk,

have you followed the instructions on https://github.com/lwfinger/rtl8723bs_bt?
I needed to copy the following files into "/usr/local/sbin/bluetooth/" after "make" and "make install".
- hciattach.txt
- rtk_hciattach
- start_bt.sh

The scripts has been installed to...
- /usr/local/sbin/pine64_bluetooth.sh
- /etc/systemd/system/bluetooth-module.service

I was able to type some commands in [bluetoothctl]# after copying these files into "/usr/local/sbin/bluetooth/"... BUT!
I don't know what exactly the problem is, but bluez seems to have bugs.

Btw: I'm using longsleep's Ubuntu image xenial-pine64-bspkernel-20161218-1.img

Here are some quotes:
Code:
root@pine64:~# rfkill list
0: sunxi-bt: Bluetooth
       Soft blocked: no
       Hard blocked: no
1: phy0: Wireless LAN
       Soft blocked: no
       Hard blocked: no
2: phy1: Wireless LAN
       Soft blocked: no
       Hard blocked: no
3: hci0: Bluetooth
       Soft blocked: no
       Hard blocked: no
Code:
root@pine64:~# pine64_bluetooth.sh
Initializing Pine64 Bluetooth Module.
[NEW] Controller 34:C3:D2:F8:C9:4B pine64 [default]
[bluetooth]# list
Controller 34:C3:D2:F8:C9:4B pine64 [default]
[bluetooth]# show
Controller 34:C3:D2:F8:C9:4B
        Name: pine64
        Alias: pine64
        Class: 0x000000
        Powered: no
        Discoverable: no
        Pairable: yes
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0525
        Discovering: no
Code:
root@pine64:~# pine64_bluetooth.sh
Initializing Pine64 Bluetooth Module.
[NEW] Controller 34:C3:D2:F8:C9:4B pine64 [default]
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Failed
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
Code:
root@pine64:~# systemctl status bluetooth
● bluetooth.service - Bluetooth service
  Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
  Active: active (running) since Wed 2017-03-22 22:44:22 UTC; 8min ago
    Docs: man:bluetoothd(8)
Main PID: 2798 (bluetoothd)
  Status: "Running"
  CGroup: /system.slice/bluetooth.service
          └─2798 /usr/lib/bluetooth/bluetoothd

Mar 22 22:44:22 pine64 bluetoothd[2798]: Current Time Service could not be registered
Mar 22 22:44:22 pine64 bluetoothd[2798]: gatt-time-server: Input/output error (5)
Mar 22 22:44:22 pine64 bluetoothd[2798]: Not enough free handles to register service
Mar 22 22:44:22 pine64 bluetoothd[2798]: Not enough free handles to register service
Mar 22 22:44:22 pine64 bluetoothd[2798]: Sap driver initialization failed.
Mar 22 22:44:22 pine64 bluetoothd[2798]: sap-server: Operation not permitted (1)
Mar 22 22:44:22 pine64 bluetoothd[2798]: hci0 Load Connection Parameters failed: Unknown Command (0x01)
Mar 22 22:44:22 pine64 systemd[1]: Started Bluetooth service.
Mar 22 22:44:38 pine64 bluetoothd[2798]: Failed to set mode: Failed (0x03)
Mar 22 22:51:24 pine64 bluetoothd[2798]: Failed to set mode: Failed (0x03)

Best regards
Julian
My forum topics:
• Create a WiFi hotspot on Debian 8
• Turn your Pine64 into a music server with mpd
• Adjust brightness of LCD on Armbian Desktop with 1 click
• My cases for Pine64 (acryl, lego & wood)

• Pine 64 - DACH - Facebook page for german-speaking Pine64-fans.
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Wifi / Bluetooth Board Update S265 2 4,687 07-30-2020, 04:53 PM
Last Post: S265
Information Howto: Getting Bluetooth (serial console) working on Debian pfeerick 14 34,887 08-19-2019, 04:33 AM
Last Post: Roverius
  WIFI & Bluetooth? 7777777 14 31,015 12-24-2016, 05:01 AM
Last Post: Toriless
  Using Bluetooth for Sending serial data Arjun 9 16,435 10-19-2016, 10:19 PM
Last Post: Arjun
  How can you get the WIFI/Bluetooth module separate? GoZone 8 12,654 07-06-2016, 05:23 PM
Last Post: JasperBrown
  WiFi/BT module, no bluetooth riviera89 5 8,032 06-24-2016, 04:32 PM
Last Post: srinivas.s34@gmail.com
  Board doesn't boot when wifi/Bluetooth connected with Lcd screen Krinilssen 4 7,755 06-16-2016, 07:22 AM
Last Post: Krinilssen
  WIFI/Bluetooth Chipset monmoonmooonmoooon 2 5,719 01-20-2016, 06:02 AM
Last Post: monmoonmooonmoooon

Forum Jump:


Users browsing this thread: 1 Guest(s)