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.

WL1801MOD: WL1801MOD : sta_connect-ex.sh ERROR:wlan0: Failed to initiate sched scan

Part Number: WL1801MOD

Hello

I am implementing wireless time synchronization on a Zynq-7000 (model: XC7Z007S-2CLG400E) proprietary board with wl1801mod.
Based on the information of "Clock synchronization by WL18xx NTP" posted on your wiki before, and the person who implemented wireless time synchronization with beaglebone implementing it.
but when I run sta_connect-ex.sh, I can't connect to the AP and it says "wlan0: Failed to initiate sched scan"

I tried to solve the problem by referring to processors.wiki.ti.com/.../WiLink8_WLAN_Demo:_Linux, but I couldn't find a solution.

The AP itself can be connected with the command "connmanctl".
The board operation log, execution procedure, and "Clock synchronization by WL18xx NTP" document are attached.
Would you please help me resolve the cause?

/cfs-file/__key/communityserver-discussions-components-files/968/sta_5F00_connect_2D00_ex_5F00_log.txt

/cfs-file/__key/communityserver-discussions-components-files/968/Execution_5F00_procedure.txt

/cfs-file/__key/communityserver-discussions-components-files/968/WL18xx_AF30ED30C330AF306830_NTP_6E300C541F67_.pdf

Thanks

  • Hi,

    I tested these commands on our EVM and do not see failed scan issue.

    You may run "wpa_cli -i wlan0" and run scan command and check if it works ok

    Thanks

    Saurabh

  • Saurabh

    Thank you for answering.

    If you try "wpa_cli -i wlan0" as answered, the following log will be displayed in an infinite loop.

    <3>CTRL-EVENT-SCAN-RESULTS
    <3>WPS-AP-AVAILABLE
    <3>CTRL-EVENT-NETWORK-NOT-FOUND

    From the message, it seems that the network cannot be found, but the "scan_result" command finds the surrounding SSIDs.

    Is there any solution?

    Thanks

    sio

  • Hi,

    I believe you need to run "scan_results" wpa_cli command to get scan results.

    Thanks

    Saurabh

  • Hi Saurabh

    As a result of continuing the investigation, we were able to solve the problem.

    You can now run the killallwpa_supplicant command to connect to the SSID before running ./sta_start.sh.

    Thank you for your cooperation in solving the problem.

    sio