Help¶

Maximum number of segments supported for incoming messages. This value should typically be fine-tuned based on what models the local node supports, i.e. what’s the largest message payload that the node needs to be able to receive. This value affects memory and call stack consumption, which is why the default is lower than the maximum that the specification would allow (32 segments).

The maximum incoming SDU size is 12 times this number (out of which 4 or 8 bytes is used for the Transport Layer MIC). For example, 5 segments means the maximum SDU size is 60 bytes, which leaves 56 bytes for application layer data using a 4-byte MIC and 52 bytes using an 8-byte MIC.

Direct dependencies¶

BT_MESH && BT

(Includes any dependencies from ifs and menus.)

Default¶

3

Kconfig definition¶

At <Zephyr>/subsys/bluetooth/mesh/Kconfig:298

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:8 → <Zephyr>/subsys/bluetooth/Kconfig:258

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Bluetooth Mesh support

config BT_MESH_RX_SEG_MAX
    int "Maximum number of segments in incoming messages"
    range 2 32
    default 3
    depends on BT_MESH && BT
    help
      Maximum number of segments supported for incoming messages.
      This value should typically be fine-tuned based on what
      models the local node supports, i.e. what's the largest
      message payload that the node needs to be able to receive.
      This value affects memory and call stack consumption, which
      is why the default is lower than the maximum that the
      specification would allow (32 segments).

      The maximum incoming SDU size is 12 times this number (out of
      which 4 or 8 bytes is used for the Transport Layer MIC). For
      example, 5 segments means the maximum SDU size is 60 bytes,
      which leaves 56 bytes for application layer data using a
      4-byte MIC and 52 bytes using an 8-byte MIC.

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