AWS IoT

[Aleksa]

Hi all,

I have an issue with integration of the AWS IoT in my source code. The example works for me. I've tried to copy&paste the example code to my project (I delete my main.c and use example code), but aws_iot_connect() resets the chip without any RTT output on the reason why the chip was reset. 

I remember there was some nrfjprog command to read the reset reason, but I'm unable to find that command at the moment. Does someone know what command it is? 

Also do you have some general ideas on why would aws_iot_connect() cause this behavior?

Cheers

Aleksa

[Charlie]

Hi Aleksa,

The application codes should not work if you only paste the codes in main.c to your project. The AWS IoT example is a whole solution based on NCS, not just codes in main.c. I suggest you adapt your project into the sample instead.

You can find all nrfjprog commands from this page, just check which one you used before.

Best regards,

Charlie 

[Aleksa]

Hi Charlie,

I don't understand why wouldn't it work? My project and the AWS IoT example use the same NCS. The only reason to fail would have to be related to Kconfig. I've made sure that the configuration in my project is the same as the one in the example though (parts relevant to the AWS IoT). 

I've searched all over nrfjprog documentation, and I wasn't able to find the specific command that I've mentioned in the post. It would literally print out a string explaining the cause of last reset.

Best Regards,

Aleksa 

[Charlie]

Hi Aleksa,

I do not know why you need to enable it before, but for AWS IoT usage, this is not necessary and should not be enabled.

Best regards,

Charlie 

[Aleksa]

Hi Charlie,

As I've said it works when I disable this config, but here:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/libraries/networking/aws_iot.html
It's clearly stated that AWS IoT can work with this config enabled.

Best Regards,

Aleksa

[Aleksa]

I have another question (maybe I can open a ticket for it).

I have connected to the aws mqtt broker from the aws mqtt test client, mqtt.fx app and from my device. 

I have subscribed with the device to all of the default shadow topics available via config. I have also subscribed to the two default custom topic(my-custom-topic/example(2)). When I publish from either of the three clients that I use, aws iot test client and mqtt.fx receive the message if they are subscribed to a specific topic. 
I was expecting same behavior for my nrf9160dk device - I expect "AWS_IOT_EVT_DATA_RECEIVED"  event to happen whenever I publish to a topic that nrf9160dk is subscribed to.

However this event seems to happen randomly completely. (out of sync with my publishes)

Any idea on what could cause this?

Best Regards,

Aleksa

[Aleksa]

If someone comes here with a similar issue, here is a similar topic:
https://devzone.nordicsemi.com/f/nordic-q-a/79784/subscribing-in-assert-tracker-v2/330201#330201

Setting lower keepalive time made it receive all of the messages. 

[Charlie]

Hi Aleksa,

It is possible to use the general Cloud API to cover the difference of AWS/AZURE/NRF_Cloud, but just enabling CLOUD_API is not enough. You can refer to the nRF9160: Cloud client sample about how cloud API is used, but for the nRF9160: AWS IoT sample, it does not use cloud API, you should not enable it here.

Best regards,

Charlie