Skip to content

Commit e4abf24

Browse files
committed
1)Updated the DAC certificate ID for Trust M MTR
2)Updated the doc for Trust M MTR provisioning
1 parent 86c1249 commit e4abf24

File tree

2 files changed

+16
-10
lines changed

2 files changed

+16
-10
lines changed

docs/guides/infineon_trustm_provisioning.md

+15-9
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ OPTIGA™ Trust M with Matter test device Attestation certificate is needed.
77

88
[Raspberry Pi 4](https://www.raspberrypi.com/products/raspberry-pi-4-model-b/)
99

10-
[OPTIGA™ Trust M S2GO](https://www.infineon.com/cms/en/product/evaluation-boards/s2go-security-optiga-m/)
10+
[OPTIGA™ Trust M MTR](https://www.infineon.com/cms/en/product/evaluation-boards/trust-m-mtr-shield/)
1111

1212
[Shield2Go Adapter for Raspberry Pi](https://www.infineon.com/cms/en/product/evaluation-boards/s2go-adapter-rasp-pi-iot/)
1313
or Jumping Wire
@@ -30,32 +30,38 @@ can be used to perform provisioning by following the steps mentioned below.
3030

3131
```
3232
$ cd linux-optiga-trust-m/
33-
$ ./trustm_installation_aarch64_script.sh
33+
$ git checkout provider_dev
34+
$ git submodule update -f
35+
$ ./provider_installation_script.sh
3436
```
3537

3638
- Run the script to generate Matter test DAC for lock-app using the public key
3739
extracted from the Infineon pre-provisioned Certificate and store it into
38-
0xe0e3
40+
0xE0E0
3941

4042
```
4143
$ cd scripts/matter_provisioning/
42-
$ ./matter_dac_provisioning.sh
44+
$ ./matter_test_provisioning.sh
4345
```
4446

4547
_Note:_
4648

47-
_By running this example matter_dac_provisioning.sh, the steps shown below are
49+
_By running this example matter_test_provisioning.sh, the steps shown below are
4850
executed:_
4951

5052
_Step1: Extract the public key from the Infineon pre-provisioned
51-
Certificate(0xe0e0) using openssl command._
53+
Certificate(0xE0E0) using openssl command._
5254

5355
_Step2: Generate DAC test certificate using the extracted public key, Signed by
5456
[Matter test PAI](https://github.com/project-chip/connectedhomeip/blob/v1.1-branch/credentials/development/attestation/Matter-Development-PAI-FFF1-noPID-Cert.pem)_.
5557
Please note that production devices cannot re-use these test keys/certificates.
5658

5759
_Step3: Write DAC test certificate into OPTIGA™ Trust M certificate slot
58-
0xe0e3_
60+
0xE0E0._
5961

60-
_Step4: Write Matter test PAI into OPTIGA™ Trust M certificate slot 0xe0e8
61-
and test CD into OPTIGA™ Trust M Arbitrary OID 0xf1e0._
62+
_Step4: Write Matter test PAI into OPTIGA™ Trust M certificate slot 0xE0E8
63+
and test CD into OPTIGA™ Trust M Arbitrary OID 0xF1E0._
64+
65+
For certificate claim and OPTIGA™ Trust M MTR provisioning, please refer
66+
to our
67+
[README for Late-stage Provisioning](https://github.com/Infineon/linux-optiga-trust-m/blob/provider_dev/scripts/matter_provisioning/README.md#certificate-claiming)

examples/platform/infineon/trustm/DeviceAttestationCredsExampleTrustM.cpp

+1-1
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@
3232

3333
/* Device attestation key ids for Trust M */
3434
#define DEV_ATTESTATION_KEY_ID 0xE0F0
35-
#define DEV_ATTESTATION_CERT_ID 0xE0E3
35+
#define DEV_ATTESTATION_CERT_ID 0xE0E0
3636
#define PAI_CERT_ID 0xE0E8
3737
#define CERT_DECLARATION_ID 0xF1E0
3838

0 commit comments

Comments
 (0)