TC-CNET-4.10 Test step 11 timeout.

Hi,

      Our product is about to undergo Matter certification. However, in the testing of TC-CNET-4.10, during the 11th step " ./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", there is a timeout error indicating that the command is not responding. However, when executing it immediately for the second time, it succeeds. This phenomenon is consistently reproducible. Can you provide any guidance on how to resolve this issue? We are anxious to proceed with the product testing.

      I'm urgently looking forward to your reply.

      Jerry.

      22/8/2023

Parents
  • Hi Jerry,

    Just got confirmation that we are able to reproduce the issue with the release configuration of door lock sample (NCS 2.2.0).
    steps needed to reproduce:
    1. commission door lock
    2. run ./chip-tool
    3. run ./chip-tool remove-network hex:<extended pan id e.g. 1111111122222222> 1 0
    4. run ./chip-tool arm-fail-safe 0 0 1 0
    It seems that the issue is with some race condition connected with CASE session because while we ran above steps within interactive controller, the 4th step successfully passed
    1. commission device
    2. run chip-tool interactive by ./chip-tool interactive start
    3. generalcommissioning arm-fail-safe 900 1 1 0
    4. remove-network hex:<extended pan id e.g. 1111111122222222> 1 0
    5. arm-fail-safe 0 0 1 0
    To find the root cause, We need more time to investigate.
    Best regards,
    Charlie
Reply
  • Hi Jerry,

    Just got confirmation that we are able to reproduce the issue with the release configuration of door lock sample (NCS 2.2.0).
    steps needed to reproduce:
    1. commission door lock
    2. run ./chip-tool
    3. run ./chip-tool remove-network hex:<extended pan id e.g. 1111111122222222> 1 0
    4. run ./chip-tool arm-fail-safe 0 0 1 0
    It seems that the issue is with some race condition connected with CASE session because while we ran above steps within interactive controller, the 4th step successfully passed
    1. commission device
    2. run chip-tool interactive by ./chip-tool interactive start
    3. generalcommissioning arm-fail-safe 900 1 1 0
    4. remove-network hex:<extended pan id e.g. 1111111122222222> 1 0
    5. arm-fail-safe 0 0 1 0
    To find the root cause, We need more time to investigate.
    Best regards,
    Charlie
Children
No Data
Related