Help¶

Number of buffers available for fragments of TX buffers. Warning: setting this to 0 means that the application must ensure that queued TX buffers never need to be fragmented, i.e. that the controller’s buffer size is large enough. If this is not ensured, and there are no dedicated fragment buffers, a deadlock may occur. In most cases the default value of 2 is a safe bet.

Direct dependencies¶

BT_CONN && BT_HCI_HOST && BT_HCI && BT

(Includes any dependencies from ifs and menus.)

Defaults¶

NET_BUF_TX_COUNT if NET_L2_BT
2

Kconfig definition¶

At <Zephyr>/subsys/bluetooth/host/Kconfig.l2cap:29

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:9 → <Zephyr>/subsys/bluetooth/Kconfig:239 → <Zephyr>/subsys/bluetooth/host/Kconfig:505

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → L2CAP Options

config BT_L2CAP_TX_FRAG_COUNT
    int "Number of L2CAP TX fragment buffers"
    range 0 255
    default NET_BUF_TX_COUNT if NET_L2_BT
    default 2
    depends on BT_CONN && BT_HCI_HOST && BT_HCI && BT
    help
      Number of buffers available for fragments of TX buffers. Warning:
      setting this to 0 means that the application must ensure that
      queued TX buffers never need to be fragmented, i.e. that the
      controller's buffer size is large enough. If this is not ensured,
      and there are no dedicated fragment buffers, a deadlock may occur.
      In most cases the default value of 2 is a safe bet.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)