Failed to publish to a topic in AWS

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: 31
Regarding 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 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

Hi,

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.

Thanks and Regards,

Raji

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

Hi,

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.

Thanks and Regards,

raji

Hi, 

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,

raji

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

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?

Regards,

raji

Hi Raji,

Happy New Year!
Apologies for all the delay but the Renesas Engineering Team was OOO the last 2 weeks.

Raji said:

But there is also an error which is status 5, ( ATCMD_Status_need_configuration = 5).  How do I correct this in the file.

Is this an error when you are trying to compile the project or while trying to run the project?

Raji said:

  Also could the MQTT publish error be due to this?

Yes, that would be possible. If the Macros where not properly defined on the images you used, you would not be able to use the MQTT publish feature.

Raji said:

Why exactly is the pBuffer is Null error is coming when trying t publish?

This could be related with a Heap exhaustion issue. How much data are you trying to publish at one time? 
On the FreeRTOSConfig.h file, you can increase the Heap. And you should handle the memory allocation on every task you have created on your project.

#ifdef INTEGRATION_WITH_RTOS_HEAP
#define configTOTAL_HEAP_SIZE					( ( size_t ) ( 300 * 1024 ) )
#else
#define configTOTAL_HEAP_SIZE					( ( size_t ) ( 200 * 1024 ) )
#endif

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

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