NXP_WTS_AGENT-R1.9: Scripts missing in Android source code package

[nandan-khant]

Hello NXP team,

We are using the NXP_WTS_AGENT_Source-R1.9 package. It has two SRC folders.

1. R-1.9-Android-SRC

2. R-1.9-Linux-SRC

The load scripts for test cases are present in the Linux source package, It is not available in the Android source package.

For Linux, The scripts are present in NXP_WTS_AGENT_Source-R1.9/SRC/R-1.9-Linux-SRC/utils/scripts/U16/load-scripts directory.

Please refer images below.

Queries:

1. Does these scripts required in Android SRC for certification?

2. If required, please help to provide scripts for NXP_WTS_AGENT_Source-R1.9 package for Android SRC.

Please help answer the above queries as soon as possible.

Thanks and Regards,

Nandan Khant

[nandan-khant]

Hello @weidong_sun 

Thank you for the updates.

Please perform the TESTING on your end and share the RESULTS.

We have created the WTS_AGENT package of the the Android-SRC.

We have copied all the scripts and configuration files from Linux-SRC to Android-SRC WTS_AGENT folder(NXP_WTS_AGENT_IMX_Android_bin) as suggested by you.

Please VERIFY and CONFIRM that this Android-SRC WTS_AGENT package(PFA) contains all the necessary scripts required for the certification of Wi-Fi4, Wi-Fi5, SVD, FFD, WPA2SI, PMF, and WPA3-R2+R3.

Thanks and Regards,

Nandan Khant

[weidong_sun]

Hello @nandan-khant ,

Confirmed it with internal team.

configuration files & script in R-1.9-Linux-SRC can also be used for android.

Try it, please!

Regards,

weidong

[nandan-khant]

Hello @weidong_sun,

Should all the scripts be copied from Linux-SRC to Android-SRC? Please share the steps.

Please share the COMPLETE package of WTS_AGENT-R_1.9.

Requesting a quick response.

Thanks and Regards,

Nandan Khant

[weidong_sun]

Hi @nandan-khant ,

>>Should all the scripts be copied from Linux-SRC to Android-SRC?

need it ? you can.

>>Please share the COMPLETE package of WTS_AGENT-R_1.9.

We have no extra config files & script. 

Regards,

weidong

[nandan-khant]

Hello @weidong_sun,

As confirmed by you previously that scripts are MISSING in the Android NXP WTS source package, we need your support in moving forward with product certification. It is a BLOCKER for us.

Please help:

1. In getting the complete NXP_WTS_AGENT_Source-R1.9 package for ANDROID with all the scripts and configurations present in Linux.

2. Provide the procedure or detailed steps to proceed ahead without adding any scripts or configurations.

Thanks and Regards,

Nandan Khant

[weidong_sun]

Hello @nandan-khant ，

I pan to run your application on our i.mx platform + android 11.

I will spend some time preparing test environment.

Regards,

weidong

[nandan-khant]

Hello @weidong_sun,

Is there any update?

Please share your updates as soon as possibe.

Thanks and Regards,

Nandan Khant

[weidong_sun]

Hello @nandan-khant ,

I just got the android 11 source code ready and am compiling it.
By the way, I don't have the 8897 module here, I can only test it on the 8997 module, which may not start until tomorrow (China time).

Regards,

weidong

[weidong_sun]

Hello @nandan-khant ,

On my side, android bsp has been run on i.MX8QM-board.

Now I am downloading android ndk, then I will cross compile the WTS DUT tool.

In addition, WTEC FAE James Lin & Luka Lin also submitted the same question as yours in our system.

I send a document to them, and ask them to forward it to you.

you can use the same version of WTS DUT agent in the document.

Regards,

Weidong

[weidong_sun]

Hello @nandan-khant 

I run wfa_dut & wfa_ca successfully on imx platform + android 11.

Below is my steps:

=============================================================

1. Getting android ndk
# cd /opt/
# sudo git clone https://github.com/urho3d/android-ndk.git

2. Creating cross compilation toolchain
# cd android-ndk
# sudo build/tools/make_standalone_toolchain.py --arch arm64 --api 26 --install-dir=/opt/ndkroot
then ndkroot will be created and full toolchains are in the directory.

3. Checking toolchain
# cd /opt/ndkroot/
# ls
aarch64-linux-android COPYING3 include manifest_4691093.xml NOTICE sysroot
AndroidVersion.txt COPYING3.LIB lib MODULE_LICENSE_BSD_LIKE prebuilt_include test
bin COPYING.LIB lib64 MODULE_LICENSE_GPL repo.prop

4. Changing configurations of Makefile.inc
Go back to ~/WTS-DUT-AGENT/NXP_WTS_AGENT_Source-R1.9/SRC/R-1.9-Android-SRC, open Makefile.inc and change it.
# cd ~/WTS-DUT-AGENT/NXP_WTS_AGENT_Source-R1.9/SRC/R-1.9-Android-SRC
# gedit Makefile
.....
NDKROOT=/opt/ndkroot/bin
PLATFORM=/opt/ndkroot/sysroot
CROSS_COMPILE=$(NDKROOT)/aarch64-linux-android-
CC=${CROSS_COMPILE}gcc
......
save & exit

5. Cross compilation
# make all

after compilation is done, NXP_WTS_AGENT_IMX_Android_bin directory is created.
# cd NXP_WTS_AGENT_IMX_Android_bin
# ls
BGN-20-1x1.sh Channel_Freq.conf getiwconfig.sh gpstats.sh stoping.sh VHT-80-1x1.sh wfa_dut WTS-AGENT-BK_UP.tar
BGN-20-2x2.sh dut.sh getpid.sh p2p.conf updatepid.sh VHT-80-2x2.sh wfaping.sh
ca.sh getipconfig.sh getpstats.sh scripts user_config.conf wfa_ca wpa_supplicant.conf

6. Using adb push to copy files to android board
[Note]
Before the operation, user should open OEM unlock of android, and make android in debug mode.
# sudo adb root
# sudo adb shell
# cd vendor
# mkdir sigma
# exit
# sudo adb push ./wfa_* /vendor/sigma

7. Try to run wfa_dut & wfa_ca
# sudo adb shell
# cd /vendor/sigma
# ls
1|mek_8q:/vendor/sigma # ls
wfa_ca wfa_dut
mek_8q:/vendor/sigma #
# ./wfa_dut
=========logs=================
|mek_8q:/vendor/sigma # ./wfa_dut
Software Version: NXP_WTS_AGENT_R-1.9-Android(01:34:43 Nov 16 2022)
Usage:
wfa_dut -v (version)
wfa_dut <interface> <port> <program_index> <wlan interface name>
where programs:
1.HE-STAUT
2.HE-APUT-HOSTAPD
3.VHT-STAUT
4.VHT-STAUT-MWIFIEX
5.VHT-APUT-UAPUTL
6.VHT-APUT-HOSTAPD
7.11N-STAUT
8.11N-STAUT-MWIFIEX
9.11N-APUT-UAPUTL
10.11N-APUT-HOSTAPD
11.PMF-STAUT
12.PMF-STAUT-MWIFIEX
13.PMF-APUT-UAPUTL
14.PMF-APUT-HOSTAPD
15.WPA3-STAUT
16.WPA3-APUT-HOSTAPD
17.WMM-PS-STAUT
18.WMM-PS-APUT
19.WMM-PS-APUT-HOSTAPD
20.P2P-MWU
21.P2P-WS
22.MBO-STAUT
23.FFD-VU-APUT-UAPUTL
24.FFD-VU-APUT-HOSTAPD
25.FFD-VU-STAUT
26.HS2-R1
27.HS2-R2
28.V-E-STAUT
29.TDLS
Example:
wfa_dut lo 8000 5 wlan0

1|mek_8q:/vendor/sigma # ./wfa_ca
File wfa_ca.c, Line 131: Usage: ./wfa_ca <control interface> <local control agent port>
1|mek_8q:/vendor/sigma #

============================================================

Regards,

weidong

[nandan-khant]

Hello @weidong_sun,

Thank you for sharing your results. I was able to run the WFA binaries. However, the issue which we reported is different.

All the test cases for Wi-Fi4, Wi-Fi5, SVD, FFD, WPA2SI, PMF, and WPA3-R2+R3 are failing when the LAB performs certification tests. 

The DUT STA is not able to connect to reference AP. As explained earlier in this case.

Please help to resolve this issue ASAP as we are running out of time and a quick response is highly appreciated.

Please refer to the logs shared in the case. 

Thanks and Regards,

Nandan Khant

[weidong_sun]

Hello @nandan-khant ,

I want to know if your DUT device is currently in WFA lab, and is it tested with sigma tool?

Regards,

weidong

[nandan-khant]

Hello @weidong_sun,

No, It is not at the WFA lab.

The WFA lab requires the fix for the issues before proceeding forward.

Can we have a quick call to discuss the issues and work on the probable fix for the issue?

Please share your time of availability. 

Thanks and Regards,

Nandan Khant

[weidong_sun]

