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.

How to initiate background scan for wilink8 driver

Other Parts Discussed in Thread: WL1835

Hi,

I referred R8.4 release notes for wilink8 driver, in that background scan is validated.

I am using wilink8 NLCP driver ol_r8.a9.14(using WL1835 chipset), i want to test whether background scan is initiating or not on wilink8 driver,can any one please help me how to test this one.

  • Hi Vinay,

    Are you talking about passive scan? Can you try: "iw dev wlan0 scan passive"

    Regards,
    Gigi Joseph.

  • Thanks for the reply Joseph Gigi,

    Yes i am talking about passive scan only,normally for active scan will use the command iw dev wlan0 scan
    ,but for passive scan without using any command directly the driver should initiate the background scan right,


    For Ex:

    connect to openAP with iw command,after connecting to AP, driver should initiate background scan by sending probe request,checked in omnipeak sniffer,no preobe requests are going once it is connected to AP.

    One more question:

    In R8.4 release notes background scan is validated,can u please explain how it is validated.

    Please give me the reply on how to test background scan for wilink8.

  • Hi Vinay,

    Not sure I understood you --- "connect to openAP with iw command,after connecting to AP, driver should initiate background scan by sending probe request" --- Why? probe request would be active scan. If you mean a "roaming" scan, then it is triggered by the RSSI level.

    Regards,
    Gigi Joseph.

  • Hi Gigi,

    I want to validate the background scan feature on wilink8 chipset.

    For wilink7:

    I checked in the code there CMD_PERIODIC_START_SCAN cmd is going to firmware and initiating background scan.

    For wilink8:

    There is no periodic scan cmd going to firmware,i don't understand how the background scan is working on wilink8 chipsets.

  • Hi Vinay,

    I believe in WL8, for Periodic scan, we send the CMD_SCAN command with scan type = SCAN_TYPE_PERIODIC. You can check the implementation in wl18xx_sched_scan_start() in drivers/net/wireless/ti/wl18xx/scan.c

    Regards,
    Gigi Joseph.

     

  • Thanks for the reply Joseph,

    I also verified the wilink8 code it is using CMD_SCAN to initiate background scan,but this is the only place where background scan is initiated or any other place is there.


    But wilink7 is not using CMD_SCAN for initiating background scan,it is using CMD_PERIODIC_SCAN,but this is not the case with wilink8.

    I will use ur information to proceed further.

  • Hi Vinay,

    Just to complete your question:

    The following command is used during a connection to permit the background scan for detecting candidate/s
    wpa_cli -i wlan0 set_network 0 bgscan '"learn:5:-65:10"'

    Where:

    5 – Short scan interval in seconds. Once AP's RSSI drops below this value, scan on all channels will be executed (like immediate scan) and scan intervals will be every 5 seconds
    -65 – AP's RSSI threshold
    10 – Long interval in seconds. Once AP's RSSI goes above this value, scan intervals will be every 10 seconds

    You can check this background roaming scan via the sniffer.

    Regards,
    Gigi Joseph.

  • Thanks for the reply Joseph Gigi,

    I will use ur information for testing the background scan,first will run the wpa_supplicant and connect to AP with open profile and then will run wpa_cli command to test the scan functionality,is it right way to do that one?

    Thanks&Regards

    k vinay kumar

  • Hi,

    Yes.

    Regards,
    Gigi Joseph.