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
Hi There,Thank you for posting your question online.
vani said: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 order to go into Provisioning mode, you will have to use the Android or IOS mobile application. Please refer on UM-WI-038 , on A.1.2 Provisioning Mode, on page: 31Regarding the error you are facing when transmitting AT commands to the DA16200:I will have to take a look and get back to you as soon as possible. In the meantime, could you please access the NVRAM via the Debug Console Interface (UART0) and check if the AWS broker configuration has been properly saved?Best Regards,OV_Renesas
hi, I cheked the nvram and got this response.
and the certificate status is as below.Is the DH parameter necessary for this to work?If necessary,how can I get it?
and getting error message as
Hi Raji,Thank you for the reply.You are using the pre-compiled images.For the generic FreeRTOS SDK v3.2.8.0 AWS:1) Download the FreeRTOS SDK v3.2..8.12) Download the AWS IoT Reference for FreeRTOS SDKInside the AWS IoT Reference for FreeRTOS there is a ReadMe file on how to integrate the AWS functionalities on the generic SDK.In order to enable the AT commands please refer on UM-WI-003, on section 4.1.1 How to Run AT-CMD on UART, on page: 26You can define the DEBUG_ATCMD macro there or in the atcmd.c/h files.Follow the steps of the UM-WI-056, on section 5.4 Importing DA16200 FreeRTOS SDK Project into e 2studio, on page: 36 so you can understand how to Import and Build your project on e2studio.We would also recommend you follow our available example first to understand how to configure the AWS Server and the DA16200 based on the following documents. 1) UM-WI-017 DA16200 AWS IoT Server Setup (renesas.com)2) UM-WI-016 DA16200 Door Lock Application Using AWS IoT (renesas.com)3)UM-WI-038 DA16200 DA16600 Getting Started with AT Command for AWS IoT (renesas.com)For our Demo, you will our Wi-Fi Provisioning App to test it:Renesas WiFiProvisioning - Apps on Google PlayFrom the log file you shared it is not clear to me how you issue the AT commands and the responses, this is the reason we need the DEBUG_ATCMD macro defined.On the log file I can see:
======================================================= argc num = 2 argv[0]: AT+AWS argv[1]: SET APP_THINGNAME vani_aws_iot ======================================================= APP SET vani_aws_iot ======================================================= argc num = 2 argv[0]: AT+AWS argv[1]: SET APP_PUBTOPIC vani_aws_iot/DeviceControl ======================================================= APP SET vani_aws_iot/DeviceControl ======================================================= argc num = 2 argv[0]: AT+AWS argv[1]: SET AWS_BROKER a3kbzziaf9hg4n-ats.iot.us-east-1.amazonaws.com ======================================================= APP SET a3kbzziaf9hg4n-ats.iot.us-east-1.amazonaws.com ======================================================= argc num = 2 argv[0]: AT+AWS argv[1]: CFG 1 mcu_door 1 0 ======================================================= ======================================================= Att[1] number : 1 Att[1] name : mcu_door Att[1] data type: 1 Att[1] MQTT type: 0 =======================================================
======================================================= argc num = 2 argv[0]: AT+AWS argv[1]: CMD MCU_DATA 1 mcu_door opened ======================================================= board feature : topicCount : 1 Count : 0, cmdNum = 1 mqtttype = 0 data type(publish)=1 call publish: 1 mcu_door opened [ERROR] [MQTT] [validatePublishParams:1756] Packet Id is 0 for PUBLISH with QoS=1. [ERROR] [MQTT] [MQTT_Publish:2193] MQTT PUBLISH failed with status MQTTBadParameter. [ERROR] [PkcsTlsTransport] [xPublishToTopic:1396] Failed to send PUBLISH packet to broker with error = MQTTBadParameter. publish (contents update) NG - topic : vani_aws_iot/DeviceControl payload: 1 mcu_door opened [/DA16200] # ======================================================= argc num = 2 argv[0]: AT+AWS argv[1]: CMD MCU_DATA 1 mcu_door opened ======================================================= board feature : topicCount : 1 Count : 0, cmdNum = 1 mqtttype = 0 data type(publish)=1 call publish: 1 mcu_door opened [ERROR] [MQTT] [MQTT_SerializePublishHeader:1995] Argument cannot be NULL: pFixedBuffer->pBuffer is NULL. [ERROR] [MQTT] [MQTT_Publish:2193] MQTT PUBLISH failed with status MQTTBadParameter. [ERROR] [PkcsTlsTransport] [xPublishToTopic:1396] Failed to send PUBLISH packet to broker with error = MQTTBadParameter. publish (contents update) NG - topic : vani_aws_iot/DeviceControl payload: 1 mcu_door opened
Hi,
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 V3.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,
Request you to please help me debug the above connection issue on flashing the custom image. Any modification need to be done in any of the sdk headers/files?
Thanks in advance,
Raji
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 V3.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
Thank you for your speedy response. I included utility as instructed in the 'Import launch configurations', gave the build, did run via 'uart_program_boot_rtos_win' and selected the lower COM port and also reset. But it gave me an error like this- failed to download error-
I also tried downloading the images through ttl macro. But again, as you mentioned it is the wrong script and I got the same error as expected-
Please help me rectify the download error. I wonder if the read is not happening correctly.
Thanks and Regards,
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 Term2) 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] menu4) 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
Thank you for your quick response.
When I tried changing the imported project to da16200_aws project, I am getting a series of include errors during build-
In the readme file suggested by you, the order of import was shown as
After reading your comment, I understand that the step 2.5 didnt happen for me when I followed step 2.2 and gave the file `~\SDK\apps\AWS\get_started_da16200\projects\da16200\`
Now as per your suggestion when I uploaded the file, da16200_aws project , it is giving build errors as mentioned above. Kindly help me with this. I did try copying the include files from the projects\da16200 folder, but errors are happening in a chain. Can you suggest a way out?
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\imgTest your configuration, and share the UART0 logs (with Timestamp if possible) so we can understand the exact issue. Best Regards,OV_Renesas
Thank you so much for your help. This time I was able to build and also flash the images.
PFA the log files for your reference.
Do let me know what I am doing wrong?
[2023-11-29 10:20:50.217] [2023-11-29 10:20:50.217] argv[0]:ATZ [2023-11-29 10:20:50.217] [2023-11-29 10:20:50.217] Usage: ATZ= [2023-11-29 10:20:52.826] [2023-11-29 10:20:52.826] argv[0]:ATE [2023-11-29 10:20:52.826] [2023-11-29 10:20:52.826] Usage: ATE=[<?>] [2023-11-29 10:21:05.199] [2023-11-29 10:21:05.199] argv[0]:AT+WFMODE [2023-11-29 10:21:05.199] argv[1]:0 [2023-11-29 10:21:05.199] [2023-11-29 10:21:05.199] Usage: AT+WFMODE=<mode> [2023-11-29 10:21:13.945] [2023-11-29 10:21:13.945] argv[0]:AT+WFJAPA [2023-11-29 10:21:13.945] argv[1]:Linksys07692 [2023-11-29 10:21:13.945] argv[2]:aryamaryjose [2023-11-29 10:21:13.945] [2023-11-29 10:21:13.945] >>> Network Interface (wlan0) : DOWN [2023-11-29 10:21:14.076] [wpa_supplicant_event_disassoc] CTRL-EVENT-DISCONNECTED bssid=e8:9f:80:35:84:aa reason=3 locally_generated=1 [2023-11-29 10:21:14.076] -- DHCP Client WLAN0: STOP(0) [2023-11-29 10:21:14.088] OK [2023-11-29 10:21:14.088] 0 [2023-11-29 10:21:14.088] [2023-11-29 10:21:14.903] [2023-11-29 10:21:14.903] >>> Network Interface (wlan0) : UP [2023-11-29 10:21:14.903] >>> Associated with e8:9f:80:35:84:aa [2023-11-29 10:21:14.999] [2023-11-29 10:21:14.999] Connection COMPLETE to e8:9f:80:35:84:aa [2023-11-29 10:21:14.999] [2023-11-29 10:21:14.999] -- DHCP Client WLAN0: SEL(6) [2023-11-29 10:21:14.999] [2023-11-29 10:21:14.999] ### User Call-back : Success to connect Wi-Fi ... [2023-11-29 10:21:17.785] -- DHCP Client WLAN0: REQ(1) [2023-11-29 10:21:17.865] -- DHCP Client WLAN0: CHK(8) [2023-11-29 10:21:18.365] -- DHCP Client WLAN0: BOUND(10) [2023-11-29 10:21:18.365] Assigned addr : 192.168.11.146 [2023-11-29 10:21:18.365] netmask : 255.255.255.0 [2023-11-29 10:21:18.365] gateway : 192.168.11.1 [2023-11-29 10:21:18.365] DNS addr : 192.168.11.1 [2023-11-29 10:21:18.365] [2023-11-29 10:21:18.365] DHCP Server IP : 192.168.11.1 [2023-11-29 10:21:18.381] Lease Time : 24h 00m 00s [2023-11-29 10:21:18.381] Renewal Time : 12h 00m 00s [2023-11-29 10:21:18.381] [2023-11-29 10:21:18.381] [2023-11-29 10:21:18.381] Usage: AT+WFJAPA=<ssid>[,<key>][,<hidden>] [2023-11-29 10:21:20.215] [2023-11-29 10:21:20.215] [/DA16200] # nvram [2023-11-29 10:21:24.215] Command-List is changed, "NVRAM" [2023-11-29 10:21:24.215] [/DA16200/NVRAM] # nvram.setenv APP_THINGNAME vani_aws_iot [2023-11-29 10:21:48.681] [/DA16200/NVRAM] # [2023-11-29 10:22:00.892] ======================================================= [2023-11-29 10:22:00.892] argc num = 2 [2023-11-29 10:22:00.892] argv[0]: AT+AWS [2023-11-29 10:22:00.892] argv[1]: SET APP_THINGNAME vani_aws_iot [2023-11-29 10:22:00.892] ======================================================= [2023-11-29 10:22:00.892] APP SET vani_aws_iot [2023-11-29 10:22:13.579] [2023-11-29 10:22:13.579] ======================================================= [2023-11-29 10:22:13.593] argc num = 2 [2023-11-29 10:22:13.593] argv[0]: AT+AWS [2023-11-29 10:22:13.593] argv[1]: SET APP_PUBTOPIC "vani_aws_iot/DeviceControl" [2023-11-29 10:22:13.593] ======================================================= [2023-11-29 10:22:13.593] APP SET "vani_aws_iot/DeviceControl" [2023-11-29 10:22:26.734] [2023-11-29 10:22:26.734] ======================================================= [2023-11-29 10:22:26.734] argc num = 2 [2023-11-29 10:22:26.734] argv[0]: AT+AWS [2023-11-29 10:22:26.734] argv[1]: SET AWS_BROKER a3kbzziaf9hg4n-ats.iot.us-east-1.amazonaws.com [2023-11-29 10:22:26.734] ======================================================= [2023-11-29 10:22:26.734] APP SET a3kbzziaf9hg4n-ats.iot.us-east-1.amazonaws.com [2023-11-29 10:22:36.159] [2023-11-29 10:22:36.160] ======================================================= [2023-11-29 10:22:36.160] argc num = 2 [2023-11-29 10:22:36.160] argv[0]: AT+AWS [2023-11-29 10:22:36.160] argv[1]: SET APP_LPORT 8883 [2023-11-29 10:22:36.160] ======================================================= [2023-11-29 10:22:36.160] APP SET 8883 [2023-11-29 10:22:44.755] [2023-11-29 10:22:44.755] ======================================================= [2023-11-29 10:22:44.755] argc num = 2 [2023-11-29 10:22:44.755] argv[0]: AT+AWS [2023-11-29 10:22:44.755] argv[1]: CFG 1 mcu_door 1 0 [2023-11-29 10:22:44.755] ======================================================= [2023-11-29 10:22:44.755] [2023-11-29 10:22:44.755] ======================================================= [2023-11-29 10:22:44.755] Att[1] number : 1 [2023-11-29 10:22:44.755] Att[1] name : mcu_door [2023-11-29 10:22:44.761] Att[1] data type: 1 [2023-11-29 10:22:44.761] Att[1] MQTT type: 0 [2023-11-29 10:22:44.761] ======================================================= [2023-11-29 10:22:44.761] [2023-11-29 10:24:23.420] [2023-11-29 10:24:23.420] ======================================================= [2023-11-29 10:24:23.420] argc num = 2 [2023-11-29 10:24:23.420] argv[0]: AT+AWS [2023-11-29 10:24:23.420] argv[1]: CMD MCU_DATA 1 mcu_door opened [2023-11-29 10:24:23.420] ======================================================= [2023-11-29 10:24:23.434] [2023-11-29 10:24:23.434] board feature : [2023-11-29 10:24:23.434] topicCount : 1 [2023-11-29 10:24:23.434] [2023-11-29 10:24:23.434] [2023-11-29 10:24:23.434] Count : 0, cmdNum = 1 [2023-11-29 10:24:23.434] mqtttype = 0 [2023-11-29 10:24:23.434] data type(publish)=1 [2023-11-29 10:24:23.434] call publish: 1 mcu_door opened [2023-11-29 10:24:24.440] [ERROR] [MQTT] [MQTT_SerializePublishHeader:1995] Argument cannot be NULL: pFixedBuffer->pBuffer is NULL. [2023-11-29 10:24:24.440] [ERROR] [MQTT] [MQTT_Publish:2193] MQTT PUBLISH failed with status MQTTBadParameter. [2023-11-29 10:24:24.440] [ERROR] [PkcsTlsTransport] [xPublishToTopic:1396] Failed to send PUBLISH packet to broker with error = MQTTBadParameter. [2023-11-29 10:24:24.440] publish (contents update) NG - topic : "vani_aws_iot/DeviceControl" payload: 1 mcu_door opened
Hi Raji,Thank you for the reply.Glad you were able to Compile and flash the images.This is not the full UART0 logs. Did you do Wi-Fi Provisioning via the Mobile application?Were you able to connect to the AWS server via the mobile application?Did you follow the AWS Server Setup document?
OV_Renesas said:1) UM-WI-017 DA16200 AWS IoT Server Setup (renesas.com)
Best Regards,OV_Renesas
Appreciate your questions. I tried to connect to AWS via the mobile app both after a manual 5sec reset press and also tried via the AT command- reset to AP. However although the app was getting connected to the DA, provisioning couldnt be done. Taking clues from your questions, I recreated a new AWS thing following the manual and did all the steps until creating a new S3 bucket to record the logs(since this option was missing in my log-in) But nothing changed.
Also when I went over https://www.renesas.com/eu/en/document/mas/um-wi-016-da16200-door-lock-application-using-aws-iot?r=1600096, In section 5.1, the MQTT_Host macro couldnt be found.
Do you thing the AWS set up is complete with creating a thing name, attaching certificates and policy, rules and publish topic? Or could it be because of any MQTT set up I missed out?
Best Regards,
As a follow up, I tired with the downloaded precompiled image to see whether I will be able to connect to any networks through the app. I could reach till the wifi provisioning this time, but again the connection to the AWS server did not happen and then the DA went to sleep mode 2. I had a hard time bringing to out from the sleep mode since I was not using an MCU at this point.
Later I wanted to give you a log file with the wifi provisioning attempts included.
[2023-12-01 14:05:41.824] [2023-12-01 14:05:41.824] argv[0]:ATZ [2023-12-01 14:05:41.824] [2023-12-01 14:05:41.824] Usage: ATZ= [2023-12-01 14:05:45.200] [2023-12-01 14:05:45.200] argv[0]:ATE [2023-12-01 14:05:45.200] [2023-12-01 14:05:45.200] Usage: ATE=[<?>] [2023-12-01 14:05:57.810] [2023-12-01 14:05:57.810] argv[0]:AT+WFMODE [2023-12-01 14:05:57.810] argv[1]:0 [2023-12-01 14:05:57.810] [2023-12-01 14:05:57.810] Usage: AT+WFMODE=<mode> [2023-12-01 14:06:07.678] [2023-12-01 14:06:07.678] argv[0]:AT+WFJAPA [2023-12-01 14:06:07.678] argv[1]:Linksys07692 [2023-12-01 14:06:07.678] argv[2]:aryamaryjose [2023-12-01 14:06:07.678] [2023-12-01 14:06:07.678] Usage: AT+WFJAPA=<ssid>[,<key>][,<hidden>] [2023-12-01 14:06:18.720] [2023-12-01 14:06:18.720] argv[0]:AT+WFJAPA [2023-12-01 14:06:18.720] argv[1]:Linksys07692 [2023-12-01 14:06:18.720] argv[2]:aryamaryjose [2023-12-01 14:06:18.720] [2023-12-01 14:06:18.720] Usage: AT+WFJAPA=<ssid>[,<key>][,<hidden>] [2023-12-01 14:06:21.610] [2023-12-01 14:06:21.610] Wakeup source is 0x4 [2023-12-01 14:06:21.610] [dpm_init_retmemory] DPM INIT CONFIGURATION(1) [2023-12-01 14:06:21.625] [2023-12-01 14:06:21.625] [2023-12-01 14:06:21.625] ****************************************************** [2023-12-01 14:06:21.625] * DA16200 SDK Information [2023-12-01 14:06:21.625] * --------------------------------------------------- [2023-12-01 14:06:21.625] * [2023-12-01 14:06:21.625] * - CPU Type : Cortex-M4 (120MHz) [2023-12-01 14:06:21.625] * - OS Type : FreeRTOS 10.4.3 [2023-12-01 14:06:21.625] * - Serial Flash : 4 MB [2023-12-01 14:06:21.625] * - SDK Version : V3.2.8.0 AWS-ATCMD Doorlock Ref. QFN GEN [2023-12-01 14:06:21.625] * - F/W Version : FRTOS-GEN01-01-f017bfdf51-006558 [2023-12-01 14:06:21.645] * - F/W Build Time : Nov 30 2023 13:23:08 [2023-12-01 14:06:21.645] * - Boot Index : 0 [2023-12-01 14:06:21.645] * [2023-12-01 14:06:21.645] ****************************************************** [2023-12-01 14:06:21.645] [2023-12-01 14:06:21.645] [2023-12-01 14:06:21.645] Not define feature and set Default EVK [2023-12-01 14:06:21.645] [2023-12-01 14:06:21.645] EVK Doorlock or Default EVK (current board=0) [2023-12-01 14:06:21.645] [2023-12-01 14:06:21.673] [2023-12-01 14:06:21.673] System Mode : Station Only (0) [2023-12-01 14:06:21.673] >>> Start DA16X Supplicant ... [2023-12-01 14:06:21.688] >>> DA16x Supp Ver2.7 - 2022_03 [2023-12-01 14:06:21.688] >>> MAC address (sta0) : d4:3d:39:38:e7:da [2023-12-01 14:06:21.688] >>> sta0 interface add OK [2023-12-01 14:06:21.688] >>> Start STA mode... [2023-12-01 14:06:21.821] [atcmd_transport_set_max_session:9479]Set max session(8), max CID(9) [2023-12-01 14:06:21.821] [atcmd_network_get_sess_info:10540]Load sess_info(len:1240, cnt:10) [2023-12-01 14:06:21.821] [2023-12-01 14:06:21.821] >>> UART1 : Clock=80000000, BaudRate=115200 [2023-12-01 14:06:21.821] >>> UART1 : DMA Enabled ... [2023-12-01 14:06:21.821] [2023-12-01 14:06:21.833] Start AT Command [2023-12-01 14:06:21.833] [UART ready notification] [2023-12-01 14:06:21.833] [atcmd_network_delete_sess_info:10594]Start [2023-12-01 14:06:22.633] RTC switched to XTAL [2023-12-01 14:06:25.993] [2023-12-01 14:06:25.993] Wakeup source is 0x4 [2023-12-01 14:06:26.011] [dpm_init_retmemory] DPM INIT CONFIGURATION(1) [2023-12-01 14:06:26.011] [2023-12-01 14:06:26.011] [2023-12-01 14:06:26.011] ****************************************************** [2023-12-01 14:06:26.011] * DA16200 SDK Information [2023-12-01 14:06:26.011] * --------------------------------------------------- [2023-12-01 14:06:26.011] * [2023-12-01 14:06:26.011] * - CPU Type : Cortex-M4 (120MHz) [2023-12-01 14:06:26.011] * - OS Type : FreeRTOS 10.4.3 [2023-12-01 14:06:26.011] * - Serial Flash : 4 MB [2023-12-01 14:06:26.011] * - SDK Version : V3.2.8.0 AWS-ATCMD Doorlock Ref. QFN GEN [2023-12-01 14:06:26.030] * - F/W Version : FRTOS-GEN01-01-f017bfdf51-006558 [2023-12-01 14:06:26.030] * - F/W Build Time : Nov 30 2023 13:23:08 [2023-12-01 14:06:26.030] * - Boot Index : 0 [2023-12-01 14:06:26.030] * [2023-12-01 14:06:26.030] ****************************************************** [2023-12-01 14:06:26.030] [2023-12-01 14:06:26.030] [2023-12-01 14:06:26.030] Not define feature and set Default EVK [2023-12-01 14:06:26.030] [2023-12-01 14:06:26.030] EVK Doorlock or Default EVK (current board=0) [2023-12-01 14:06:26.030] [2023-12-01 14:06:26.056] [2023-12-01 14:06:26.056] System Mode : Station Only (0) [2023-12-01 14:06:26.056] >>> Start DA16X Supplicant ... [2023-12-01 14:06:26.072] >>> DA16x Supp Ver2.7 - 2022_03 [2023-12-01 14:06:26.072] >>> MAC address (sta0) : d4:3d:39:38:e7:da [2023-12-01 14:06:26.072] >>> sta0 interface add OK [2023-12-01 14:06:26.072] >>> Start STA mode... [2023-12-01 14:06:26.137] [atcmd_transport_set_max_session:9479]Set max session(8), max CID(9) [2023-12-01 14:06:26.137] [atcmd_network_get_sess_info:10540]Load sess_info(len:1240, cnt:10) [2023-12-01 14:06:26.137] [2023-12-01 14:06:26.137] >>> UART1 : Clock=80000000, BaudRate=115200 [2023-12-01 14:06:26.152] >>> UART1 : DMA Enabled ... [2023-12-01 14:06:26.152] [2023-12-01 14:06:26.152] Start AT Command [2023-12-01 14:06:26.152] [UART ready notification] [2023-12-01 14:06:26.152] [atcmd_network_delete_sess_info:10594]Start [2023-12-01 14:06:27.002] RTC switched to XTAL [2023-12-01 14:06:31.928] [2023-12-01 14:06:31.928] argv[0]:ATZ [2023-12-01 14:06:31.928] [2023-12-01 14:06:31.928] Usage: ATZ= [2023-12-01 14:06:34.168] [2023-12-01 14:06:34.168] argv[0]:ATE [2023-12-01 14:06:34.168] [2023-12-01 14:06:34.168] Usage: ATE=[<?>] [2023-12-01 14:06:43.945] [2023-12-01 14:06:43.945] argv[0]:AT+WFMODE [2023-12-01 14:06:43.945] argv[1]:0 [2023-12-01 14:06:43.945] [2023-12-01 14:06:43.945] Usage: AT+WFMODE=<mode> [2023-12-01 14:07:03.243] [2023-12-01 14:07:03.243] argv[0]:AT+WFJAPA [2023-12-01 14:07:03.243] argv[1]:Linksys07692 [2023-12-01 14:07:03.243] argv[2]:aryamaryjose [2023-12-01 14:07:03.243] FAIL [2023-12-01 14:07:03.243] 0 [2023-12-01 14:07:03.243] [2023-12-01 14:07:04.043] [2023-12-01 14:07:04.043] >>> Network Interface (wlan0) : UP [2023-12-01 14:07:04.043] >>> Associated with e8:9f:80:35:84:aa [2023-12-01 14:07:04.154] [2023-12-01 14:07:04.154] Connection COMPLETE to e8:9f:80:35:84:aa [2023-12-01 14:07:04.154] [2023-12-01 14:07:04.154] -- DHCP Client WLAN0: SEL(6) [2023-12-01 14:07:04.170] [2023-12-01 14:07:04.170] ### User Call-back : Success to connect Wi-Fi ... [2023-12-01 14:07:05.562] -- DHCP Client WLAN0: REQ(1) [2023-12-01 14:07:05.562] -- DHCP Client WLAN0: CHK(8) [2023-12-01 14:07:06.077] -- DHCP Client WLAN0: BOUND(10) [2023-12-01 14:07:06.077] Assigned addr : 192.168.11.146 [2023-12-01 14:07:06.077] netmask : 255.255.255.0 [2023-12-01 14:07:06.077] gateway : 192.168.11.1 [2023-12-01 14:07:06.077] DNS addr : 192.168.11.1 [2023-12-01 14:07:06.077] [2023-12-01 14:07:06.077] DHCP Server IP : 192.168.11.1 [2023-12-01 14:07:06.077] Lease Time : 24h 00m 00s [2023-12-01 14:07:06.077] Renewal Time : 12h 00m 00s [2023-12-01 14:07:06.077] [2023-12-01 14:07:06.077] [2023-12-01 14:07:06.077] Usage: AT+WFJAPA=<ssid>[,<key>][,<hidden>] [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] =========================================== [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] [ APP-IOT AT-COMMAND ] [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] [ aws_shadow_dpm_auto_start] [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] AWS_IOT on Station Mode for "test_aws_iot" [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] ============================================ [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] [pal_app_dpm_auto_start] mcu_wakeup_port=-1, mcu_wakeup_pin=0x0 [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] default set to mcu_wakeup_port=0, mcu_wakeup_pin=0x800 [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] [2023-12-01 14:07:06.096] Root CA: O [2023-12-01 14:07:06.096] Certificate: O [2023-12-01 14:07:06.104] Private Key: O [2023-12-01 14:07:06.104] [2023-12-01 14:07:06.104] nvram read string(broker) error [2023-12-01 14:07:06.104] [2023-12-01 14:07:06.104] invalid APP feature...can't start APP Platform thread...check again [2023-12-01 14:07:06.104] [2023-12-01 14:07:06.104] [2023-12-01 14:07:06.104] >>latestStatus : 5 [2023-12-01 14:07:32.345] [2023-12-01 14:07:32.345] ======================================================= [2023-12-01 14:07:32.345] argc num = 2 [2023-12-01 14:07:32.345] argv[0]: AT+AWS [2023-12-01 14:07:32.345] argv[1]: SET APP_THINGNAME vani_aws_iot [2023-12-01 14:07:32.345] ======================================================= [2023-12-01 14:07:32.345] APP SET vani_aws_iot [2023-12-01 14:07:43.690] [2023-12-01 14:07:43.690] ======================================================= [2023-12-01 14:07:43.705] argc num = 2 [2023-12-01 14:07:43.705] argv[0]: AT+AWS [2023-12-01 14:07:43.705] argv[1]: SET APP_PUBTOPIC vani_aws_iot/DeviceControl [2023-12-01 14:07:43.705] ======================================================= [2023-12-01 14:07:43.705] APP SET vani_aws_iot/DeviceControl [2023-12-01 14:07:54.186] [2023-12-01 14:07:54.186] ======================================================= [2023-12-01 14:07:54.202] argc num = 2 [2023-12-01 14:07:54.202] argv[0]: AT+AWS [2023-12-01 14:07:54.202] argv[1]: SET AWS_BROKER a3kbzziaf9hg4n-ats.iot.us-east-1.amazonaws.com [2023-12-01 14:07:54.202] ======================================================= [2023-12-01 14:07:54.202] APP SET a3kbzziaf9hg4n-ats.iot.us-east-1.amazonaws.com [2023-12-01 14:08:22.538] [2023-12-01 14:08:22.538] ======================================================= [2023-12-01 14:08:22.538] argc num = 2 [2023-12-01 14:08:22.538] argv[0]: AT+AWS [2023-12-01 14:08:22.538] argv[1]: CFG 1 mcu_door 1 0 [2023-12-01 14:08:22.538] ======================================================= [2023-12-01 14:08:22.538] [2023-12-01 14:08:22.538] ======================================================= [2023-12-01 14:08:22.538] Att[1] number : 1 [2023-12-01 14:08:22.538] Att[1] name : mcu_door [2023-12-01 14:08:22.538] Att[1] data type: 1 [2023-12-01 14:08:22.553] Att[1] MQTT type: 0 [2023-12-01 14:08:22.554] ======================================================= [2023-12-01 14:08:22.554] [2023-12-01 14:10:09.370] [2023-12-01 14:10:09.370] [/DA16200] # net [2023-12-01 14:10:16.923] Command-List is changed, "NET" [2023-12-01 14:10:16.923] [/DA16200/NET] # cert status [2023-12-01 14:10:21.099] [2023-12-01 14:10:21.099] #1: [2023-12-01 14:10:21.099] For MQTT, CoAPs Client [2023-12-01 14:10:21.099] - Root CA : Found [2023-12-01 14:10:21.099] - Certificate : Found [2023-12-01 14:10:21.099] - Private Key : Found [2023-12-01 14:10:21.099] - DH Parameter: Empty [2023-12-01 14:10:21.115] [2023-12-01 14:10:21.115] #2: [2023-12-01 14:10:21.115] For HTTPs, OTA [2023-12-01 14:10:21.115] - Root CA : Empty [2023-12-01 14:10:21.115] - Certificate : Empty [2023-12-01 14:10:21.115] - Private Key : Empty [2023-12-01 14:10:21.115] - DH Parameter: Empty [2023-12-01 14:10:21.115] [2023-12-01 14:10:21.115] #3: [2023-12-01 14:10:21.115] For Enterprise (802.1x) [2023-12-01 14:10:21.115] - Root CA : Empty [2023-12-01 14:10:21.115] - Certificate : Empty [2023-12-01 14:10:21.130] - Private Key : Empty [2023-12-01 14:10:21.130] - DH Parameter: Empty [2023-12-01 14:10:21.130] [2023-12-01 14:10:21.130] TLS_CERT for ATCMD [2023-12-01 14:10:21.130] - TLS_CERT_01 : Empty [2023-12-01 14:10:21.130] - TLS_CERT_02 : Empty [2023-12-01 14:10:21.130] - TLS_CERT_03 : Empty [2023-12-01 14:10:21.130] - TLS_CERT_04 : Empty [2023-12-01 14:10:21.130] - TLS_CERT_05 : Empty [2023-12-01 14:10:21.130] - TLS_CERT_06 : Empty [2023-12-01 14:10:21.130] - TLS_CERT_07 : Empty [2023-12-01 14:10:21.147] - TLS_CERT_08 : Empty [2023-12-01 14:10:21.147] - TLS_CERT_09 : Empty [2023-12-01 14:10:21.147] - TLS_CERT_10 : Empty [2023-12-01 14:10:21.147] [2023-12-01 14:10:21.147] [/DA16200/NET] # top [2023-12-01 14:10:24.282] Command-List is changed, "ROOT" [2023-12-01 14:10:24.282] [/DA16200] # [2023-12-01 14:10:45.691] ======================================================= [2023-12-01 14:10:45.691] argc num = 2 [2023-12-01 14:10:45.691] argv[0]: AT+AWS [2023-12-01 14:10:45.691] argv[1]: CMD RESET_TO_AP [2023-12-01 14:10:45.691] ======================================================= [2023-12-01 14:10:45.706] [2023-12-01 14:10:45.706] board feature : [2023-12-01 14:10:45.706] TO AP resetMode [2023-12-01 14:10:45.706] [2023-12-01 14:10:45.706] DA16200 factory reset AP mode = 1 ("AP_ONLY").... [2023-12-01 14:10:45.785] .....[app_set_customer_ap_configure] set AP config mode = 1 [2023-12-01 14:10:45.834] [2023-12-01 14:10:45.834] apps_reboot_ap_mode Customer configuration ... [2023-12-01 14:10:45.834] . [2023-12-01 14:10:45.899] default_ssid = "Dialog_DA16200" ..., ap_config_param->ssid_name [2023-12-01 14:10:45.899] [2023-12-01 14:10:45.899] PW = 1234567890 [2023-12-01 14:10:45.899] [2023-12-01 14:10:45.899] PW = 1234567890 completed [2023-12-01 14:10:45.899] . [2023-12-01 14:10:45.899] apps_reboot_ap_mode IPADDR_CUSTOMER... [2023-12-01 14:10:45.914] .... [2023-12-01 14:10:45.947] apps_reboot_ap_mode customer_dhcpd_flag == DHCPD_CUSTOMER.. [2023-12-01 14:10:45.947] ...... [2023-12-01 14:10:46.058] OK [2023-12-01 14:10:46.058] [2023-12-01 14:10:46.058] [2023-12-01 14:10:46.461] [2023-12-01 14:10:46.461] Wakeup source is 0x0 [2023-12-01 14:10:46.461] [dpm_init_retmemory] DPM INIT CONFIGURATION(1) [2023-12-01 14:10:46.461] [2023-12-01 14:10:46.461] [2023-12-01 14:10:46.461] ****************************************************** [2023-12-01 14:10:46.477] * DA16200 SDK Information [2023-12-01 14:10:46.477] * --------------------------------------------------- [2023-12-01 14:10:46.477] * [2023-12-01 14:10:46.477] * - CPU Type : Cortex-M4 (120MHz) [2023-12-01 14:10:46.477] * - OS Type : FreeRTOS 10.4.3 [2023-12-01 14:10:46.477] * - Serial Flash : 4 MB [2023-12-01 14:10:46.477] * - SDK Version : V3.2.8.0 AWS-ATCMD Doorlock Ref. QFN GEN [2023-12-01 14:10:46.477] * - F/W Version : FRTOS-GEN01-01-f017bfdf51-006558 [2023-12-01 14:10:46.493] * - F/W Build Time : Nov 30 2023 13:23:08 [2023-12-01 14:10:46.493] * - Boot Index : 0 [2023-12-01 14:10:46.493] * [2023-12-01 14:10:46.493] ****************************************************** [2023-12-01 14:10:46.493] [2023-12-01 14:10:46.493] [2023-12-01 14:10:46.493] Not define feature and set Default EVK [2023-12-01 14:10:46.493] [2023-12-01 14:10:46.493] EVK Doorlock or Default EVK (current board=0) [2023-12-01 14:10:46.493] [2023-12-01 14:10:46.523] [2023-12-01 14:10:46.523] System Mode : Soft-AP (1) [2023-12-01 14:10:46.523] [2023-12-01 14:10:46.523] >>> DHCP Server Started [2023-12-01 14:10:46.523] >>> Start DA16X Supplicant ... [2023-12-01 14:10:46.571] >>> DA16x Supp Ver2.7 - 2022_03 [2023-12-01 14:10:46.571] >>> Add SoftAP Inteface (softap1) ... [2023-12-01 14:10:46.571] >>> MAC address (softap1) : d4:3d:39:38:e7:db [2023-12-01 14:10:46.587] >>> softap1 interface add OK [2023-12-01 14:10:46.587] >>> AP Operating Channel: 1(2412) [2023-12-01 14:10:46.587] [2023-12-01 14:10:46.587] >>> Network Interface (wlan1) : UP [2023-12-01 14:10:46.587] >>> BSS Isolate Disabled [2023-12-01 14:10:46.587] [2023-12-01 14:10:46.587] Soft-AP is Ready (d4:3d:39:38:e7:db) [2023-12-01 14:10:46.634] [atcmd_transport_set_max_session:9479]Set max session(8), max CID(9) [2023-12-01 14:10:46.634] [atcmd_network_get_sess_info:10540]Load sess_info(len:1240, cnt:10) [2023-12-01 14:10:46.652] [2023-12-01 14:10:46.652] >>> UART1 : Clock=80000000, BaudRate=115200 [2023-12-01 14:10:46.652] >>> UART1 : DMA Enabled ... [2023-12-01 14:10:46.652] [2023-12-01 14:10:46.652] Start AT Command [2023-12-01 14:10:46.652] [UART ready notification] [2023-12-01 14:10:46.652] [atcmd_network_delete_sess_info:10594]Start [2023-12-01 14:10:46.652] [2023-12-01 14:10:46.652] =========================================== [2023-12-01 14:10:46.652] [2023-12-01 14:10:46.652] [ APP-IOT AT-COMMAND ] [2023-12-01 14:10:46.652] [2023-12-01 14:10:46.652] [ aws_shadow_dpm_auto_start] [2023-12-01 14:10:46.652] [2023-12-01 14:10:46.652] ============================================ [2023-12-01 14:10:46.669] [2023-12-01 14:10:46.669] [2023-12-01 14:10:46.669] [pal_app_dpm_auto_start] mcu_wakeup_port=-1, mcu_wakeup_pin=0x0 [2023-12-01 14:10:46.669] [2023-12-01 14:10:46.669] default set to mcu_wakeup_port=0, mcu_wakeup_pin=0x800 [2023-12-01 14:10:46.669] [2023-12-01 14:10:46.669] [2023-12-01 14:10:46.669] Root CA: O [2023-12-01 14:10:46.669] Certificate: O [2023-12-01 14:10:46.669] Private Key: O [2023-12-01 14:10:46.669] [2023-12-01 14:10:46.669] shadow item count = 0, (integer#=0, string#=0, float#=0) [2023-12-01 14:10:46.669] nvram read shadow config error [2023-12-01 14:10:46.669] [2023-12-01 14:10:46.669] invalid APP feature...can't start APP Platform thread...check again [2023-12-01 14:10:46.669] [2023-12-01 14:10:46.669] [2023-12-01 14:10:46.669] >>latestStatus : 5 [2023-12-01 14:11:18.395] AP-STA-CONNECTED 22:d2:bd:fb:84:4b [2023-12-01 14:11:18.395] [2023-12-01 14:11:18.395] ### User Call-back : Success to connect Wi-Fi ...
I have 3 questions at this point-
1. After the hard reset and provisioning, is it possible to wake up the DA from the DPM sleep mode in any simple way? Since AT commands were not exactly possible in this mode, by giving any external pulses to the RT_WAKEup pin is it supposed to come out? I had to use power switch and reset and finally a reloading of the image to get it working.
2. Why is it not listing any networks when I used our custom image, a hard reset and invoked provisioning as shown in this image?
3. Please go through the attached log and help me understand if any issues with AWS IOT setup. The device shadow and certificates are attached to the thing as shown here.
I hope you will be able to give me a solution and get my DA working finally
Hi Raji,Thank you for the replies.Let me take a look on these and I will get back to you as soon as possible.I will try to do a detailed step by step on how to use the AWS with the Mobile application.Best Regards,OV_Renesas
Thank you for your kind reply. I thought of also sharing the console o/p which I received on trying the initial hard reset. Hope this along with the logs will help you to understand the DA not listing the available ssid's on using the built image. Please note that I have not made any changes in the SDK file other than enabling the debug logs as instructed.
Hi Raji,Thank you for the reply and apologies for the delay.I wanted to let you know that we are still working on this.Best Regards,OV_Renesas
Any updates? I wanted to let you know that the AWS configuration is good since I could manage to publish via a different sdk once. I tried provisioning via the setup command using teraterm. Not using the provisioning app. I tried downloading the sdk again from your server using this link- https://www.renesas.com/us/en/products/wireless-connectivity/wi-fi/low-power-wi-fi/da16200mod-ultra-low-power-wi-fi-modules-battery-powered-iot-devices?downloads-title-filter=image#design_development. Its now back to MQTT bad parameters and packet id 0. Could you please help me with this SDK issues since I'm really falling on time.
Appreciate a speedy response.
raji
With the sdk which helped me connect to MQTT and publish to AWS , the AT command window is not becoming active now. Even on reset, the +init 0 is not getting displayed or commands cannot be typed (higher port, baud rate:115200). Including a screenshot of the response i recieved on flashing the image -
Please provide me with an SDK which can connect to the AWS and in which MQTT connection is possible. This is urgent. Request your speedy response
Regards,
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: 26Best Regards,OV_Renesas
Hi Raji,I forgot to mention the following:On the same file (config_generic_sdk.h file) please make sure you have defined the __SUPPORT_MQTT__ macro on the line 850. You will need to do this only if you define the __SUPPORT_AWS_IOT__ macro as well
// AWS IoT Platform define from project config #if defined ( __SUPPORT_AWS_IOT__ ) || defined ( __SUPPORT_AZURE_IOT__ ) #undef __SUPPORT_DPM_MANAGER__ // use or not DPM manager #if defined ( __SUPPORT_WIFI_CONCURRENT__ ) #undef __SUPPORT_WIFI_CONCURRENT__ #define __SUPPORT_FACTORY_RST_APMODE__ // Factory reset AP-Mode #undef __SUPPORT_FACTORY_RST_STAMODE__ // Factory reset STA-Mode #endif #if !defined ( __SUPPORT_FACTORY_RESET_BTN__ ) #define __SUPPORT_FACTORY_RESET_BTN__ #endif #if defined ( __SUPPORT_WPS_BTN__ ) #undef __SUPPORT_WPS_BTN__ // WPS button #endif #if !defined ( __SET_WAKEUP_HW_RESOURCE__ ) #define __SET_WAKEUP_HW_RESOURCE__ // RTC_WAKEUP_PIN1/2 #endif #if defined ( __SUPPORT_WIFI_PROVISIONING__ ) #undef __SUPPORT_WIFI_PROVISIONING__ // AP Provisioning operation with Phone APP #endif #if defined ( __SUPPORT_HELLO_WORLD__ ) #undef __SUPPORT_HELLO_WORLD__ #endif #if defined ( __SUPPORT_MQTT__ ) #undef __SUPPORT_MQTT__ // Support MQTT #endif #if defined ( __SUPPORT_IPERF__ ) #undef __SUPPORT_IPERF__ // IPerf #endif #if !defined ( __SUPPORT_OTA__ ) #define __SUPPORT_OTA__ #endif #if defined ( __SUPPORT_WEBSOCKET_CLIENT__ ) #undef __SUPPORT_WEBSOCKET_CLIENT__ // websocket client #endif #endif // __SUPPORT_AWS_IOT__
Hi OV_Renesas,
Thank you for your reply. __SUPPORT_ATCMD__.and __SUPPORT_MQTT__ are defined in the file. uart1 and 2 messages are also present. But there is also an error which is status 5, ( ATCMD_Status_need_configuration = 5). How do I correct this in the file. Also could the MQTT publish error be due to this? Why exactly is the pBuffer is Null error is coming when trying t publish?