Hello @nandan-khant ,

If your device is not in WFA lab, you cannot complete the test. Because the sigma tool requires a lot of external equipment. I also can't complete the test in office.

If you encounter problems in WFA lab certification, you can submit a ticket to us.

Regards,

weidong

[nandan-khant]

Hello @weidong_sun,

The WFA lab has already performed test cases inside the LAB with a complete WFA setup.

All the test cases failed. The WFA lab has shared the results with us which I have already shared with you previously. 

The WFA lab is waiting for the fix to the issue which we have reported to NXP.

Thanks and Regards,

Nandan Khant

[weidong_sun]

Hello @nandan-khant ,

OK, understand your situation.

According to your above descripitons, these test plans didn't pass in WFA lab, Wi-Fi4, Wi-Fi5, SVD, FFD, WPA2SI, PMF, and WPA3-R2+R3. 

Please follow thest steps to create ticket in our system FOR EACH test plan.

For example: 

1. WPA3-R3 test plan

In Wi-Fi_CERTIFIED_WPA3_Test_Plan_v3.2,  chaper "3.2.2 STAUT test applicability", 

if "STAUT SAE confirmation exchange variation test" failed, It will be better if you use 5.2.7_STAUT_SAE_ confirmation_exchange_variation_test named your log's file name.

......

2. Create a ticket via nxp website www.nxp.com

SUPPORT--->support ticket--->Create New Case

in your ticket, you should provide these information:

(1) Driver / Firmware version

(2) Android platfor information

(3) Hardware platform information

(4) Siniffer logs 

(5) if you have ucc logs, provide it, please!

(6) wpa_supplicant version (the one in android 11 or from open source v2.10)

(As I am known, wpa_supplicant in android 11 doesn't support WPA3-R3, but in android 12, no problem)

(7) wpa_supplicant.conf  

we need it's detailed configurations of wpa_supplicant.conf  

Then I will share above information with internal team, and analyse it together.

Thanks!

Regards,

weidong

[nandan-khant]

Hello @weidong_sun,

The customer has already filed a ticket in your system a few days back. As you have mentioned previously in your comment of 15th November.

The lab performed the very basic test case 11N-5.2.35_AN and it failed to connect with the test bed AP.

The release used: SD-WLAN-SD-BT-8897-AO_LINUX_4_9_70-BG4CT-W15.68.19.p59-15.26.19.p59-C4X15698_B0B1-GPL

OS: ANDROID-11

Chipset: W8897

wpa_supplicant.conf:

##### wpa_supplicant configuration file template #####
update_config=1
ctrl_interface=mlan0
eapol_version=1
ap_scan=1
fast_reauth=1
p2p_disabled=1
wowlan_triggers=any

I am attaching the logs for your reference again.

Please share all the details with your internal team and share the updates.

The customer is FRUSTRATED and would like to ESCALATE this issue to the next level.

Please help to resolve the issue as soon as possible.

Thanks and Regards,

Nandan Khant

[weidong_sun]

Hello @nandan-khant ,

OK, got it.

But your configurations in wpa_supplicant.conf seems not correct.

For connections to AP with WPA3-R3 security , wpa_supplicant.conf should be like this:

=====================

ctrl_interface=/var/run/wpa_supplicant
update_config=1
network={
ssid="wpa3r3"
scan_ssid=1
key_mgmt=SAE
proto=RSN
pairwise=CCMP
group=CCMP
psk="12345678"
ieee80211w=2
}
sae_groups=19 20 21
sae_pwe=1

============================

Regards,

weidong

Regards,

weidong

[nandan-khant]

Hello @weidong_sun,

THE LAB PERFORMED THE VERY BASIC TEST CASE 11N-5.2.35_AN AND IT FAILED TO CONNECT WITH THE AP.

Please share the logs and details with your internal team.

The ticket has been already filed in your system. REFER to that ticket as well and proceed further with your internal team. All the details are already shared by the customer in the ticket.

The test case is 11N-5.2.35_AN.

wpa_supplicant.conf:

##### wpa_supplicant configuration file template #####
update_config=1
ctrl_interface=mlan0
eapol_version=1
ap_scan=1
fast_reauth=1
p2p_disabled=1
wowlan_triggers=any

This is taking too much time. If required we can have a quick call to discuss the issue.

Thanks and Regards,

Nandan Khant

[weidong_sun]

Hi @nandan-khant ,

I have already shared your questions with internal team. 

Then let us continue to disscuss it.

Please tell me :

when you open your wifi in Android GUI, it can scan and connect to AP?

Regards,

weidong