This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3220SF-LAUNCHXL: Out-Of-The-Box Example

Part Number: CC3220SF-LAUNCHXL

I was using the RTOS-based Gateway Reference Design given here:

So I created the thing on IOT, downloaded the certificates and keys. However, when I debug it in CCS it gives me this problem regarding the MQTT Thread:

So, I have 2 questions. Firstly, what is the problem here? Secondly, when I build the project on CCS, I don't recall putting any network information. How did the example connect to the cloud?

  • Hi,

    You probably provisioned your CC3220 through another example such as the out of box example. Once provisioned, the CC3220 will have the Wi-Fi AP SSID and key saved on the external serial flash, so you don't need to provide it to this demo.

    The issue you are likely running into is that your certificates are not copied to the certs.h correctly. For the root CA, what file are you providing? For AWS IoT connections with the new ATS endpoint, you will need to provide the Starfield Class 2 Certificate Authority certificate. See my E2E post here for a correctly-formatted array you can copy into your certs.h:

    Please copy over that root ca cert, and also check your device cert and key to ensure that they are formatted like the root ca provided with each line having a \r\n newline.

    Let me know if you still run into your issue after checking your certs.



  • After changing the SC2 root, the error changed from -23 to -24. I tried both \r\n and \.

    Just for clarification, root CA is the SC2 key, cert.pem is certification file, and privateKey.pem is from private.pem.key from AWS right? 

  • Hi,

    The root CA cert is not directly provided by AWS. You can find the Starfield Class 2 Certificate Authority cert you need from a variety of sources, but you can just copy the C-formatted array from my linked post.

    The cert.pem is the cert file from AWS, and the private key is also the correct one from AWS>



  • I still got the same problem, but I notice that sometimes my aws console says that there are connections made.