Open PriyankaATamhankar opened 1 year ago
Thank you for your mail.I'm on vacation right now so I can't access it, so I'll get back to you next week.Regards,Kentaro Mitsuyasu2023/02/16 1:40、PriyankaATamhankar @.***>のメール: Hello, first of all thankyou for this detailed example on configuring and provisioning the ECC chip with esp32. I was successful in configuring the chip and retrieving the public key in my example. But, when I am trying to provision I am encountering a device certificate mismatch. When I tried doing it with a fresh atecc chip there was mismatch again but what caught my eye is that it was the exact bytes that were wrong in both cases. I have my chip connected to i2c 1 of the esp dev kit. I am attaching the screenshots here. can you hint me on why a device certificate mismatch might happen?
Above are screenshots for the mismatch output for two chips. The bytes that are inconsistent are : 15-30 -> 16 bytes 200-263 -> 64 bytes 279-298 -> 20 bytes Hope to hear from you soon.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
I found out that this provision progarm lacks sign function for each batch. I'll refactor this to be able to sign from host program written in python.
Thanks for the reply but I figured out the error. There was a mismatch in the public key. I am now extending the project to have an AWS root CA
I had already created a demo for a related use case. Below is an example of signing each device certificate in Python. I'm glad if you can use it as a reference. https://github.com/kmwebnet/ECC608-MassProvisioning
Hello, first of all thankyou for this detailed example on configuring and provisioning the ECC chip with esp32. I was successful in configuring the chip and retrieving the public key in my example. But, when I am trying to provision I am encountering a device certificate mismatch. When I tried doing it with a fresh atecc chip there was mismatch again but what caught my eye is that it was the exact bytes that were wrong in both cases. I have my chip connected to i2c 1 of the esp dev kit. I am attaching the screenshots here. can you hint me on why a device certificate mismatch might happen?
Above are screenshots for the mismatch output for two chips. The bytes that are inconsistent are : 15-30 -> 16 bytes 200-263 -> 64 bytes 279-298 -> 20 bytes
Hope to hear from you soon.