Other Parts Discussed in Thread: CC3235S, UNIFLASH
We have been using the CC3235S as a Wi-Fi Client to Connect to an Access Point utilizing EAP-TLS (Enterprise Security) with the SDK 3.20.00.06 (28 Jun 2019) without issue.
Upon upgrading the SimpleLink SDK to 3.40.00.05 (30 Jan 2020) we are now receiving the following abort/error information upon attempting to establish a connection (sl_WlanConnect) via the callback "SimpleLinkFatalErrorEventHandler":
[ERROR] - FATAL ERROR: Abort NWP event detected: AbortType=2, AbortData=0x24c (588)
[Note: We have not changed the Application software (MCU image) or the certificates (/sys/cert/ca.der, /sys/cert/client.der, /sys/cert/private.key) only the underlaying SDK bin.]
1.) Can TI provide information on what the Abort Data is attempting to tell us
2.) What information can be shared in the handling of EAP-TLS between these SDK versions (i.e. can not see any change information indicating a non-backwards compatible EAP-TLS handling being introduced).
A breakdown between the last 4 SDK versions:
TI SDK |
EAP-TLS : Connection |
3.20.00.06 (28 Jun 2019) |
Works – Successful Connection as designed |
3.20.01.01 (11 Sept 2019) |
Works – Successful Connection as designed |
3.30.00.04 (4 Oct 2019) |
Fails ([ERROR] - FATAL ERROR: Abort NWP event detected: AbortType=2, AbortData=0x24c (588)) |
3.40.00.05 (30 Jan 2020) |
Fails ([ERROR] - FATAL ERROR: Abort NWP event detected: AbortType=2, AbortData=0x24c (588)) |
Thanks,
/David