Forums - QCA4020 Onboard_Demo awsiot cert provide

2 posts / 0 new
Last post
QCA4020 Onboard_Demo awsiot cert provide
chau-nm
Join Date: 12 Feb 17
Posts: 8
Posted: Thu, 2018-08-02 08:42

I'm building the Onboard awsiot demo for QCA4020 (CBD20) evaluation kit.

Now I got problem when the device does shadow connects, the return error is -6 (SSL_CONNECTION_TIMEOUT)

The cert I provided in "cert_buf.h" was in PEM format  like below

uint8_t aws_thing_cert[] =
{"-----BEGIN CERTIFICATE-----\n"\
"MIIDWTCCAkGgAwIBAgIUafLBL4SZYEk1J6znQma8DrXmoecwDQYJKoZIhvcNAQEL\n"\
....
"GpzNw02GFaVTcaQzgIfXICbkQFfDYHsNpCKWaaLYokB+rCEAhMMwPWihzl7k\n"\
"-----END CERTIFICATE-----"};
 
In cert_buf.h, I saw comment to use sharkSSLparse before providing the cert but in "load_cert_file" function the cert is type is QAPI_NET_SSL_PEM_CERTIFICATE_WITH_PEM_KEY_E and ca_list type is QAPI_NET_SSL_PEM_CA_LIST_E.
 
So I have to question:
1. Is the aws_calist is the rootCA for AWS?
2. Do I provide the correct format for the certificate or I have to provide in a single line statemnt like the document 80-ya121-140?
  • Up0
  • Down0
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Thu, 2018-08-02 11:19

1. Is the aws_calist is the rootCA for AWS?
>> Yes, aws_Calist is the rootCA from AWS.

2. Do I provide the correct format for the certificate or I have to provide in a single line statement like the document 80-ya121-140?
>> You need to provide the contents of certificate in a single statement as mentioned in our document 80-ya121-140.

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.