- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can anyone help with this error we encountered while debugging EAP-TLS on Wiced 3.7.0-3: "Error with TLS client handshake 5042, TLS handshake failed". It appears we did receive responses from the server including 1336-byte and 399-byte data packets but the EAP-TLS authentication sequence quits due to this error.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello John,
The error that you mentioned stands for NO DATA during the handshake process. But you have mentioned about two received packets. We were not able to recreate the issue here when we are using ThreadX RTOS. Eventually, the issue was found out to be RTOS specific where an enum was differently optimized. We also advise you to upgrade to latest SDK as there were some memory related bugs in the 3.7.0.3 version of SDK as already mentioned.