Adjust Peripheral startTime in Case we Miss the Peer on the CS Instant

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Urgent
    • SimpleLink Lowpower SDK F3 BLE5 Stack
    • BLE_LOKI-3820
    • BLE_LOKI_9_14_00
    • Hide
      BLE_LOKI_9_14_01
      BLE_LOKI_9_14_01_RC1
      Show
      BLE_LOKI_9_14_01 BLE_LOKI_9_14_01_RC1
    • Hide
      CC23xx
      CC27xx
      Show
      CC23xx CC27xx

      Description: When operating with certain smartphone as peer, we occasionally experience anchor misalignment between CS events, particularly during connection parameter updates. This causes subevents to lose synchronization, resulting in procedure abortion and returning 0xFFFFFFFF (invalid) measurements. The current implementation does not attempt to recover from this specific type of anchor misalignment, leading to complete procedure failure and invalid results being reported to the host.

      Reproduction Steps:
      Establish BLE connection with certain smartphone
      Initialize Channel Sounding with multi-event procedures
      Put the phone very close to the Car Node
      Observe the anchor misalignment in sniffer logs, followed by procedure failure

            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-6299 - Adjust Peripheral startTime in Case...
                SYNCHRONIZED
                • Last Sync Date: