Hi,
I have finished building the sample code. Am trying to connect the kit to my router to try if it can throw anything to AWS. How to connect it to the router (AP)?
Hope to hear from you soon.
Thanks.
Regards,
Nelson
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.
I assume sample code is the QCLI_demo with wlan and Ecosystem options to connect to AWS.
In case of QCLI_demo follow instructions from section "5.3.16.5.2 Connection procedure" of document "QCA402x Programmers Guide 80-Y9381-2".
In case of Onboard_demo follow instructions from section "5.3 Run onboard AWS demo" of document "QCA402x (CDB2x) Development Kit User Guide 80-YA121-140"
Hi Raja,
I am following the document 80-ya121-140-qca402xcdb2x_development_kit_user_guide.pdf on page 50 section 5.3 step 5. It says that upon successful onboarding, we should be able to see a place that lets us key our Home AP credentials. But that screen/dialog box doesn't appear.
In this link https://developer.qualcomm.com/project/qca4020-onboard-with-cloud-mode, at section "Launch the Smartphone App", at step 5, it also mentions the same thing. But the screen/dialog box doesn't appear.
So how do we connect our board to AWS account?
Hope to hear from you soon.
Regards,
Nelson
Hi Raja,
I am able to connect my CDB20 board to my router already. It has to be done using this settings at the IDE Project -> Properties -> C/C++ Build -> Behavior tab, at the Build (Incremental build) you set t 4020 2 1 1 cdb. This is indicating the Onboarding mode to be WiFi.
But I have a question to ask again. After the board is connected to my AWS account (I set the AWS credentials into the code in file aws_util.h and cert_buf.h), the sensor data is dumped to which service of AWS? How can I know the sensor data has reached AWS already?
Hope to hear from you soon.
Regards,
Nelson
Hi Raja,
I saw this in my serial console...
Hi Raja,
I modified something and recompile using t 4020 2 1 1 cdb. I tried to scan using the Android App. Now it no longer can let me do onboarding using WiFi. There's no place for me to key in my home AP credential anymore. Why is it like this?
Actually, can we let the board connect to our home AP automatically?
Regards,
Nelson
Hi Raja,
I know why it can't be onboarded using WiFi. In oder to onboard using WiFi, my phone Location (GPS) needs to be turned on.
Yupppie...
Now, let's go back to the issue
It seem strange as the device is throwing "unable to resolve IP address" for AWS END Point.
Could you try create another thing in US-WEST-2 Region and let us know if you are still facing the same issue.
From the logs till data, the only reason we suspect is either network blocking the AWS connection or AWS build environment issue.
I assume you have set the ARM TOOLCHIAN PATH/ NEWLIBPATH and TOOLLIBPATH correctly ?
Kindly also verify the issue with mobile hotspot or non-corporate network.
Hi Raja,
In my Project->Properties->C/C++ Build->Environment
my NEWLIBPATH is C:\Program Files\GNU Tools Arm Embedded\6 2017-q2-update\arm-none-eabi\lib\thumb\v7e-m
my TOOLLIBPATH is C:\Program Files\GNU Tools Arm Embedded\6 2017-q2-update\lib\gcc\arm-none-eabi\6.3.1\thumb\v7e-m
my PATH contains C:\Program Files\GNU Tools ARM Embedded\6 2017-q2-update\bin
let me go through section 3.9.1 of document "80-ya121-140-qca402xcdb2x_development_kit_user_guide.pdf" to see if I miss out anything. Is the section of the document correct? Or you have other reference?
Regards,
Nelson
Hi Raja,
I have gone through the document's steps. I don't miss out anything. I tried with other router. It can be connected to my aws.
The router I used previously (let's call it router A) can't let the CDB20 board connect. I am able to use the same router (router A) to connect to the Internet using my phone and PC.
Is there anything in CDB20 board that stops it from connect to aws using router A? I ask you this because this router A will always be used for our IoT projects. It has to work with CDB20. Other boards from other vendors, can connect through router A to aws.
Hope to hear from you soon.
Regards,
Nelson
Hi Raja,
I tried with the US-east-1 region, also it can't work. I attach the log here...
Hi Raja,
Is there anything in CDB20 board that blocks it from connecting to the Internet through a DLink router?
Hi Raja,
I saw one of your posts here...
https://developer.qualcomm.com/forum/qdn-forums/hardware/qca4020-qca4024...
I think mine is quite similar with this. I've checked, my router is set to WPA2. For the link above I saw that you use CLI_demo to do the settings. But I am using onboard_demo, how can I let it connect and use my router to connect my aws since it's WPA2?
Hope to hear from you soon.
Regards,
Nelson
hi Raja,
It looks like it's the WPA2 issue. I used the QCLI_demo to try to connect to my AWS, it works after I followed the CLI method to solve the WPA2 issue. You can refer to below log.
But how to solve this WPA2 issue if I am using onboard_demo?
By default onboard demo fetches the list of saved wifi credentials in your mobile and connects to the selected Access Point.
From the logs , we can confirm the device is able to successfully connect and get DHCP address.
Onboard: SSID=LO_Work2
Onboard: PassWD=xxxxxxxx
Onboard: CONNECTING to SSID:LO_Work2, pwd:xxxxxxxx
Onboard: Setting SSID to LO_Work2
Onboard: Connecting to :LO_Work2
Onboard: WLANCB: dID:1, cbID:0, val:1
Onboard: Connect event on devId:1 val:1
Onboard: devid - 1 1 CONNECTED MAC addr 80:26:89:30:54:10
Onboard: WLANCB: dID:1, cbID:0, val:16
Onboard: Connect event on devId:1 val:16
Onboard: 4 way handshake success for device=1
Can you try with the CLI verified "testAP", even I tried locally in my setup with southeast-1 and us-east-1. In both cases no issues were seen, I am able to update and modify the shadow using Co-coordinator and end point.
Since the issue is "unable to resolve address" the reason should be either lack of internet connection or DHCP server not started on device.
Please soft restart multiple times during the issue to check any timing compatibility.
Also, check with any non corporate network or hotspot to confirm network is not blocking.
Hi Raja,
Using QCLI_demo, I am able to connect to aws (iot.ap-southeast-1.amazonaws.com), as shown in my last post. But using onboard_demo, it can't.
At QCLI_demo, I used command prompt to solve the WPA2 issue. You can see below. But I think the onboard_demo has doesn't go through the process of solving the WAP2 issue, does it?
Hi Raja,
I have tried 3 times using the QCLI_demo to resolve a39obhn7hjv632.iot.ap-southeast-1.amazonaws.com, it really works. But it just doesn't work with onboard_demo. Do you know why?
<p>Its been long time you are still facing the issue, I apologize for taking this long in debugging.<br>Kindly share us your SDK zip file with changes, I will verify locally and check for issue.<br><br> </p>
Hi Raja,
How to share the SDK with you? Can I have your email to attach the zip file?
You can upload SDK into google driver and share details with us.