In rare cases, when RPA refresh interval is low, a connection may fail to be established

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • SimpleLink Lowpower SDK F3 BLE5 Stack
    • BLE_LOKI-1653
    • BLE Stack BLE5-3.3.1 RC4
    • Hide
      BLE Stack BLE5-3.3.2 RC10
      BLE Stack BLE5-3.3.2 RC8
      BLE Stack BLE5-3.3.2
      Show
      BLE Stack BLE5-3.3.2 RC10 BLE Stack BLE5-3.3.2 RC8 BLE Stack BLE5-3.3.2
    • CC23XX

      Description of the issue: When Initiator receives aux_scan_rsp with unknown address, instead of sending "last command done" and let the stack decide if it's a valid address, it ignore the packet and keep scanning. The peripheral act as the connection is established. 

      Steps to reproduce the issue:

      1. Set the initiator Resolvable Private Address Timeout to 5 seconds or less.
      2. Set Create connection command with privacy.
      3. The peripheral will advertise but with wrong IRK.
      4. The connection should not be established.
      5. Wait at least 5 seconds.
      6. The peripheral will now advertise with correct IRK
      7. The connection now should be established but will fail.

       

       

            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-4569 - In rare cases, when RPA refresh int...
                SYNCHRONIZED
                • Last Sync Date: