michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: Bluetooth: Document issue with certain controllers

Browse source 
Certain Qualcomm controllers do not accept our settings for Host Buffer
Size:

< HCI Command: Host Buffer Size (0x03|0x0033) plen 7       #19 [hci0]
22.391048
        ACL MTU: 27   ACL max packet: 6
        SCO MTU: 0    SCO max packet: 0
> HCI Event: Command Complete (0x0e) plen 4                #20 [hci0]
22.391525
      Host Buffer Size (0x03|0x0033) ncmd 1
        Status: Invalid HCI Command Parameters (0x12)

Likely due to the fact that we do not reserve space for any SCO packets
in the Host.

Other Controllers (Realtek) seem to not transmit any data at all in the
Controller to Host direction if Controller to Host flow control is
enabled.

Document this fact in the User Guide so that users know what to do when
this happens.

Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
This commit is contained in:
Carles Cufi 2020-04-24 20:58:18 +02:00 • committed by Johan Hedberg
commit 3d16bda27d
1 changed files with 27 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

42
doc/guides/bluetooth/bluetooth-dev.rst
View file

@ -71,8 +71,8 @@ to use the btmon tool from :ref:`BlueZ <bluetooth_bluez>`:
$ btmon --tty <console TTY> --tty-speed 115200
QEMU with an external Controller
================================
Host on Linux with an external Controller
=========================================
.. note::
This is currently only available on GNU/Linux
@ -81,17 +81,37 @@ This setup relies on a "dual-chip" :ref:`configuration <bluetooth-configs>`
which is comprised of the following devices:
#. A :ref:`Host-only <bluetooth-build-types>` application running in the
:ref:`QEMU <application_run_qemu>` emulator
:ref:`QEMU <application_run_qemu>` emulator or the ``native_posix`` native
port of Zephyr
#. A Controller, which can be one of two types:
* A commercially available Controller
* A :ref:`Controller-only <bluetooth-build-types>` build of Zephyr
.. warning::
Certain external Controllers are either unable to accept the Host to
Controller flow control parameters that Zephyr sets by default (Qualcomm), or
do not transmit any data from the Controller to the Host (Realtek). If you
see a message similar to::
<wrn> bt_hci_core: opcode 0x0c33 status 0x12
when booting your sample of choice (make sure you have enabled
:option:`CONFIG_BT_DEBUG_LOG` in your :file:`prj.conf` before running the
sample), or if there is no data flowing from the Controller to the Host, then
you need to disable Host to Controller flow control. To do so, set
``CONFIG_BT_HCI_ACL_FLOW_CONTROL=n`` in your :file:`prj.conf`.
QEMU
----
You can run the Zephyr Host on the :ref:`QEMU emulator<application_run_qemu>`
and have it interact with a physical external Bluetooth Controller.
Refer to :ref:`bluetooth_qemu_posix` for full instructions on how to build and
run an application in this setup.
Native POSIX with an external Controller
========================================
Native POSIX
------------
.. note::
This is currently only available on GNU/Linux
@ -100,16 +120,8 @@ The :ref:`Native POSIX <native_posix>` target builds your Zephyr application
with the Zephyr kernel, and some minimal HW emulation as a native Linux
executable.
This executable is a normal Linux program, which can be debugged and
instrumented like any other.
Just like with QEMU, you also need to use a combination of two devices:
#. A :ref:`Host-only <bluetooth-build-types>` application running in
native_posix as a Linux application
#. A Controller, which can be one of two types:
* A commercially available Controller
* A :ref:`Controller-only <bluetooth-build-types>` build of Zephyr
instrumented like any other, and it communicates with a physical external
Controller.
Refer to :ref:`bluetooth_qemu_posix` for full instructions on how to build and
run an application in this setup.