Connection Monitor failed to start monitoring after about 6 hours

XMLWordPrintable

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: High
    • SimpleLink Lowpower SDK F3 BLE5 Stack
    • BLE_LOKI-1674
    • BLE Stack BLE5-3.3.1 RC4
    • BLE_LOKI_8_40_00
    • CC23XX
    • not reproduced for Loki High (tested with ver8.40.00.35) and Loki Low++ (tested with ver8.40.00.43)

      Description: The test runs three connections with different CI intervals: 7.5msec, 100msec, 200msec. The issue occurs after about 6 hours of the test execution.

      Steps to reproduce the issue:
      1. Flash the connection_monitor hex to cc23xx and rtls_coordinator hex to cc26xx.
      2. Flash host_test_bond hex to three cc26xx devices.
      3. Configure rtls_example python script with correct COM ports and run the script.
      4. Run three HCITester scripts (attached)

            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-4561 - Connection Monitor failed to start ...
                SYNCHRONIZED
                • Last Sync Date: