cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Wi-Fi Combo

MiSa_2357281
New Contributor II

Hello all,

I'm trying to check about it connect the P2P-GC with 43907(using test/console wiced sample apps) to Autonomous GO on 43455(Linux).

It can connect the P2P-GC with 43907 to Autonomous GO on 43455 with 2.4GHz CH.

However, it can not connect to Autonomous GO on 43455 with 5GHz CH.

## It do not found 5GHz p2p device on test/console app(using p2p_connect pbc command ).

Test step

1. Start 43455 p2p GO(36 CH) and dhcp server on linux kernl 4.9 and using FMAC release at 2019-05-08

2. enter wps_pbc connamd with p2p-go i/f using wpa_cli on 43455 linux

3. enter this command on test/console apps on WICED 43907 devise

    p2p_connect pbc

** Do not found p2p device(43455) from 43907 device

4. Start 43455 p2p GO(6 CH) and dhcp server on linux kernl 4.9 and using FMAC release at 2019-05-08

5. enter wps_pbc connamd with p2p-go i/f using wpa_cli on 43455 linux

6. enter this command on test/console apps on WICED 43907 devise

    p2p_connect pbc

** The 43907 device can found p2p-go device and connect it.

##Please see attached file.

## The Country code is not set on both device ( Country code is default)

It do not seems to occur the issue on 43455 when it connect Nexus6 p2p to 43455 p2p-GO(5GHz).

So,there is no issue for 43455 p2p-GO.

And It can connect to AP(5GHz ch) ,so, 43907 have features of the connecting 5GHz .

Q1.Is this WICED Studio version supported the connecting p2p-go (5GHz ch) by Wicied libraries?

I check Wicied libraries code.

I do not seem to support this in the library.

I do not seems to found to set reg_class of channel in code.

Is this support connecting p2p-go (5GHz) at this library?

Q2. Please advise how to connect p2p-go(5GHz) if this is supported to conenct 5GHz GO.

I see the wiced code, however I do not know how to setup connecting p2p GO(5GHz).

Please advise how to connect p2p-go(5GHz).

Q3.Do you have to plan to support the features of P2P-GO(5GHz) in WICED library if it do not support 5GHz p2p-go?

Or how to modify the WICED library code?

We wish to support the connecting to p2p-GO(5GHz) .

Please advise.

Thanks,,

Minoru Sasaki

0 Likes
1 Solution
MiSa_2357281
New Contributor II

Hello All

I checked some code  in WICED Studio.

In the "\43xxx_Wi-Fi\WICED\security\BESL\host\WICED\p2p_internal.c, there are code as follows:

----------------------

static besl_result_t p2p_scan( p2p_workspace_t* workspace, uint16_t scan_action, wiced_bool_t scan_all_channels )

{

    wiced_buffer_t  buffer;

    wl_p2p_escan_t* p2p_scan;

    besl_mac_t      bcast = {{255, 255, 255, 255, 255, 255}};

    uint32_t        number_of_channels = 3; /* Default number of channels to cover the three social channels (1, 6, 11) */

    uint16_t        social_channels[3] = { 1, 6, 11 };

    uint16_t        all_channels[11]   = { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 };   // @@ This code

    uint16_t*       channel_list_ptr   = social_channels;

    uint32_t        bss_index          = wwd_get_bss_index( WWD_P2P_INTERFACE );

    uint32_t*       data;

    uint32_t        data_size;

    if ( workspace->scan_in_progress == 1 )

    {

        BESL_DEBUG(("p2p_scan: scan already in progress\r\n"));

    }

    workspace->scan_in_progress = 1;

    /*  Begin p2p scan of the "escan" variety */

    if ( scan_all_channels == WICED_TRUE ) /* All channels means 2.4 GHz 1-11 for now */

    {

        number_of_channels = 11;          // @@ This code

        channel_list_ptr   = all_channels;

    }

------------------------

I think that it is limited for scan of GO channel by 1ch - 11ch in this code.

So I add  the w52 ch(36,40,44,48) to all_channels and index = 11 to 15, and number_of_channels = 11 to 15.

Then, it can found the 43455 36 ch GO and connected 43907 to this GO.

I think this is not a correct fix, but I think it can be used for testing.

I will test using this change.

Thanks,,

Minoru Sasaki

View solution in original post

4 Replies
Zhengbao_Zhang
Moderator
Moderator

hello:

   from the function:

p2p_set_listen_channel , it is limited to 1, 6, 11 channel in current release.

will check if we can set to 5G band  for the test later, thanks.

0 Likes
MiSa_2357281
New Contributor II

Hello ZhengbaoZ

Thank you for your response.

I did a little confirmation from that.

The WICED device and 43455(Linux) device can connect 5GHz CH GO(43455 go intent =5) and GC(WICED 43907 go intent = 1) using by p2p negotiation.

When the WICED device disconnect, and it run the "p2p_discovery_enable" and "p2p_peer_list" on WICED device , WICED device can not found the 43455 P2P device .

And After this time, when 43455 exec the p2p_group_remove p2p-wlan0-0, and it run the "p2p_discovery_enable" and "p2p_peer_list" on WICED device , WICED device can found the 43455 P2P device .

And when it create p2p-GO(2.4GHz ch) on 43455 and it run the "p2p_discovery_enable" and "p2p_peer_list" on WICED device , WICED device can found the 43455 P2P device .

The Android device can discover P2P device even if it is running P2P-GO on both channels.

At this way,

When the 43455 device was execing p2p-go(5GHz ch), the WICED can not found p2p device using p2p_peer_list command.

So I think that there is issue on discovery process.

Please advise.

Thanks,,

Minrou Sasaki

0 Likes
MiSa_2357281
New Contributor II

Hello All

I checked some code  in WICED Studio.

In the "\43xxx_Wi-Fi\WICED\security\BESL\host\WICED\p2p_internal.c, there are code as follows:

----------------------

static besl_result_t p2p_scan( p2p_workspace_t* workspace, uint16_t scan_action, wiced_bool_t scan_all_channels )

{

    wiced_buffer_t  buffer;

    wl_p2p_escan_t* p2p_scan;

    besl_mac_t      bcast = {{255, 255, 255, 255, 255, 255}};

    uint32_t        number_of_channels = 3; /* Default number of channels to cover the three social channels (1, 6, 11) */

    uint16_t        social_channels[3] = { 1, 6, 11 };

    uint16_t        all_channels[11]   = { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 };   // @@ This code

    uint16_t*       channel_list_ptr   = social_channels;

    uint32_t        bss_index          = wwd_get_bss_index( WWD_P2P_INTERFACE );

    uint32_t*       data;

    uint32_t        data_size;

    if ( workspace->scan_in_progress == 1 )

    {

        BESL_DEBUG(("p2p_scan: scan already in progress\r\n"));

    }

    workspace->scan_in_progress = 1;

    /*  Begin p2p scan of the "escan" variety */

    if ( scan_all_channels == WICED_TRUE ) /* All channels means 2.4 GHz 1-11 for now */

    {

        number_of_channels = 11;          // @@ This code

        channel_list_ptr   = all_channels;

    }

------------------------

I think that it is limited for scan of GO channel by 1ch - 11ch in this code.

So I add  the w52 ch(36,40,44,48) to all_channels and index = 11 to 15, and number_of_channels = 11 to 15.

Then, it can found the 43455 36 ch GO and connected 43907 to this GO.

I think this is not a correct fix, but I think it can be used for testing.

I will test using this change.

Thanks,,

Minoru Sasaki

View solution in original post