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.

wpa_supplicant compilation issue provided with R8.5 Wilink8 for Android 4.2.2 Devkit 4.1.1 AOSP AM335x

Hello All,

I am working Android JellyBean 4.2.2 Devkit 4.1.1 on  AM335x customized board.

I have ported R8.5 Wilink 8 on it for wlan interface.Currently, I am facing issue regarding the association and de-association problem when the device connects to AP.I LOGCAT the scenario and found that it is getting de-associated because wpa_supplicant [VERSION 0_8_X_TI] in devkit doesnt support the command "BTCOEXMODE"

Further ,i tried to compile the wpa_supplicant 2.1-devel by ti comes with the Wilink 8 R8.5 WLAN WL18xx package.As it handles the above mention command.

When i tried to compile the wpa_supplicant with the AOSP.It got stuck with the error of

No such file or directory : '.........../libkeystore_binder/export_includes'  needed by .........../libkeystore_binder/import_includes' 

I am unable to compile kindly please guide me for this.

Regards

Nitish

  • Hi Nitish,

    could provide us with the following so that we can better help you:

    1) the sources URL for the wpa_suppplicant version you are trying to install
    2) the full build logs and the build command you are running

  • Hello Team,

    Thank you for response.Here i am attaching wpa_supplicant source tar ,Logs file and Android.mk file that i used to compile the wpa_supplicant in AOSP.

    Regards

    Nitish Mehta

    6354.Android.txt6404.BuildLogs_Android.txt5025.wpa_supplicant-ti-2.1.tar.gz

  • Hi Nitish,

    I could reproduce the issue and investigate on this missing library.
    It turns out the libkeystore_binder was included in Android with JB 4.3 (commit 07438c8d7256d3788dac323b4d0055f201e0bec9).

    In order to use this version of wpa_supplicant you need to either:
    - backport the keystore binder feature in JB 4.2.2 supported by TI
    - port the keystore client (old version) to the new version of wpa_supplicant.
  • Hello Team,

    Thank you again for your valuable response.I will be grateful to you for putting more light on this part.

    As i am not able to understand how i have to backport  keystore binder feature or port the keystore client.Which version of the same i have to port.

    I didnt have anything related to Android 4.3.

    Regards

    Nitish Mehta

  • Hi Nitish,

    Basically, the libkeystore changed its API in between version JB 4.2.2 and JB 4.3:
    • JB 4.2.2 (official BSP for am335x) provides libkeystore_client
    • JB 4.3 provides libkeystore_binder

    The wpa_supplicant provided with JB 4.2.2 that lack your BTCOEXMODE is using the libkeystore_client API.
    The wpa_supplicant 2.1 that you want to use, being more recent, uses the newer API from libkeystore_binder and therefore cannot work as is on JB 4.2.2.

    The 2 possible solutions would be:

    • port the libkeystore_binder from JB 4.3 to JB 4.2.2, which might be not trivial

    OR

    • backport the wpa_supplicant 2.1 libkeystore backend back to libkeystore_client rather than libkeystore_binder

    I hope this is a little bit more clear.

  • Hi all,

    Taking over the thread, I have tried backporting the wpa_supplicant 2.1 by TI package and successfully compiled it.

    But new problem is, when the device is up and running , the service for wpa_supplicant doesn't start through init.am335xevm.rc file. After giving "ps" command, I can't see any backend process for wpa_supplicant. If I manually try to run the wpa_supplicant, it aborts with an error.

    When I run "wpa_cli -iwlan0 scan" command, it gives an error
    "failed to connect to non-global ctrl_ifname: wlan0 error: No such file or directory ".

    My wpa_supplicant.conf under having "crtl.interface=wlan0".

    All drivers are loaded fine and i get wlan0 interface UP when i run "netcfg" command.

    Currently I cant find "iw" command so I cant cross check wlan unless and untill wpa_cli and wpa_supplicant runs OK.

    Kindly suggest me what can be the issue? How can I start the wpa_supplicant service while init by default.

    Quick response is expected ASAP.

    Thanking in advance,

    Divyesh Maisuria.
  • Hi all,

    There is an update, I have managed to have iw tool on android and with this tool , I am able to access and use wifi just OK.

    That states there's no issue on wifi driver side, the only issue I may predict is the wpa_supplicant service not invoking properly from init.am335xevm.rc.

    I really appreciate a response to help me get this issue resolved.

    Thanks & Regards,
    Divyesh Maisuria
  • Hi Divesh,

    In our board wifi driver configured as dynamic load and it is working fine.

    Please share me your .rc files and I will try if I find anything you missed in that.

    In your board you configured the wifi driver as a statically?

    Regards

    Ashok

  • Hi Ashok,

    Thanks for the co-operation, I'm attaching all required rc files, wpa_supplicant.conf file and wpa_supplicant and wpa_cli binaries i'm using.

    I have also attached output of "ps" command and "service list" command.

    Kindly go through it and let me know if you can find any breach.

    Regards,

    Divyesh M5482.AD_wpa_supplicant_Issue.zip7558.ServiceList.txt

  • PS: the wifi drivers are loaded as module from init scripts.

    Regards,
    Divyesh
  • Hi Divyesh,

    As per init.am335xevm.rc file your not loading wifi as a dynmicallly,

    #wi-fi
        mkdir /data/misc/wifi/sockets 0770 wifi wifi
        mkdir /data/misc/dhcp 0770 dhcp dhcp
        insmod /system/lib/modules/compat.ko
        insmod /system/lib/modules/cfg80211.ko
        insmod /system/lib/modules/mac80211.ko
        insmod /system/lib/modules/wlcore.ko
        insmod /system/lib/modules/wlcore_sdio.ko
        insmod /system/lib/modules/wl18xx.ko

    Please confirm that.

    For dynamic loading of wifi driver, need to do changes in hardware/libhardware_legacy/wifi/Android.mk and wifi.c file.

  • Hi ,

    I have managed to get the wpa_supplicant running OK. But, when I connect to an AP, it gets some issue as follow.

    root@android:/ # [  751.917239] wlan0: deauthenticating from 02:1a:11:f2:da:24 by local choice (Reason: 3=DEAUTH_LEAVING)

    [  752.032580] cfg80211: Calling CRDA to update world regulatory domain

    [  752.757424] wlan0: authenticate with 02:1a:11:f2:da:24

    [  752.768171] wlan0: send auth to 02:1a:11:f2:da:24 (try 1/3)

    [  752.798297] wlan0: authenticated

    [  752.808655] wlan0: associate with 02:1a:11:f2:da:24 (try 1/3)

    [  752.916174] wlan0: RX AssocResp from 02:1a:11:f2:da:24 (capab=0x421 status=0 aid=5)

    [  752.931060] wlan0: associated

    [  752.941884] wlcore: Association completed.

    [  763.494291] wlan0: deauthenticating from 02:1a:11:f2:da:24 by local choice (Reason: 3=DEAUTH_LEAVING)

    [  763.535160] cfg80211: Calling CRDA to update world regulatory domain

    [  764.259465] wlan0: authenticate with 02:1a:11:f2:da:24

    [  764.270840] wlan0: send auth to 02:1a:11:f2:da:24 (try 1/3)

    [  764.304025] wlan0: authenticated

    [  764.318656] wlan0: associate with 02:1a:11:f2:da:24 (try 1/3)

    [  764.353537] wlan0: RX AssocResp from 02:1a:11:f2:da:24 (capab=0x421 status=0 aid=6)

    [  764.368529] wlan0: associated

    [  764.380109] wlcore: Association completed.

    [  774.827024] wlan0: deauthenticating from 02:1a:11:f2:da:24 by local choice (Reason: 3=DEAUTH_LEAVING)

    [  774.864842] cfg80211: Calling CRDA to update world regulatory domain

    [  775.614615] wlan0: authenticate with 02:1a:11:f2:da:24

    [  775.625192] wlan0: send auth to 02:1a:11:f2:da:24 (try 1/3)

    [  775.656684] wlan0: authenticated

    [  775.668650] wlan0: associate with 02:1a:11:f2:da:24 (try 1/3)

    [  775.693621] wlan0: RX AssocResp from 02:1a:11:f2:da:24 (capab=0x421 status=0 aid=7)

    [  775.708455] wlan0: associated

    [  775.719637] wlcore: Association completed.

    I have attached detailed log file.

    PL let me know if you're familiar with this issue.

    Regards,

    Divyesh1524.wpa_suppl_Isuue.txt