SSL handshake failure (Fatal exception 29)

jdmrcq
Posts: 1
Joined: Sat Feb 13, 2016 12:14 am

SSL handshake failure (Fatal exception 29)

Postby jdmrcq » Fri Feb 19, 2016 6:55 pm

Hi all,

I wrote a simple SSL application that sends HTTPS requests to a server. After thousands of requests, the application crashes during handshake:

Code: Select all

client handshake start.
E:M 1032
Fatal exception 29(StoreProhibitedCause):
epc1=0x4000e1b2, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000004, depc=0x00000000

 ets Jan  8 2013,rst cause:2, boot mode:(1,6)

 ets Jan  8 2013,rst cause:4, boot mode:(1,6)

wdt reset


At this point nothing run anymore, the application didn't restart properly.

I tried to disassemble my program with objdump to see which instruction fail at epc1=0x4000e1b2. But this address seems to be in BOOT ROM section according to http://esp8266-re.foogod.com/wiki/Memory_Map#bootrom.

Another point is that after every request I get the error:

Code: Select all

client's data invalid protocol
Error: SSL error 3

But it doesn't stop program execution. I have no idea what these errors means as they are printed by SDK and I didn't find any documentation about it.

I have no solution, could anyone help?
Thanks

ESP_Faye
Posts: 1640
Joined: Mon Oct 27, 2014 11:08 am

Re: SSL handshake failure (Fatal exception 29)

Postby ESP_Faye » Wed Mar 02, 2016 2:51 pm

Hi,

Please have a try with the attachment based on ESP8266_NONOS_SDK_V1.5.1.

If your problem is still unsolved, please feel free to let us know.
Attachments
libssl_ESP8266_NONOS_SDK_V1.5.1.zip
(160.52 KiB) Downloaded 159 times

DarkSide
Posts: 29
Joined: Mon Apr 06, 2015 6:51 pm

Re: SSL handshake failure (Fatal exception 29)

Postby DarkSide » Fri Jun 09, 2017 11:49 pm

SDK 2.0.0 - having same problem from time to time, it's not reproducing constantly but definetelly related to SSL

DomalysAlexis
Posts: 4
Joined: Thu Mar 02, 2017 11:01 pm

Re: SSL handshake failure (Fatal exception 29)

Postby DomalysAlexis » Tue Dec 05, 2017 11:39 pm

Hi all,

I have exactly same issue with SDK 2.1.0.
Is it plan to have a fix quickly for this issue?

Who is online

Users browsing this forum: Google [Bot] and 7 guests