b20784dfbb
The API directory really isn't the best place for shell documentation, which isn't API. Created a new directory for Bluetooth shell documentation and moved the ISO and LE Audio docs in there. The existing bluetooth-shell.rst file was also split into several new files, so that it follows the same structure. Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
27 lines
1.1 KiB
ReStructuredText
27 lines
1.1 KiB
ReStructuredText
Bluetooth: GATT Shell
|
|
#####################
|
|
|
|
The following examples assume that you have two devices already connected.
|
|
|
|
To perform service discovery on the client side, use the :code:`gatt discover` command. This should
|
|
print all the services that are available on the GATT server.
|
|
|
|
On the server side, you can register pre-defined test services using the :code:`gatt register`
|
|
command. When done, you should see the newly added services on the client side when running the
|
|
discovery command.
|
|
|
|
You can now subscribe to those new services on the client side. Here is an example on how to
|
|
subscribe to the test service:
|
|
|
|
.. code-block:: console
|
|
|
|
uart:~$ gatt subscribe 26 25
|
|
Subscribed
|
|
|
|
The server can now notify the client with the command :code:`gatt notify`.
|
|
|
|
Another option available through the GATT command is initiating the MTU exchange. To do it, use the
|
|
:code:`gatt exchange-mtu` command. To update the shell maximum MTU, you need to update Kconfig
|
|
symbols in the configuration file of the shell. For more details, see
|
|
:zephyr:code-sample:`bluetooth_mtu_update`.
|