- Newest
- Most votes
- Most comments
Thank you Greg.
I don't know how I missed this, but even after combing over AWS policy statements for days, I completely missed the "Receive" action. I succeeded with Connect, Publish, Subscribe, GET, and UPDATE, but I completely overlooked Receive.
This is what happens when an Embedded/Hardware Engineer dives into AWS. I'm learning to swim in the deep end.
I feel a bit silly, but that was my problem. I enabled Receiving, and all is well. Thank you for your response. I will keep it in case I run into trouble again.
Hi MicroTech. I don't immediately see any obvious issue with your code.
Is this taken from sample code in the SimpleLink SDK? I ask because it's an old version of the AWS IoT Device SDK. Version 3.X. This was superseded by a very different design almost 2 years ago. If you are undertaking a new development, I recommend you use the latest release: https://github.com/aws/aws-iot-device-sdk-embedded-C/releases
Or you can take up the latest FreeRTOS Long Term Support (LTS) release: https://github.com/FreeRTOS/FreeRTOS-LTS/releases . FreeRTOS LTS essentially has the same C SDK libraries, but packaged with the FreeRTOS kernel.
You can find the shadow demo here: https://github.com/aws/aws-iot-device-sdk-embedded-C/tree/main/demos/shadow/shadow_demo_main
Furthermore, we have a reference implementation of the C SDK libraries and FreeRTOS for the CC3220SF: https://github.com/aws/amazon-freertos/tree/main/vendors/ti/boards/cc3220_launchpad
Including a shadow demo: https://github.com/aws/amazon-freertos/tree/main/demos/device_shadow_for_aws
Getting started guide here: https://docs.aws.amazon.com/freertos/latest/userguide/getting_started_ti.html
The 3220 is very similar to your part, so it should not be too hard to adapt as necessary.
If you instead wish to persevere with the old SDK, you can search the repo by tag of course. For example, for 3.1.5: https://github.com/aws/aws-iot-device-sdk-embedded-C/tree/v3.1.5
And find the shadow demo: https://github.com/aws/aws-iot-device-sdk-embedded-C/tree/v3.1.5/samples/linux/shadow_sample
I would suggest though that you probably need to trace through your code, from reception of the get/accepted
to figure out why the callback doesn't fire. Alternatively you may consider to create a support case.
Relevant content
- Accepted Answerasked 5 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a month ago
- Why can't I view the EventBridge trigger in my Lambda function that my CloudFormation stack created?AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 8 months ago