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 P2P WiFi Direct Connection to PC

Other Parts Discussed in Thread: CC3200

Hi all,

I have a custom CC3200 based board that I'm attempting to use to communicate with a Windows 10 PC.  My project is based on a minimally modified p2p example.

Using an Android device, my CC3200 successfully connects and gets an IP address using the WiFi Direct settings.  Right now, I'm stuck at initializing the connection with the PC.  There is identical behaviour using the Launchpad with default p2p code.

My method for establishing the connection has been via Settings>Devices>Connected Devices>Add a device which, as you can see from the image below, the CC3200 is being discovered.

The Windows driver is also attempting to do some work...

After approximately a minute, the system fails to connect and the wifi direct driver disappears from the network connections witht he following message:

The entire debug text (from beginning to Win10 failure) is as follows:

                 *************************************************
                            CC3200 P2P Demo Application
                 *************************************************



Scan Wi-FI direct device in your handheld device
Host Driver Version: 1.0.1.6
Build Version 2.7.0.0.31.1.4.0.1.1.0.3.34
Device is configured in default state
Started SimpleLink Device: P2P Mode
Connect to cc3200-p2p-device

Any ideas as to how to get this connection established?

Thanks,

Joe

  • Hello Joe,

    The interoperability of CC3200 with Win10 over P2P has been discussed in this forum some time ago.

    It seems that even mobiles sometimes have hard time connecting with Win10.

    TheWin10 AddDevices is not working reliably as far as I tested.

    I suggest using a developer utility above the Win10 driver. Look for example apps from Microsoft Universal Windows Platform Samples. You have more control there.

    What I can also share is that P2P on CC3200 does not support replying to invites (with windows 10 device , the default P2P settings, in a specific sequence, acts as Autonomous/Persistent GO and send invite which our device can’t reply). This would be the case if you connected at least once and tries to connect again.

    Regards,

    Shlomi

  • Hi Shlomi,

    Thanks for your response.  I actually did try working from those exact platform samples and had some different results that I originally had using the Windows Add Devices feature.  The Windows sample I'm working from is "WiFiDirect" and it sniffs out the cc3200 using the "Connector" page. 

    To make more progress, I switched the security type to SL_SEC_TYPE_P2P_PIN_DISPLAY and set the security key based on the MAC (e0:e5:cf:c7:28:16 which results in a PIN of 904022 and a checksum of 3 for a concatenated keycode of 90400223).  I set this value as the P2P_SECURITY_KEY even though I believe it would be defaulted to this value.  The error code I'm now getting when trying to connect is "SL_GENERAL_ERROR_CON_MGMT_STATUS_DISCONNECT_DURING_CONNECT" (error code -109).  It sounds like this is what you were referring to with your last paragraph.  I also could have sworn I found another user who had a similar issue (albeit with an android device) and was offered a successful fix but I can't seem to track down that forum post again.

    #define P2P_REMOTE_DEVICE   "remote-p2p-device"
    //#define P2P_REMOTE_DEVICE   "JOE-PC"
    #define P2P_DEVICE_NAME     "cc3200-p2p-device"
    //#define P2P_SECURITY_TYPE   SL_SEC_TYPE_P2P_PBC
    //#define P2P_SECURITY_TYPE   SL_SEC_TYPE_P2P_PIN_KEYPAD
    #define P2P_SECURITY_TYPE   SL_SEC_TYPE_P2P_PIN_DISPLAY
    #define P2P_SECURITY_KEY    "90400223"
    #define P2P_CONFIG_VALUE    "1-0050F204-1"

    The above are my security settings for the CC3200.  Do you have any suggestion as to how to modify the CC3200 code to support replying to invites or any other way to get around this error -109 problem?

    Thanks,

    Joe