• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 40 subscribers
  • Views 299 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

LAUNCHXL-CC3235S: CC3235S

LAUNCHXL-CC3235S: EAP-TLS (Enterprise Security) Abort with SimpleLink 3.40.00.05 (30 Jan 2020)

David Dykhuizen
Intellectual 320 points
Part Number: LAUNCHXL-CC3235S

The original forum question under:

https://e2e.ti.com/support/wireless-connectivity/wifi/f/968/t/887569

 is locked.

Was wondering if there was any progress in reproducing or further guidance/information can be provided?

Original question:

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.]


Thanks,
/David

 


  • 0
    TI__Mastermind 40965 points

    Hi David,

    I had managed to get a Cisco AP with EAP capability but was unable to replicate your issue. I was able to use my CC3235 with the latest SDK and servicepack to connect with EAP-TLS without the abort.

    That being said, I had a radius server setup that wasn't quite the same as what you had. Instead of freeradius v3 that you are running, I have freeradius v2.2.8 running on my linux PC connected to my EAP AP. I was hoping to setup a freeradius v3 server to be able to use your config files, but unfortunately have not been able to do so yet.

    Still, using my freeradius v2 server I can confirm that there shouldn't be an issue connected with EAP-TLS. Being able to fully use your config would let us know whether the issue is specific to your config, despite having not changed it since the previously-working SDK release.

    If you are able to do so, I suggest you try using freeradius v2, to see if you still encounter that abort.

    Regards,

    Michael