TIDUE59A May 2018 – September 2020
The Wi-Fi doorlock example application needs certain files to be present in the CC3220 file system to successfully run. These files are already included as part of the premade UniFlash ImageCreator Project, but the user must program them to the serial flash prior to debugging the application using CCS.
Table 3-5 lists the files that must be on the file system for the demo and their function.
FILE | FUNCTION |
---|---|
dummy-root-ca-cert | Dummy certificate chain used to verify application binary for secure boot evaluation (must be replaced by user in production) |
dummy-trusted-ca-cert | |
dummy-trusted-cert | |
dummy_ota_vendor_cert.der | Dummy certificate used to verify the signature on each file in the OTA bundle during secure OTA update (must be replaced by user in production) |
dummy-root-ca-cert | Certificate and private key for running internal HTTP server with secure connection (HTTPS).
Note: Server can use a certificate chain in PEM format in place of the single certificate (must be replaced by user in production). |
dummy-root-ca-cert-key | |
eclipsecert.der | Root CA of Eclipse IoT MQTT server used by the client to verify the server during TLS connection |
digicertca.der | Root CA of api.dropboxapi.com used by the CC3220 to verify the Dropbox server during TLS connection |
The root CA for the Eclipse server and Dropbox can be found using a website like ssltools.com or a tool such as OpenSSL or Curl. The dummy certificates and keys are located in the SimpleLink Wi-Fi SDK under tools/cc3220_tools/certificate-playground and tools/cc3220_tools/ota-example-cert.
The dummy certificates and keys are to be used only for demo and development purposes. It is the responsibility of the developer to get actual certificates and keys for code signing and SSL/TLS when needed.