Pi3B+ with PiCore 13 Bluetooth Issues

[carrot]

I have a Pi3B+ setup with PiCore 13 working well with the exception of Bluetooth, which I want to setup for connecting a keyboard. I have read through and followed the posts on this forum for setting things up and have had success in turning on, searching and pairing the keyboard with an authentication key. My problem is that when I issue the connect command in bluetoothctl I get the message that the device is connected then a few seconds later I get an error 'org.bluez.Error.NotAvailable' and then the connection messages again saying its not connected. I have also tried to pair my iPhone thinking maybe its a keyboard issue, but this resulted in the same problem, it would pair but not connect with the same error. I have also tried blueman and the various scripts to use different rates (921600 and 300000) when running hciattach, and loading/not loading hci_uart module. I also have tried starting bluetooth via bluetoothd rather than init.d/bluez to watch for errors, but none of the messages gave any indication as to what the problem was.

Has anyone got any ideas on something else I can try to get bluetooth working?

thanks

[Paul_123]

Without knowing exactly what scripts you are using, it’s hard to say.  The order the scripts run, is important.   

What is in dmesg?   And does the firmware load properly?

[carrot]

sorry for the lack of info Paul. From what I can tell the firmware does load properly, and I can run the hciattach command to flash the firmware.  The attached file is part of my setup script for loading and powering on bluetooth. After I couldn't connect the keyboard I added the manual trigger to skip the "auto setup" and print them to the screen instead so I could "manually" follow them.

[attachment deleted by admin]

[Rich]

Hi carrot
The file you attached is empty.

[carrot]

sorry, hopefully this one is better

[Paul_123]

Looks ok.  Here is a more complete script to setup hci.  https://github.com/RPi-Distro/pi-bluetooth/blob/master/usr/bin/btuart

I mostly pair audio devices using a noinputnooutput agent, but keyboards likely need a different agent.

When you are pairing, what agent are you using?   Also, what version of bluez is used?   5.55 should be the current in the repo.

[carrot]

thanks Paul. I had tried that script but had issues with /dev/serial1 not existing. I have revised my script to include the MAC address and change the rate per the link but no improvements.

the version of Bluez is 5.55 per the repo. I have even tried re-downloading it to make sure that is the correct one.

to be honest I didn't understand the agent piece and so was just trying with the default agent that was loaded. after reading a little more I have now tried KeyboardOnly, KeyboardDisplay, and DisplayOnly, all of which have given the same result. I can pair and enter the key from the keyboard, but then it disconnects with the Bluez error form my previous post.
I have attached a screenshot to try and show this part of the process.

[Rich]

Hi carrot
Did you start  dbus ?

[carrot]

Yes via /usr/local/etc/init.d/dbus

Once I start bluez I do get a msg stating dbus-daemon has stopped.

[Juanito]

Sometimes that happens - you can double-check if dbus is still running with:

Code: [Select]

$ ps aux | grep dbus

[Rich]

Hi carrot

... I do get a msg stating dbus-daemon has stopped.

I'm guessing that may be the source of the  "ServicesResolved:  No"  and  "org.bluez.Error.NotAvailable"  error messages
in your attachment.

[carrot]

thanks Juanito and Rich. I have double checked and dbus is definitely still running before I try to connect to the keyboard.

[Rich]

Hi carrot
Is it still running after you try to connect to the keyboard?

[carrot]

yes it is Rich

[Paul_123]

So pairing and authentication appear to be working. The error is relegated to a profile or service not enabled by default in bluez.  It may require a change in one of the configuration files, or it may require extra software running.  Is this just a keyboard, or does it have some other types of controls on it?

Anyway, after Pairing, type

trust 34:88:5D:41:9C:42

also please copy and paste the results of

info 34:88:5D:41:9C:42