Help¶

Set the Bluetooth Company Identifier that will be used in the VERSION_IND PDU. Uses BT_COMPANY_ID by default, although silicon vendors and hardware manufacturers can set their own Company Identifier for the controller. The full list of Bluetooth Company Identifiers can be found here: https://www.bluetooth.com/specifications/assigned-numbers/company-identifiers

Direct dependencies¶

BT_LL_SW_SPLIT && BT_CTLR && BT_HCI && BT

(Includes any dependencies from ifs and menus.)

Default¶

BT_COMPANY_ID

Kconfig definition¶

At <Zephyr>/subsys/bluetooth/controller/Kconfig.ll_sw_split:87

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:9 → <Zephyr>/subsys/bluetooth/Kconfig:240 → <Zephyr>/subsys/bluetooth/controller/Kconfig:595

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

config BT_CTLR_COMPANY_ID
    hex "Controller Company Id"
    range 0x0000 0xFFFF
    default BT_COMPANY_ID
    depends on BT_LL_SW_SPLIT && BT_CTLR && BT_HCI && BT
    help
      Set the Bluetooth Company Identifier that will be used in
      the VERSION_IND PDU. Uses BT_COMPANY_ID by default, although
      silicon vendors and hardware manufacturers can set their own
      Company Identifier for the controller. The full list of Bluetooth
      Company Identifiers can be found here:
      https://www.bluetooth.com/specifications/assigned-numbers/company-identifiers

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