Failed to publish to a topic in AWS

Question

I'm using DA 16200mod evk to publish to a topic in Aws. Downloaded the DA16200 firmware image '.ttl' script from DA16200_DA16600_AWS_v3.2.8.0_ATCMD_img. Have sent the three certificates files over uart.I have done the configurations using AT commands sending from nRF52840 DK uart, as follows 
 
 "AT+AWS=SET APP_THINGNAME tap-pet-nrf-device 
 " ); 
 
 ( "AT+AWS=SET AWS_BROKER a3kbzziaf9hg4n-ats.iot.us-east-1.amazonaws.com 
 " ); 
 ( "AT+AWS=SET APP_LPORT 8443 
 " ); 
 ( "AT+AWS=CFG 0 sample/pet 0 0 
 " ); 
 ( "AT+AWS=CMD MCU_DATA 0 sample/pet 25 
 " ); 
 
 All in station mode 
 
 As per the manual after this a factory reset is to be done which leads to soft ap mode and waiting for provisioning. But here it is entering soft AP mode but no wfscan happens or provisioning cannot be done.

In teraterm I'm getting it with error as shown below (when nrf transmits AT COMMANDS to DA)

Raji · Accepted Answer

Hi OV_Renesas, 
 Thank you for the reply and wish you a great year ahead! 
 The issue was indeed a network connection one and could rectify it once shadow was configured. Appreciate all the support extended. 
 Regards, 
 Raji

OV_Renesas · Answer

Hi Raji, Thank you for the reply and apologies for the delay. 
 Raji said: Thank you for you detailed reply. I followed your instructions, copied the AWS IoT package in the '~SDK\apps\' directory of the DA16200_DA16600 Generic SDK V 3.2.8.1, defined the DEBUG_ATCMD macro and built it using e2 studio. But after flashing the new images in the DA16200MOD-DeVKT through teraterm using the macro and .ttl script generated as shown below,

I believe you used the wrong .ttl script to flash your board.
Note: Please refer on UM-WI-056 on how to add the launchers on the e2studio.
On section 5.5.2 Changing Flash Configuration, on page:44.
Follow the same steps but select the following:

When the Build operation is finished, you should see the following

Now you can select the Run External Tools button

and select the uart_program_boot_rtos_win launcher.

After that, specify the COM on the console and make sure that the device is not in DPM sleep (Reset it) after that the firmware should be downloaded automatically:

Then please try to test the UART1 via AT commands.

Best Regards,
OV_Renesas

OV_Renesas · Answer

Hi There, Apologies for the delay. 
 vani said: and getting error message as 
 
 The MQTTBadParameter error code corresponds to if the packet would exceed the size allowed by the MQTT spec or if a subscription is empty. It seems that you did not issue the MQTT request with the correct parameters. Please refer on User Manual DA16200 DA16600 Getting Started with AWS&reg; IoT Using AT Command UM-WI-038 It would be helpful for us if you could share the whole UART0 and UART1 log files so we can understand the AT commands sequence you used and how you configured your DA16200. With the Wi-Fi Provisioning Mobile application were you able to do provisioning and access the AWS server? Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Raji,

Thank you for the reply.
From the screenshot you shared, I have two points to highlight:
1) I do not think you have imported the correct project to work on AWS. You should import the da16200_aws project.
2) In order to use the launchers, you will have to select the project you want to download.
Please check below screenshot:

If the launcher keeps on not working, you can do the same approach manually from Tera Term.
Follow the steps below:
1) Open Tera Term
2) Connect to UART0, with Baudrate set at 230400 as shown below:

3) Trigger the RST switch and then type 'reset'
The MaskROM Bootloader should load:

Type Enter one type to make sure that we are into the [MROM] menu
4) Type 'loady 0'. so we can load first the FBOOT image.

5) Go on File-->Transfer-->YMODEM-->Send...

6) Navigate onto the path of your projects images, and select FBOOT image.
7) In case the operation is not successful, please type again 'loady 0' and repeat the steps.
8) If the operation is successful, then type 'loady 23000' and follow the same steps to load the FROTS image into the board.
9) When both images have been downloaded successfully, you can type 'reboot' and the firmware should start running.

Best Regards,
OV_Renesas

OV_Renesas · Answer

Hi Raji, Thank you for the reply. I believe you did not copy/replace the correct files inside the SDK. I have integrated the AWS reference SDK into the SDK v3.2.8.1. 
 Please download files from the following URL: < https://upload.hdedrive.com/ui/renesas.com/dl/SB1701187602-6bbb18a6-03d8-4ef1-b79a-94ab5bb0d78e > 
 * This URL requires guest identity verification as well as download password authentication. Once the identity verification passed, the verification step can be skipped for up to 30 days in the same browser. 
 Download Password: 9!/M5cMEVJjR 
 This URL will expire on December 12, 2023 6:06 PM (UTC+02:00) I was able to Import the da16200_aws project and enable AT commands and made sure I defined the DEBUG_ATCMD macro in the atcmd.h file. I then downloaded the Images and tested the AT commands, it works on my side. Please download the SDK from the link above and use the da16200_aws project. The Images of the da16200_aws project can be found on the following path: ...DA16200_DA16600_SDK_FreeRTOS_v3.2.8.0_1_AWS\apps\AWS\get_started_da16200\projects\da16200\img Test your configuration, and share the UART0 logs (with Timestamp if possible) so we can understand the exact issue. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Raji, Thank you for the replies and apologies for the delay. We are sorry for any inconvenience our delay has created. Glad you were able to use the MQTT commands and publish to AWS. Regarding the AT command window: On UART0 during boot-up, you should see the following (highlighted) lines, that would show that the UART2 has been initialized for AT commands: If you are not able to see those lines, it means that you have not enabled the AT commands on the generic SDK. In order to do that, please go on config_generic_sdk.h file: You will have to define the __SUPPORT_ATCMD__ . If the __SUPPORT_MQTT__ macro is defined (which is defined by default), the MQTT client feature would be enabled on the image created by the building process. This is documented on the UM-WI-003 , on section 4.1.1 How to Run AT-CMD on UART, on page: 26 Best Regards, OV_Renesas

Failed to publish to a topic in AWS

Top Replies