You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While doing the commissioning using the BLE-wifi after resetting the DUT sometimes commissioning failed with an error unsupported certificate format. this is causing an interrupt in the automation testing of the test harness.
[1658315004.845157][5619:5624] CHIP:CTL: Device returned status 3 on receiving the NOC
[1658315004.845228][5619:5624] CHIP:CTL: Add NOC failed with error ../../src/controller/CHIPDeviceController.cpp:1271: CHIP Error 0x00000050: Unsupported certificate format
[1658315004.845302][5619:5624] CHIP:CTL: Error on commissioning step 'SendNOC': '../../src/controller/CHIPDeviceController.cpp:1271: CHIP Error 0x00000050: Unsupported certificate format'
[1658315004.845359][5619:5624] CHIP:CTL: Failed to perform commissioning step 13
[165
NOCResponse(Status=3) is InvalidNOC from device. I couldn't find the NOC bytes in the log. Could you post the malformed NOC TLV hexstream to this issue?
Please add --trace_decode 1 to your chip-tool invocations so we can see outbound commands such as the AddNOC and see the malformed certificate.
The NOC will be the first parameter (0) of CommandPathIB = //EP0/Cluster=0x3E/Command=6.
shgutte
changed the title
[EFR32] Commissioning is failing at step 13 : Unsupported certificate format
[EFR32] Commissioning is failing at commissioning step 13 : Unsupported certificate format
Jul 20, 2022
Problem
While doing the commissioning using the BLE-wifi after resetting the DUT sometimes commissioning failed with an error unsupported certificate format. this is causing an interrupt in the automation testing of the test harness.
App used - lock app
Platform - Chip-tool - RPI-4, 8GB RAM
DUT - EFR32 + WF200 , EFR32 +RS9116
Network - Ble-wifi
Logs
chip-tool-step13-error.txt
device-step13-error.txt
The text was updated successfully, but these errors were encountered: