DA16200 put "Hard Fault Exception" with AT+NWHTC.

Question

Hi, I use US159-DA16200MEVZ with AT Command. When I tried acceess to AWS s3 use on AT+NWHTC(with presigned URL), DA16200 put "Hard Fault Exception". Presigned URL is long(over 1500 character) URL Data. 
 AT Command AT+NWHTC=https://xxxxxxxx....xxxxxxx,get 
 Debug Message

And, I confirmed same issue with dummy long URL. AT Command AT+NWHTC=https://aaaaaaa...aaaaaaa,get 
 Debug Message

When I used dummy short long URL, Hard Fault is not occured. 
 AT Command 
 AT+NWHTC=https://aaaaa,get

OK

+NWHTCSTATUS:3
 
 Debug Message 
 Read CA(length = 0)
Read Cert(length = 0)
Read Privkey(length = 0)

[httpc_cb_result_fn:674]httpc_result: 3, received: 0 byte, err: -16 
 
 so, I think maybe over DA16200's URL limit size. I want to solve this problem. I would greatly appreciate any feedback, guidance, or suggestions that the Renesas community can provide. 
 
 My SDK Information is... 
 Wakeup source is 0x4
[dpm_init_retmemory] DPM INIT CONFIGURATION(1)


 ******************************************************
 * DA16200 SDK Information
 * ---------------------------------------------------
 *
 * - CPU Type : Cortex-M4 (120MHz)
 * - OS Type : FreeRTOS 10.4.3
 * - Serial Flash : 4 MB
 * - SDK Version : V3.2.3.0 GEN-ATCMD
 * - F/W Version : FRTOS-GEN01-01-56c232799-004158
 * - F/W Build Time : Jun 3 2022 16:56:46
 * - Boot Index : 0
 *
 ******************************************************



System Mode : Station Only (0) 
 
 Best Regarts.

OV_Renesas · Accepted Answer

Hi There, Thank you for the reply and the feedback. Glad you are no longer facing these errors. I will update you here when the latest version (which includes the patch) will be released. If you found any answer helpful, you can accept it, this way you can help others in the community as well. If you face any other issue, feel free to raise a new ticket. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi There, Thank you for posting your question online. From the logs you have shared I can see that you are using a quite old SDK version (v3.2.3). Is there a reason you are not using the latest SDK version? We highly recommend to use the latest SDK version v3.2.6 which you can find here: https://www.renesas.com/eu/en/document/sws/da16200-da16600-freertos-sdk-v3260?r=1600096 You can find the pre-compiled images here: https://www.renesas.com/eu/en/document/sws/da16200-da16600-freertos-sdk-image-v3260?r=1600096 Regarding the issue you are facing with AT+NWHTC: The maximum url string length is 256 bytes. That is why you were facing a Hard Fault Exception. 
 You should search on the user_http_client.h file and change: 
 #define HTTPC_MAX_PATH_LEN 256 and change it to: #define HTTPC_MAX_PATH_LEN (1024 * 2) This way you can query at least 2kB URL string length. The Max request data can be set through the below definiotins in the same file: // Max size of HTTP Client's request data
#define HTTPC_MAX_REQ_DATA (1024 * 4) Note: Keep in mind that Max request data cannot be over the stack size: // Stack size of HTTP Client
#define HTTPC_STACK_SZ (1024 * 6) // Max 10KB If the HTTP buffer is increased, AT command buffer size should also be increased inside the atcmd.h file: #define TX_PAYLOAD_MAX_SIZE (1024 * 8) // Max 8KB Kind Regards, OV_Renesas

OV_Renesas · Answer

Hi There, Apologies for the delay. The issue on SDK v3.2.6 has been fixed. Please refer here: DA16200 SDK 3.2.6 unable to build - Wi-Fi - Wireless Connectivity - Renesas Community Kind Regards, OV_Renesas

OV_Renesas · Answer

Hi There, Apologies for the delay. Regarding the Error: -682 The root cause of this error was that MCU sent the AT+NWHTC command before it had received the +NWHTCSTATUS:0 response. 
 The normal sequence is like below: 1. MCU will send "AT+NWHTC=">">https://xxxxx,put,Message1" command. 2 . MCU will receive "OK" response.(Then, the MCU can send another command (for instance: AT+VER) except "AT+NWHTC" to DA16200. You cannot send again the AT+NWHTC command because it is still working) 3 .Finally, if the MCU receives "+NWHTCSTATUS:0" response, then the MCU can send next AT+NWHTC command. Please test after changing the sequence on the MCU side. Regarding the Hard Fault Error : We were not able to reproduce this error after trying multiple times. Can you please clarify if you faced the error -682 and the hard fault error with the official (pre-compiled) binary ( DA16200_IMG_FreeRTOS_ATCMD_QFN_v3.2.6.0_4MB ) or if it happened with your own custom binary? If it happened with your own custom binary, could you please provide a map file so we can investigate it? Can you also kindly share how many times (how often) are you able to reproduce the hard fault error? Finally, could you please test again after changing the sequence of the MCU? (MCU send the next AT+NWHTC command only after it has received the +NWHTCSTATUS response) Best Regards, OV_Renesas

OV_Renesas · Answer

Hi There, Apologies for the delay. Please find the attached zip with a patch we created for SDK v3.2.6 in order to fix the ASSERT vPortFree 405 Error , and hopefully the Hard Fault error as well. You will need to replace the file inside the folder path of SDK v3.2.6 as shown in the zip file. Please test it from your side and share any feedback. 20230411_assert_and_hardfault_patch.zip Kind Regards, OV_Renesas

DA16200 put "Hard Fault Exception" with AT+NWHTC.

Top Replies