Scan Response not received from a bonded device after advertising burst

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • SimpleLink Lowpower SDK F3 BLE5 Stack
    • BLE_LOKI-2500
    • BLE Stack BLE5-3.3.3
    • Hide
      BLE_LOKI_8_40_00_RC2
      BLE_LOKI_8_40_00
      Show
      BLE_LOKI_8_40_00_RC2 BLE_LOKI_8_40_00
    • CC23XX

      Summary- Behavior occurs due to a combination of two phenomena:

      1. The ADV is disabled after a single burst - this means the next ADV will be a new command to the RCL
      2. After each command the stack deletes the extended accept list under certain circumstances. Need to check if it's acceptable to keep resolved addresses in extended accept list - this way the RCL will at least answer with a SCAN_RSP on the second adv set.{}

      SDK Version: simplelink_lowpower_f3_sdk_8_10_01_02

      SDK Versions tested: (Product SDK)

      • 8.10.01.02
      • 8.20.00.82_ea
      • 8.20.00.83_eng

      Device: CC2340R5

      Issue description: Scan response sometimes arenot being received from a bonded device. During initial debug, it was found that this was not happening due to the address of the bonded device not getting added to the Accept List. The filter was set to "Process Scan Requests from Bonded Devices Only", which would cause the Scan Response not to be sent.

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

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-5064 - Scan Response not received from a b...
                SYNCHRONIZED
                • Last Sync Date: