Attestation - Secure Cert, SendAttestationRequest failed (CON-1453)

[ethan-jy]

Describe the bug
Chip-tool debugging failed
command:

esp-matter-mfg-tool -cn meanwell -v 0xFFF2 -p 0x8001 --pai
-k /home/meanwell/espressif/esp-matter/connectedhomeip/connectedhomeip/credentials/test/attestation/Chip-Test-PAI-FFF2-8001-Key.pem
-c /home/meanwell/espressif/esp-matter/connectedhomeip/connectedhomeip/credentials/test/attestation/Chip-Test-PAI-FFF2-8001-Cert.pem
-cd /home/meanwell/espressif/esp-matter/connectedhomeip/connectedhomeip/credentials/test/certification-declaration/Chip-Test-CD-FFF2-8001.der
--dac-in-secure-cert --target esp32h2 -n 2 --product-name meanwell --hw-ver-str "1.0" --vendor-name meanwell

xxx_esp_secure_cert.bin download to 0xd000;
xxx-partition download to 0x3E0000;

DAC Provider set to Attestation - Secure Cert
CONFIG_CHIP_FACTORY_NAMESPACE_PARTITION_LABEL = fctry = 0x3E0000

Environment

• ESP-Matter Commit Id:1.3

• ESP-IDF Commit Id:5.3.1

• SoC (eg: ESP32 or ESP32-C3):esp32h2

• Device Logs (Please attach the log file):ubuntu
  Uploading Chip-tool Log.txt…

• Host Machine OS:

• Host Machine Python version:

• Commissioner app and versions if present:

• Home hub app and versions if present:

• Commissioner's logs if present:

Any additional details
...

[ethan-jy]

Chip-tool Log.txt
SDK config.txt
Please review the recording

[ethan-jy]

[ethan-jy]

What is this problem and how should it be handled?

[shripad621git]

@ethan-jy , thanks for reporting the issue. We are looking into it. We will get back with the solution soon.

[shripad621git]

@ethan-jy , we have identified the issue. The esp-matter-mfg-tool does not burn the private key in the efuse in case of h2. For more information on efuse and esp_secure_cert_partition in case of esp32h2, you can refer here.
We are in process of adding the support and testing it out. You will get to test the functionality soon.