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.

CC3200 STA mode WPA password length

Other Parts Discussed in Thread: CC3200

Hello again,

I have been working with the CC3200 and have really liked what it does.  But I do have a couple questions I couldn't find the answer to.  What is the maximum length of a WPA password in STA mode?  It has a limit of 32 bytes when in AP mode, the smartConfig apps limit it to 32 bytes, but nowhere does it explicitly say that the limit is 32 bytes for WPA in STA mode.

I have used the API to create a profile with a 37 byte password as well as to simply connect with 37 byte password (without making a profile).  Both of these tests were successful, but I don't know if they were simply a buffer overrun that happened in my favor.

Can someone verify what the maximum WiFi password length is that can be stored in a profile on the CC3200?  If it is more than 32 bytes, will the POST variables be changed in the production silicon to allow more than the 32 bytes?

Additionally, it has been asked a couple times, but I haven't found a clear answer.  Do the CC3200 parts themselves have a MAC address?  Will I need to allocate a block of MAC addresses to program into CC3200 parts purchased for custom boards?

Thanks!

  • Hi Trevor,

    I apologies for the delayed response on this thread.

    • The maximum password length supported for WPA security is 63 characters (this is limited by security protocol itself). I will share the feedback on smartconfig app with the team.
    • The http post token already supports upto 64 byte token value.
    • CC3200/CC3200 parts have pre assigned MAC address. User don't need to allocate the MAC address to use the device however if different pool of MAC is need user can flash the new MAC address on the device also.

    Regards,

    Ankur

  • Hi Ankur,

    Thank you very much for this information. However, I think I need to give some clarification. The 32 character POST variable I was referring to was __SL_P_P.C. In SWRU368 on page 89 table 12-20, it says that the value for the Security Key token must be smaller than 32 characters. Additionally, it fails to create the profile (through the profiles_config.html page included) if it has a password greater than 32 characters, it just doesn't create the profile. However, in the code for the password text box, the HTML says the maxlength is 64. This is where I get a little confused as to if the limit on the post variable was intended to be 32 or 64. It seems the NWP wants it to be less than 32, and if this was not intended to be the case, will it be changed later on?

    As for the MAC addresses, this is exactly what I have been looking for.

    Thanks,
    Trevor
  • I would like some clarification on this as well. The iOS Wi-Fi SmartLink Starter app imposes a limit of 32 characters, as Trevor has stated. It should be 64 characters for full WPA2 security support. What/where is it that is imposing this limit, beyond the app user interface, and can this be remedied. Seems like imposing this limit kind of goes against the "usability" claim of Smart Config.
  • Hi Trevor,

    I apologies for the delayed response.

    We are able to reproduce the issue you are seeing with the pre defined post token for the password key (__SL_P_P.C). The length of the token is indeed limited to 32 bytes.
    As a workaround you can use the user defined tokens (for SSID, security type and password) to save a profile if the expected password length is more that 32 characters.

    Regards,
    Ankur
  • Hi Mark,

    32 character password is the limitation of current smartconfig library and app. Simplelink device doesn't have any such limitations and supports the password upto 63 characters for WPA security.
    I have share the feedback with the team on this and we will fix it in next release.

    Regards,
    Ankur
  • Hi Ankur,

    Thank you for looking in to this for me. You can see my confusion with mixed lengths depending on what method used to program the profile. Thank you for your help and submitting feedback to get it fixed where possible.

    Trevor
  • TI,

    When is the "next release" this issue will be fixed in going to happen?

    Thank you.
    -Mark
  • I would also be interested in knowing if this will be changed/fixed. I noticed in the 'Known-issues' section in one of the documents, it acknowledges the issue, but side-steps it with a work around. Is this something that is in the plan to be fixed?