• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 40 subscribers
  • Views 463 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.

LAUNCHXL-CC3235SF: Enterprise authentication through AT commands

rei
Mastermind 6155 points
Part Number: LAUNCHXL-CC3235SF
Other Parts Discussed in Thread: CC3235SF, UNIFLASH

Hi,

 

My customers are evaluating LAUNCHXL-CC3235SF and AT commands example. They were able to connect WPA2-PSK etc. They want to do Enterprise authentication through AT commands.

SDK:SIMPLELINK-CC32XX-SDK v4.30

Example:at_commands_CC3235SF_LAUNCHXL_tirtos_ccs

Question 1:

Is it possible to send a certificate or private key to CC3235 using the AT command example?

 

I think it's possible to use a certificate written with Uniflash, but I find it difficult to use a certificate sent from external server.

 

Question 2:

Customer can't connect with PEAP using the AT command example. They want to use PEAP, which does not require a certificate.

 

They used the following AT command.

AT + Wlan Connect

I have set the following, but I cannot connect.

　SecurityType: WPA_ENT

　SecurityExtEapMethod: PEAP0_XXX

 

What else should I set?

 

Regards,

Rei

  • 0
    TI__Mastermind 40965 points

    Hi Rei,

    Have they confirmed the settings they are using for WPA-Enterprise and ensured they are correct?

    I suggest they use the network_terminal demo in the SDK, modify the wlanconnect function in the code so that it uses the enterprise settings they are attempting to use, and see if it works.

    Regards,

    Michael

  • 0 in reply to Michael Reymond
    Mastermind 6155 points

    Hi Michael,

    Thank you very much. Customers are investigating what they can do with the AT Commands Example. So we are not running the Network terminal Example, but I am guessing that the PEAP in the AT Command Example is defaulted to need CA. We are hoping to set this one to none.

    And what do you think about Q1?

    Regards,

    Rei

  • +1 in reply to rei
    TI__Mastermind 40965 points

    Hi Rei,

    The customer should be able to use the AT+File* commands to transfer files including certificates and private keys.

    They can check the implementation of the AT+WlanConnect function in atcmd_wlan.c of the AT command library. Looks like it just parses the command string, and then executes a sl_WlanConnnect() directly. In general, the CC3220 will assume that your ENT method will require certs. See section 4.3.3.2 of the NWP programmer's guide: www.ti.com/lit/swru455

    Still, I suggest they either use the network terminal example to test their ENT settings, or perhaps run their AT command program in debug mode to ensure that the ENT settings appear correct when they are passed to the NWP using the sl_WlanConnect command.

    Regards,

    Michael