Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable


First ,I power down group owner device after creating a connect between a group owner device and a client device,Then,I power on the group owner device,if the interval time between power down and power on  is shortly(the client device is not "P2P interface down  status"),the group owner device can not automatic connect the client device, if the interval time between power down and power on  is long(the client device is "P2P interface down  status"),the group owner device can automatic connect the client device. Why?  if this,how to let the client device`s interface status is down after the group device power down or on?

the group owner device will create a persistent group using the "p2p_go_start"function after powering on every time.

SDK 3.1.2

BCM9WCDUSI09 platform   

0 Likes
7 Replies
Anonymous
Not applicable

can you help me?

Thanks you !

0 Likes
Anonymous
Not applicable

until now,it still is a problem  !

can you help me ?

Thanks!

0 Likes

Sorry for the delay. Let me look into this and get it scheduled. 

0 Likes
Anonymous
Not applicable

Thank you very much !

0 Likes
Anonymous
Not applicable

Dear gangi:

      do you test this problem ? I still not solve the problem . I very much hope that get your help .

thanks a lot

0 Likes

Hi there,

I've just tried this out on the WICED SDK 3.1.2 on a 43362 board with connection to a Galaxy S5.

This was the process I followed:

1. On WICED board

>> p2p_go_start p test 12345678 1

>> p2p_registrar_start pbc

2. On Galaxy S5

Connect to WICED_P2P from the Wi-Fi Direct menu

3. On WICED board

>> p2p_peer_list (Shows Galaxy S5 in screenshot)

4. Reset the WICED board

5. Set up the group owner again right after reset on WICED

>> p2p_go_start p test 12345678 1

6. Check peer list

>> p2p_peer_list

The Galaxy S5 doesn't show up for the first few tries but it does after a few seconds.

Could you check again in the short interval reset scenario if the client shows up later?

Thanks,

Jaeyoung

p2p_peer.PNG

Anonymous
Not applicable

Hi there,

On my BCM9WCDUSI09 board still has the problem.

I've just tried this out on the WICED SDK 3.1.2 on a BCM9WCDUSI09 board with connection to an other  BCM9WCDUSI09 board.

This was the process I followed:

1. On a WICED board (as a Group Owner,IP 192.168.10.2)

>> p2p_go_start p test 12345678 1

>> p2p_registrar_start pin 81818884

2. On an other WICED board (as a Client,IP 192.168.10.4)

>> p2p_connect pin 81818884

now the board can connect to DIRECT-test.

3. On an other WICED board (as a Client,IP 192.168.10.4)

>>status

it is up.

>> ping 192.168.10.2

it can sucess.

QQ截图20150511092817.png

4. Reset the WICED board (as a Group Owner,IP 192.168.10.2)

5. Set up the group owner again right after reset on WICED

>> p2p_go_start p test 12345678 1


Note:the interval between step 4 and step 5 is short ,about 1 seconds.


6. On an other WICED board (as a Client,IP 192.168.10.4)

>> status

the client is up,

>> ping 192.168.10.2

but it is timeout.

QQ截图20150511093801.png

if on step 5, after reset,when set up the group owner again, change the channel num what different the last.  The problem will resolve.

I do not Why ?

Could you test this?

Thanks.

0 Likes