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 sample not working

Other Parts Discussed in Thread: UNIFLASH, CC3200, CC3100

Hello,

I am working the CC3200 LaunchPadLX dev board Rev 4.1.  I am running the p2p sample application connecting with a few different Android phones, Samsung S4 mini, Samsung S5 and a Nexus 6.  When I first got everything setup, I was able to connect to my Samsung S4 twice.  Since then I have not been able to connect to any of these devices.  I have 4 dev boards and I am using two separate development machines.  All boards tested have been patched using Uniflash with the lastest service pack.  

There appears to be three different scenarios for the failures:

1. No SL_WLAN_P2P_DEV_FOUND_EVENT.  This is the least common failure.

2. No SL_WLAN_P2P_NEG_REQ_RECEIVED_EVENT.  This is the most common failure. This results in a hang on IS_P2P_REQ_RCVD(g_ulStatus) in WlanConnect()

3. No SL_NETAPP_IPV4_IPACQUIRED_EVENT.  Second most common failure.  This results in a hang on IS_IP_ACQUIRED(g_ulStatus) in WlanConnect.

Tests have been performed with Android's sample WiFiDirectActivity and with the native WiFi Direct connection method. The Android devices can connect to each other without issue.

The p2p sample is unmodified beyond the name.  It puts out this info to console:

Scan Wi-FI direct device in your handheld device
Host Driver Version: 1.0.0.1
Build Version 2.0.7.0.31.0.0.4.1.1.5.3.3
Device is configured in default state
Started SimpleLink Device: P2P Mode
Connect to TEST-P2P-E10298

What I am doing wrong?  Any ideas?

  • Hi Justin,

    The build version you have provided is not the latest.
    Can you try programming the device again? the latest version is 2.2.0.1.1.2.0.2.1.0.3.23 for a production device.

    more details can be found in here:www.ti.com/.../cc3100sdk

    Release notes: processors.wiki.ti.com/.../CC31xx_Release_Notes

    I hope it will solve your issues.

    Best Regards,
    Nir Nitzani
  • Hi Nir,

    Thank you for the response. I am using the CC3200 and not the CC3100. These are different parts, correct?

    The SDK I used was from here:

    www.ti.com/.../CC3200SDK

    Thanks,
    -justin
  • I see the service pack is for both. I am testing now. I will let you know.
  • OK, the problem has disappeared for the phones in question. Thank you for the sanity check!
  • Hi Justin,

    The CC3200 and CC3100 are different parts. the networking part is identical in both parts. the CC3200 includes an MCU M4 cortex for user host application.

    The same service pack is been used for the CC3100 and CC3200 - the link you pointed is the correct one.
    Once you program the device you should get the build version I've provided before.


    Best Regards,
    Nir
  • Hi Nir,

    I figured that out. Thanks. What started this problem is:

    I have an Android 4.2.2 build that when the phone takes on GO, it creates a group listed in Remembered Groups. If I disconnect the dev board using the phone's native GUI and try to reconnect the dev board again, it will fail. The only way I have found to get the dev board to connect again is to remove the group that Android created from the initial successful connection.

    Do you have any insight into why this happens and what I might be able to do to prevent or recover from this scenario from the dev board? Is there way for me to rejoin a group I have been disconnected from?

    Thanks,
    -justin
  • Hi Justin,

    I've got several questions for you, in order  to try and get to the bottom of this issue:

    1. Can you please describe if the P2P menu in your phone is in scanning state after you are disconnecting the dev board?
    2. Are you also configuring fast connection policy in addition to auto connection policy?
    3. Are you able to provide a wireless sniffer capture of the GO wifi channel during the connection attempt?

    Thanks,
    Alon

  • Hi Alon,

    Thank you for the reply.  We are working on getting fast connection running.  I think that will solve the problem.  I am answering the questions for future reference.

    1. The process is, scan, connect (the Android 4.2.2 phone must be the GO so a group is made), disconnect the CC3200 through the Android interface, power cycle the CC3200 (because the demo only works for one connection), and try to reconnect.  When scanning from the Android phone, the CC3200 will appear but when you try to connect, the CC3200 doesn't get an IP address and the Android phone gives up.

    2. We are in the process of setting this up.  I believe this will likely resolve the issue.

    3. A packet capture would be great but I don't have that capability at the moment.  If we are still having problems once we get fast connection working, we will pursue it.

    Thanks,

    -justin

  • Hi Justin,

    Thanks for the update.
    I am closing the thread for now, if issue still exist please open a new thread and add a link to this one for reference.

    Thanks,
    Alon