Uploaded image for project: 'Embedded Software & Tools'
  1. Embedded Software & Tools
  2. EXT_EP-10806

HCI_EXT_SetTxPowerCmd only works if adv sets are destroyed/not yet created

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • SimpleLink CC13x2-26x2 SDK BLE5 Stack
    • BLE_AGAMA-3231
    • BLE Stack BLE5-2.2.1 RC12
    • Hide
      BLE Stack BLE5-2.2.5 RC4
      BLE Stack BLE5-2.2.5 RC2
      BLE Stack BLE5-2.2.5
      Show
      BLE Stack BLE5-2.2.5 RC4 BLE Stack BLE5-2.2.5 RC2 BLE Stack BLE5-2.2.5
    • CC26X2R1

      Problem Description

      HCI_EXT_SetTxPowerCmd does not affect an advertisement set's tx power after
      an advertisement set has been enabled. This issue does not occur before if HCI_EXT_SetTxPowerCmd is called before GapAdv_create().

      The issue was seen in the simple_peripheral example after GapAdv_create()is used to enable an advertisement. Calling HCI_EXT_SetTxPowerCmd after this step does not result in a change in TxPower.

      Root cause/Fix:

      This issue was fixed in the link layer. HCI_EXT_SetTxPowerCmd will allow runtime changes to the TX power only if using GapAdv_create() passed in with GAP_ADV_TX_POWER_NO_PREFERENCE, which is set by default in the application.

            syncuser TI User
            syncuser TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: