Hi, we have not seen this taking place, but clearly it is occurring. Certainly it is difficult to root cause
until a reproducible test case can be devised. The fault address and function is now isolated
so that is step toward a solution.
As with most of the binary BESL, we can advise
and recommend but the WICED support team ultimately handles features and bugfixes.
As you may know Cypherbridge uSSL SDK is running under a WICED wrapper framework,
and one aspect of its function is to manage memory resources. Is it possible this issue
relates to the content transfer? Perhaps it was mentioned before, but can you be more specific about the session context. Is it client, or server? ingress certainly. What payload or content? HTTP, proprietary?
Is there any way to wireshark the transfer at the peer end of the TLS connection?
I seems also hit this issue on SDK-3.1.2.
No particular timing pattern, the device randomly reboot after running for a couple hours.
After tracking the issue for a while, it seems hangup at below call:
result = tls_get_next_record( context, &record, timeout, TLS_RECEIVE_PACKET_IF_NEEDED );
Can someone help?