TC-CNET-4.10 Test step 11 timeout.

[hoorii-zzy]

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

[hoorii-zzy]

Charlie said:

For the issue itself, an 802.15.4 pcap sniffer file and Thread networkkey form that test steps can help to analyze the causes.

Hi Charlie,

I have captured the network packets for the first failed attempt and the second successful attempt during the execution of the eleventh step. Could you please take a look at them and provide your analysis?

Thanks!

Jerry

[Charlie]

Hi Jerry, 

I will forward the pcap files to our development team for analysis. 

1. What is your network key?

2. Can you test original SED sample like nrf/samples/matter/lock on nRF52840DK?

Best regards,

Charlie

[hoorii-zzy]

Hi Charlie,

I apologize for the inconvenience caused by the Docker crash. As a result, I had to restart a new Docker instance, which led to a change in my network key. I have retested the lock and was able to reproduce the same scenario. I will provide you with the new pcap files and the updated network key. Please prioritize the analysis based on these two pcap files.
The new network key is c7f5e95a64ddb5bf6b4a668bd0ca133b.

Thanks!

Jerry

[hoorii-zzy]

TC-CNET-4.10-LOCK-secondTry.pcap

TC-CNET-4.10-LOCK-firstTry.pcap

[Charlie]

Hi Jerry,

Just want to confirm the latest test is based on the original NCS\v2.2.0\nrf\samples\matter\lock, correct?

BR,

Charlie