Other Parts Discussed in Thread: UNIFLASH,
Tool/software: Code Composer Studio
My project now has a code signing certificate signed by DigiCert. The delivery consisted of three files:
Filename Issued To
=====================================
TrustedRoot.crt DigiCert Assured ID Root CA
DigiCertCA.crt DigiCert SHA2 Assured ID Code Signing CA
mycompany.crt My Company Name, LLC
The TrustedRoot is issued to "DigiCert Assured ID Root CA" and issued by "DigiCert Assured ID Root CA" which is listed in the certificate catalog, certcatalog20181112.lst.
These files correspond very well to the TI provided certificate playground files:
dummy-root-ca-cert
dummy-trusted-ca-cert
dummy-trusted-cert
The playground uses DER files so the CRT certificates were converted to DER with OpenSSL. The DER read correctly from Windows.
So I changed out the filename and certificate names, from the playground settings to the production settings. The image built without errors but bootloading a board resulted in error -677705143.
What is that error -677705143?
In SWPU332, SimpleLink™ Wi-Fi® Certificates Handling, section 2.2 "Installing the Certificates" is says:
"When installing a DER-formatted certificate chain, the filename of the root and intermediate
certificates (that is, all but the vendor certificate) should match exactly the value of the certificate’s “Issued
To” field. The “Issued To” value makes a full path that is relative to the file system’s root folder (unless the
field value contains subfolders, the certificates should be located in the root folder). The vendor (identity)
certificate can have any path or name as long as the full path is referenced when it is used in the
application code or in Uniflash."
Since the vendor certificate name can change, I tried again and removed the comma from its name. Error -677705143.
As an experiment, I went back to the playground build, added a file called "mytest.txt" but named it "Test File Name" with initial capital letters. When the CC3220SF file list is checked, it returns "test file name" without capitals and therefore the name does not match exactly.
Question: Does the TI toolchain support certificates with upper case letters?