Part Number: CC3551E
Hello,
I have a customer who is testing the WiFi Direct P2P mode, with 2 launchpads, and he noticed that sometimes the connection will fail unless the launchpads are in a specific orientation in relation to each other. Both LP are just being desk tested so they are right next to each other.
Any suggestions on things they can try to make the connection more stable?
Munan
Yes, it is happening after the p2p_connect commands.
This is a successful connect. I've using current-sense-resistors on the 1.8V rail (Yellow trace) and the 3.3V rail (Green trace) to monitor current consumption. The initial activity is doing the role up and initial connect command. Then there's a pause, and then the connection is successful with more clear activity. I stopped the capture early, since there was no reason to continue.
In the log you can see it go through every step appropriately, with the P2P connect command executing and then several WLAN EVENT HANDLER lines about the connection associating and then being successful.
R btn! Starting WLAN cme: osi_ThreadCreate Event_Thread: thrd is running Starting software download..... received ROM init complete..... R btn!R btR !RbR btn!-------------- Download First CMD -------------- Download IniParams -------------- Wait for IniParams complete Wlan start success! Starting Device with p2p params: operational channel=6, listen channel=6, goInte nt=4 operational regulatory class=81, listen regulatory class=81 CME :CmeDeviceFlowSmValidateTransitionUserEvent: Valid state :1, ENUM(Cme_STA_ev ents_e, 0) current state ENUM(Cme_DEVICE_states_e, 0) P2P Role Up Connecting P2P CME roleType sta or p2p client doesn't exists [WLAN EVENT HANDLER]P2P Scan completed event arrived [WLAN EVENT HANDLER] WLAN_EVENT_DISCONNECT [WLAN EVENT HANDLER] Device disconnected from the AP: , BSSID: 0:0:0:0:0:0, reason code :200 P2P connect, peer address: 2e:d3:ad:a8:5a:86 security-type:6 pin:0 pin_len:0 [WLAN EVENT HANDLER] WLAN_EVENT_CONNECTING, STA is connecting [WLAN EVENT HANDLER] WLAN_EVENT_ASSOCIATED, STA associated [WLAN EVENT HANDLER] WLAN_EVENT_CONNECTING, STA is connecting [WLAN EVENT HANDLER] WLAN_EVENT_ASSOCIATED, STA associated [WLAN EVENT HANDLER] P2P GROUP STARTED Ip address was not received!! link_callback==UP starting DHCP DHCP is 0 [WLAN EVENT HANDLER] WLAN_EVENT_P2P_GROUP_STARTED P2P ,ROLE CLIENT connected. GO Bssid: 2c:d3:ad:a8:5a:85 on Channel :6 [p2p_connect app] : connected !!!! status_callback==UP, local interface IP is 10.0.0.4
This is the scope capture of the power rails when the connection never completes and then times out. You can see the initial activity at the beginning, then the 3.3V rail drops to no current and the 1.8V has a low pulse. It's almost like it thinks it's found something, and then it gives up when it should be connecting.
The log looks like it follows that pattern. The line "P2P Scan completed event arrived" happens, then a "WLAN_EVENT DISCONNECT" and the P2P Connect line, like above. Then it sits there until it times out and proves the "Timeout expired" line.
R btn! Starting WLAN cme: osi_ThreadCreate Event_Thread: thrd is running Starting software download..... received ROM init complete..... R btn!R btn!-------------- Download First CMD -------------- Download IniParams -------------- Wait for IniParams complete Wlan start success! Starting Device with p2p params: operational channel=6, listen channel=6, goIntent=8 operational regulatory class=81, listen regulatory class=81 CME :CmeDeviceFlowSmValidateTransitionUserEvent: Valid state :1, ENUM(Cme_STA_events_e, 0) current state ENUM(Cme_DEVICE_states_e, 0) P2P Role Up Connecting P2P CME roleType sta or p2p client doesn't exists [WLAN EVENT HANDLER]P2P Scan completed event arrived [WLAN EVENT HANDLER] WLAN_EVENT_DISCONNECT [WLAN EVENT HANDLER] Device disconnected from the AP: , BSSID: 0:0:0:0:0:0, reason code :200 P2P connect, peer address: 2e:d3:ad:a8:5a:86 security-type:6 pin:0 pin_len:0 [p2p_connect app] : Timeout expired connecting WiFi-Direct: 6 [WLAN EVENT HANDLER] WLAN_EVENT_P2P_GROUP_REMOVED! RoleType=3
I have also seen where the pulses continue on the green ages, but it still doesn't connect. This capture is on a much shorter time scale though.
Another timeout capture:
A capture featuring a successful connection and then I restart both boards and attempt a new connection that times out:
I kind of hard coded some commands to do all this with a button press, so it's possible there's session info that is normally added as part of entering it as a terminal command that I'm missing. Something that wouldn't cause a compilation error but might make connections more unstable.
Also, to answer your initial question all the way at the top, if I remember correctly, I couldn't connect P2P at all before the patch referenced in the other thread, so I suppose you could say I don't think I saw any of this before the patch 
Can't remember if I saw this using just keyboard inputs, I'll go back and reconfigure stuff tomorrow to test that as well. If it works well there then it's likely some support data I'm leaving out of my commands that's breaking stuff.
