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.

p2p sign in error

Other Parts Discussed in Thread: CC3200, UNIFLASH, CC3200-LAUNCHXL

I'm trying to get acquainted with the p2p example and keep getting a couple of errors.

The first is,

[GENERAL EVENT] - ID=[-102] Sender=[5]

which, according to the documentation is SL_CON_MGMT_STATUS_UNSPECIFIED

the second is,

[GENERAL EVENT] - ID=[-109]SENDER=[5]

which is,

SL_CON_MGMT_STATUS_DISCONNECT_DURING_CONNECT

Is there a way to deal with these? I read from a thread in early 2016 that the p2p connection success rate is 65%. Is that still the case?

I'm on windows 7 w/svc pack 1. x64, CCS 6.2 w/svc pack 1.0.1.6-2.7.0.0 and sdk 1.2

thanks

  • Hi,

    According information in release note for latest service pack (1.0.1.6-2.7.0.0), was p2p connection success rate improved. From release notes:
    MCS00130040 - Negotiation with other peer not always successful at first chance (fix increased to >90%).

    Jan
  • Hello Greg,

    As Jan stated, statistics for P2P has been improved to over 90% with latest SP.

    These errors indicate you cannot make a P2P connection with the peer device.

    What device are you using on the other side?

    Can you connect to it with another device over P2P?

    What is the procedure you are following?

    Are you able to see cc3200-p2p-device on the other device?

    Regards,

    Shlomi

  • Hello Shlomi, thanks you for the reply.

    On the other side I am using an android phone (galaxy S5 android v 6.01) and have also tried with a galaxy tab 2 running android v 4.2.2.

    I can connect both android devices to each other via p2p and can see the cc3200 with 100% consistency.

    Procedurally, from CCS I am running the example p2p program by clicking debug then resume (f8)

    In Tera Term this is my initial display;

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

    Scan Wi-FI direct device in your handheld device
    Host Driver Version: 1.0.1.6
    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 cc3200-p2p-device
    Device has found a p2p device
    Device has found a p2p device

    I've added a couple of lines to the event handler to make sure the cc3200 is seeing other devices although I don't know exactly what devices it sees.

    On my phone (android v 6.01) the cc3200 shows up as a found device and I tap it to connect. and get the following display on Tera Term;

    Device has found a p2p device
    Device has received a negotiation request
    [GENERAL EVENT] - ID=[-102] Sender=[5]

    line one of the preceding looks like the device found something new. line two is what I added to the event handler to confirm the request is being received. And line three is my very consistent error.

    Does any of this shed light? I know there's a way to confirm what devices the cc3200 finds but I can't find any documentation about how to implement it.

    Thanks again

     

  • Hello,

    I guess the p2p device found message was added to SL_WLAN_P2P_DEV_FOUND_EVENT case, right?

    If so, please look at the comments in this case regarding how to print the name of the peer device.

    Then, you get a negotiation request from peer device but for some reason it is dropped by SimpleLink.

    From the printout, I can see build version is 2.0.7.0.31.0.0.4.1.1.5.3.3.

    This is ROM version which means you do not have service pack programmed which may explain many things.

    Can you verify you program latest 2.7.0.0?

    The printout should be Build Version 2.7.0.0.31.1.4.0.1.1.0.3.34.

    Also, what launch pad board version are you using?

    Regards,

    Shlomi

  • You are correct, I added the device found message to confirm that the cc3200 was finding p2p devices.

    I don't see the case you reference for printing the device name but I got it done with the following;
    UART_PRINT("Device has found a p2p device \n\r");
    UART_PRINT(pSlWlanEvent->EventData.P2PModeDevFound.go_peer_device_name);
    UART_PRINT("\n\r");
    I'm sure there's a more elegant way but this will do for now.

    Uniflash was a torture when I first started with this and apparently I didn't get the service pack properly flashed. I went back and re-did that and now have build version 2.7.0.0.31.1.4.0.1.1.0.3.34.

    I think my board version is 4.1, at least that's what is printed on the PCB under "CC3200-LAUNCHXL".

    Even with the proper build version connection is erratic. The follow is the results of four attempts to connect, only one of which was successful.

    1st try
    *************************************************
    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
    Device has found a p2p device
    [TV]47LM6400-UA
    Device has found a p2p device
    [Phone] SAMSUNG-SM-G900V
    Device has found a p2p device
    DIRECT-7C-HP ENVY 5660 series
    Device has received a negotiation request
    [GENERAL EVENT] - ID=[-102] Sender=[5]



    2nd try

    *************************************************
    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
    Device has found a p2p device
    [TV]47LM6400-UA
    Device has found a p2p device
    [Phone] SAMSUNG-SM-G900V
    Device has received a negotiation request
    [GENERAL EVENT] - ID=[-109] Sender=[5]
    [GENERAL EVENT] - ID=[-109] Sender=[5]
    Device connected as station event triggered
    CC3200 Device IP : IP=192.168.49.153
    Send TCP packets from your handheld device to CC3200's IP
    Received TCP packets successfully
    Test passed, exiting application...


    3rd try

    *************************************************
    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
    Device has found a p2p device
    DIRECT-7C-HP ENVY 5660 series
    Device has found a p2p device
    [TV]47LM6400-UAVY 5660 series
    Device has found a p2p device
    [Phone] SAMSUNG-SM-G900Veries
    Device has received a negotiation request
    [GENERAL EVENT] - ID=[-109] Sender=[5]
    [GENERAL EVENT] - ID=[-109] Sender=[5]
    [GENERAL EVENT] - ID=[-109] Sender=[5]


    4th try

    *************************************************
    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
    Device has found a p2p device
    Roku 3 - 417
    Device has found a p2p device
    DIRECT-7C-HP ENVY 5660 series
    Device has found a p2p device
    [TV]47LM6400-UAVY 5660 series
    Device has found a p2p device
    [Phone] SAMSUNG-SM-G900Veries
    Device has received a negotiation request
    [GENERAL EVENT] - ID=[-102] Sender=[5]

    It seems the -102 error is always a killer and with the -109 error it was still able to connect on one occasion.

    Respectfully,

    Greg
  • Hello Greg,

    Is it possible on your side to get sniffer logs?

    Regards,

    Shlomi

  • Sniffer logs are a whole new learning curve for me that I think I'll have to take a look at.

    In any event I think I found the primary problem, at least the -102 error. My phone was signed onto a 5ghz router and once I changed that to a 2.4ghz connection I no longer experience the -102 error. I can now connect to the cc3200 with far more regularity. When the -109 error comes up a hard reset seems to resolve the issue, at least for the next 5 to 10 connection attempts.

    At this point I think we can call this issue resolved. I very much appreciate your help here, specifically bringing to my attention the improperly applied service pack and the sniffer log suggestion.

    Respectfully,

    Greg

  • Sure Greg, no problem.

    High thumbs for the catch.

    I am closing the thread for now. In case you have updates on this specific issue, I highly recommend you open a new thread and link to this one as reference.

    Regards,

    Shlomi