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.

CC3220: WPA2 enterprise with SL_ENT_EAP_METHOD_PEAP0_MSCHAPv2 raise callback disconnect with reason 154

Part Number: CC3220

Hi,

I am trying to implement the WPA2 enterprise connection on our device which is using the cc3220.

When using WPA2 enterprise I get the event SL_WLAN_EVENT_DISCONNECT in the callback SimpleLinkWlanEventHandler with the error reason 154. I cannot find the error reason 154 in wlan.h.

More infos:

  • I have put a dummy (correctly formated) certificate in sys/cert/ca.der
  • I have tried with both the wlan profile and the direct connection with same result.
  • The same thing works on our other product which is using cc3200 so the radius server and AP are working fine.
  • The wpa2 personnal is working fine on the cc3220

My questions:

  • What is the error reason 154? 
  • Is there something obviously wrong with my configuration below?

Here is the code snippet where I configure the connection: 

SlWlanSecParams_t secParams;

SlWlanSecParamsExt_t eapParams;

secParams.Key = "thepassword";
secParams.KeyLen = strlen("thepassword");
secParams.Type = SL_WLAN_SEC_TYPE_WPA_ENT;

eapParams.EapMethod = SL_WLAN_EAPMETHOD(SL_PEAP0, SL_MSCHAP

SL_WLAN_CC31XX_DEFAULT_CIPHER,
SL_WLAN_CC31XX_DEFAULT_CIPHER);
eapParams.User = "user";
eapParams.UserLen = strlen((const char *) eapParams.User);
eapParams.AnonUserLen = 0;



_u8 param = 1; /* 1 means disable the server authentication */

ret = sl_WlanSet(SL_WLAN_CFG_GENERAL_PARAM_ID,SL_WLAN_GENERAL_PARAM_DISABLE_ENT_SERVER_AUTH,1,&param);
if( ret )
{
ERROR_PRINT("Could not configure");
}

ret = sl_WlanProfileAdd((const signed char*) wificreds->ssid, strlen(wificreds->ssid),forced_mac, &secParams ,&eapParams,7 ,0);

  • Hi Cedric,

    When you mention that your other product works fine, if this other product uses the CC3200 then have you tried looking at the enterprise connection code and seeing if there is any difference between that and the CC3220 code you have provided above?

    As for the meaning of error code 154, I will have to look into the network processor firmware to see what can cause that error code to be thrown, since as you mention that error code is not explained in host driver header files. In the meantime, I suggest you take a look at what you have working on the CC3200 and see if you can replicate it on the CC3220.

    Regards,
    Michael
  • Hi Michael,

    Thank you for your response. I've ported the code from the cc3200 to the cc3220, so it's mostly the same thing apart from the needed change for the new sdk.

    Knowing the meaning of error 154 will help, thank you for looking!

    Best regards,

    Cédric

  • So after erasing and readding the cert files, it is working as expected. No idea what went wrong at first.
  • Hi Cedric,

    Good to know that you have resolved your issue with your enterprise connection. Perhaps the certs on the CC3220 weren't the correct ones before?

    Let me know if you have further questions or need more help.

    Regards,
    Michael