Forums - Firmware for AWS iot

16 posts / 0 new
Last post
Firmware for AWS iot
firdaus
Join Date: 11 Dec 17
Posts: 14
Posted: Wed, 2018-01-03 02:18

Hi everyone,

1) Where can I get the firmware for AWS IoT for QCA4010 module?

2) How can I get the  " raw_flashimage_AR401X_REV6_IOT_MP1_hostless_ap+sta_mcc+aws_singleband_4bitflash.bin "  file?

 
  • Up0
  • Down0
jbhanu Moderator
Join Date: 6 Feb 17
Posts: 77
Posted: Wed, 2018-01-03 05:10

Hi ,

For AWS image you need to

6.3.2 AWS IoT demo build To build the AWS IoT demo:

1. Set up the environment variables required for building the binary image. source sdkenv.sh

2. Build the IoT demo. cd demo/aws/ make

3. Select the tunable_input file and modify this file according to the build image type:

cd .../../tool/ cp tunable/tunable_input_mp1_hostless_4bitflash.txt tunable/tunable_input.txt

echo OP_FLAVOR 9 >> tunable/tunable_input.txt

echo "export FLASH_FLAVOR=\"_IOT_MP1\"" >> tunable/tunable_input.txt

4. Run Qonstruct. ./qonstruct.sh --qons tunable/follow below instruction to build image.

This will generate raw_flashimage_AR401X_REV6_IOT_MP1_hostless_ap+sta_mcc+aws_singleband_4bitflash.bin .

Please download the UG from below link

https://developer.qualcomm.com/download/qca4010/qca4010-sdk-2-1-user-gui...

In this please check section 6 AWS IoT demo. 

While compile you may get one  error. So please do below modification in sdk AWS demo Makefile.

  Under LDFLAGS, change -Tsdk_shell.ld to aws_demo.ld. 

Hope it clarifies your doubt. 

 

Regards

jyotiranjan

  • Up0
  • Down0
firdaus
Join Date: 11 Dec 17
Posts: 14
Posted: Wed, 2018-01-03 17:31

Hi,

I got the error as below during step "2. Build the IoT demo. cd demo/aws/ make"

/home/firdaus/xtensa/XtDevTools/install/tools/RE-2013.3-linux/XtensaTools/bin/xt-ld: cannot open linker script file sdk_shell.ld: No such file or directory
make: *** [/home/firdaus/qca4010-tx-2-1_qca_oem_1-5mb-mesh.git/target/image/aws_demo.out] Error 2
what should I do?
  • Up0
  • Down0
jbhanu Moderator
Join Date: 6 Feb 17
Posts: 77
Posted: Wed, 2018-01-03 18:04

In Makefile replace sdk_shell.ld with aws_demo.ld under LDFLAGS.

  • Up1
  • Down0
firdaus
Join Date: 11 Dec 17
Posts: 14
Posted: Wed, 2018-01-03 20:22

Hi,

How do I solve the below error?

Error: the "KF=home/firdaus/xtensa/XtDevTools/install/tools/RE-2013.3-linux/XtensaTools" core is not in the current Xtensa core registry.
 
You need to either specify the name of a registered Xtensa core (with the --xtensa-core option or the XTENSA_CORE environment variable) or
specify a different registry of Xtensa cores (with the --xtensa-system option or the XTENSA_SYSTEM environment variable).
make: *** [/home/firdaus/aws/target/image/aws_demo.out] Error 2
 
Is it related to below setup? And where I need to put this setup:
 
3. Setup environment variables for command line access to Xtensa tools.
 
a. Place the following variables either in a script to be sourced later, or in a .bashrc (or equivalent) startup file.
 
NOTE:The value to fill in for <TOOL_INSTALL_DIR> is the value recorded from step 2-a. As an example: /home/user/xtensa
 
 export XTENSA_INST=<TOOL_INSTALL_DIR>
 export XTENSA_CORE=KF
 export XTENSA_ROOT=$XTENSA_INST/XtDevTools/install/builds/RE-2013.3-linux/KF
 export XTENSA_SYSTEM=$XTENSA_ROOT/config
 export XTENSA_TOOLS_ROOT=$XTENSA_INST/XtDevTools/install/tools/RE-2013.3-linux/XtensaTools
 export LM_LICENSE_FILE=~/license.dat
 export PATH=$PATH:$XTENSA_TOOLS_ROOT/bin
 
b. Either source the script created in 3-a, or open a new terminal if using .bashrc in 3-a.
 
c. Test the environment variable settings by compiling a simple program.
 echo 'main(){}' > test.c
 xt-xcc test.c

 

  • Up0
  • Down0
firdaus
Join Date: 11 Dec 17
Posts: 14
Posted: Thu, 2018-01-04 18:03

Hi,

How do I solve the problem below?

