Skip to contentSkip to conversation

Request for BLE server applications and documents - BLUEZ

DISCUSSION Mallikarjuna V 3 participants 5 messages May 16, 2016 – May 17, 2016 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

Hi Marcel,

I need to develop the BLE based profile on GATT layer by using BULEZ software. I am unable to find the any reference documents to add new BLE services on GATT layer.

Can you please provide any documents or links to develop the GATT server profiles on BLUEZ stack.

Thanks & Regards,
V.Mallikarjuna Rao.

#1 lore raw

Hi,

Quoted 9 lines · Mallikarjuna V

Hi Marcel,

I need to develop the BLE based profile on GATT layer by using BULEZ software. I am unable to find the any reference documents to add new BLE services on GATT layer.

Can you please provide any documents or links to develop the GATT server profiles on BLUEZ stack.

You can find the GATT related API documentation here:

https://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/gatt-api.txt

There is also a python sample available under test/example-gatt-server:

https://git.kernel.org/cgit/bluetooth/bluez.git/tree/test/example-gatt-server

Signature · 1 line
Luiz Augusto von Dentz
#2 lore raw

||||

Luiz,

We tried below python script, we got an error *|"GattManager1 interface not found"
|*

Can you please provide flow of sequence and dependences.

Thanks &Regards,
V.Mallikarjuna Rao

Quoted 22 lines · Luiz Augusto von Dentz

Hi,

Quoted 8 lines · Mallikarjuna V

Hi Marcel,

I need to develop the BLE based profile on GATT layer by using BULEZ software. I am unable to find the any reference documents to add new BLE services on GATT layer.

Can you please provide any documents or links to develop the GATT server profiles on BLUEZ stack.

You can find the GATT related API documentation here:

https://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/gatt-api.txt

There is also a python sample available under test/example-gatt-server:

https://git.kernel.org/cgit/bluetooth/bluez.git/tree/test/example-gatt-server

#3 lore raw

Hi,

Quoted 7 lines · Mallikarjuna V

Luiz,

We tried below python script, we got an error "GattManager1 interface not found"

Can you please provide flow of sequence and dependences.

Please don't top post in the list, comment inline:
http://www.bluez.org/development/lists/. It is also not recommended to use html in the emails sent to the list.

Regarding the actual problem it is probably because experimental interfaces are not enabled by default, you can do enable that by passing -E to bluetoothd.

Quoted 32 lines · Luiz Augusto von Dentz

Hi,

On Mon, May 16, 2016 at 10:05 AM, Mallikarjuna V
<[email protected]> wrote:

Hi Marcel,

I need to develop the BLE based profile on GATT layer by using BULEZ software. I am unable to find the any reference documents to add new BLE services on GATT layer.

Can you please provide any documents or links to develop the GATT server profiles on BLUEZ stack.

You can find the GATT related API documentation here:

https://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/gatt-api.txt

There is also a python sample available under test/example-gatt-server:

https://git.kernel.org/cgit/bluetooth/bluez.git/tree/test/example-gatt-server

Signature · 1 line
Luiz Augusto von Dentz
#4 lore raw
Quoted 3 lines · Luiz Augusto von Dentz

<snip>

Quoted 3 lines

Regarding the actual problem it is probably because experimental interfaces are not enabled by default, you can do enable that by passing -E to bluetoothd.

If you’re using systemd, the file you’ll want to tweak is

/lib/systemd/system/bluetooth.service

Modify your ExecStart line to include the -E option. Mine currently looks like:

ExecStart=/usr/lib/bluetooth/bluetoothd -d -E --noplugin=*

The -d is indispensable and took my a while to stumble upon. Any python error you have that is fired by dbus callbacks will not show up on the stdout/stderr of you program (e.g. an error downstream of a WriteValue() callback). Rather it will show up in the debug output of the bluetooth daemon. So I pretty much always have

journalctl -flu bluetooth

running when I’m changing things, so I can see those errors reported there.

By default, you get a whole bunch of stuff in your dbus namespace from older stuff. The —noplugin=* flag gets rid of all of those, so you’ll only see your own stuff in the dbus tree.