/home/firdaus/xtensa/XtDevTools/install/tools/RE-2013.3-linux/XtensaTools/bin/xt-ld: cannot open linker script file aws_demo.ld: No such file or directory
make: *** [/home/firdaus/QCA4010.TX.2.2_QDN/target/image/aws_demo.out] Error 2
The problem come after I replace sdk_shell.ld with aws_demo.ld in Makefile under LDFLAGS.
 
Thanks.
  • Up1
  • Down0
jbhanu Moderator
Join Date: 6 Feb 17
Posts: 77
Posted: Thu, 2018-01-04 23:17

Hi It is presnt inside SDK 

root@ubuntu12:~/QCA4010.TX2.1/QDN/QCA4010.TX.2.1_QDN/target/demo/aws# ls
aws_demo.ld  aws_iot_src  Makefile  Makefile.aws  sample_apps  timer_interface.h
 
Which SDk are you using?I have downloaded from QDN . It is TX2.1 SDK .
 
Regards
Jyotiranjan 
  • Up0
  • Down0
firdaus
Join Date: 11 Dec 17
Posts: 14
Posted: Fri, 2018-01-05 00:10

 

Yes I have all that file.

How about the sdkenv.sh file. Do I need to setup anything?

  • Up0
  • Down0
firdaus
Join Date: 11 Dec 17
Posts: 14
Posted: Sun, 2018-01-07 18:35

Hi,

1) How can I setup the QCA4010 module to connect with wifi?

2) Any specific command do I need to use?

  • Up1
  • Down0
firdaus
Join Date: 11 Dec 17
Posts: 14
Posted: Mon, 2018-01-08 20:12

Hi,

1) How can I access to the command below for aws iot setup?

wmiconfig --connect HWAP
wmiconfig --ipdhcp
getcert b8486.cert.bin 192.168.0.104 -p 1443 -s crtmn
wmiconfig --aws shadow a3eo5p112nq5b9.iot.us-west-2.amazonaws.com 8883 MyDevice crtmn
2) Do I need to use ath_console.exe?
  • Up0
  • Down0
svegesna Moderator
Join Date: 7 Jun 17
Posts: 20
Posted: Tue, 2018-01-09 03:43

Hi,

In answer to your question, this command is  used to Connect to the AWS IoT server and update the value of shadow.

Are you not able to connect to AWS server using this command?


Before that you need to create an AWS profile. Please follow below procedure:

1.       Create an AWS profile in https://console.aws.amazon.com/console/home

2.       Select My Security Credentials under username in the top right section of the window.

3.       Select Get started with IAM users, select Add user, give a username and select Programmatic access.

4.       Create a group and set permission for demo as add user to group.

5.       The credentials.csv file is created. Download the file and move it to the DUT.

This is the one time setting which binds the Amazon AWS credentials to this device.

Thanks,

Santhosh

  • Up0
  • Down0
firdaus
Join Date: 11 Dec 17
Posts: 14
Posted: Wed, 2018-01-17 19:10

Hi all,

How to run the SharkSSLParseCert.exe as intruction below? Because when I run the SharkSSLParseCert.exe it just pop-up for a second.

5. Create a new IoT certificate.
When the new certificate is created, the IoT web interface gives you a chance to save keys
and certificate files, which are PEM-encoded. Saving the public key is not necessary in this
case, and only the private key and the certificate are required. Then use the
SharkSSLParseCert.exe to convert the key and certificate to the binary file.
  • Up0
  • Down0
svegesna Moderator
Join Date: 7 Jun 17
Posts: 20
Posted: Thu, 2018-01-18 12:09

Hi Firdaus,

In the sdk demo code sharkssl certificates were present in the below location.
qca4010-tx-2-2-qca_oem_ext.git/target/tool/linux/
SharkSslParseCAList
SharkSslParseCert
SharkSslParseKey

In the QCA4010 user guide, see certificate  management demo
1. Convert certificate to SharkSSL binary format.
a. Generate binary certifcate file.

SharkSSLParseCert  foo.pem  foo.key -b foo.cert.bin

b. Generate binary CA List file.
SharkSSLParseCAList  -b  foo.calist.bin  foo.pem

Thanks,

Santhosh

 

  • Up0
  • Down0
jbhanu Moderator
Join Date: 6 Feb 17
Posts: 77
Posted: Fri, 2018-01-19 23:43

Please look at Certificate mangement demo in UG. Please follow UG and it will help you a lot . Are you able to run demo now?

  • Up0
  • Down0
linn.htun.thaw
Join Date: 3 Aug 17
Posts: 2
Posted: Fri, 2018-03-16 00:36

Hi, 

I am also encountering the same problem, if you have already solved it, please let me know how you did. Thanks

  • Up0
  • Down0
linn.htun.thaw
Join Date: 3 Aug 17
Posts: 2
Posted: Fri, 2018-03-16 00:36

Hi, 

I am also encountering the same problem, if you have already solved it, please let me know how you did. Thanks

  • 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.