[88W8997] module iperf disconnect and ping failed issue with drv_mode=1 (PCIE+UART, Host: iMX8MQ)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

[88W8997] module iperf disconnect and ping failed issue with drv_mode=1 (PCIE+UART, Host: iMX8MQ)

1,075 Views
yao_feng
Contributor III

Host: iMX8MQ
SW: Q2, 24 BSP version + patch

@ArthurC 
@Christine_Li 

0 Kudos
Reply
4 Replies

1,057 Views
Christine_Li
NXP TechSupport
NXP TechSupport

Hi, @ArthurC ,

I post the shared logs on this new case. We will discuss the iperf disconnect and ping failed issue with drv_mode=1(to disable uap0).

For drv_mode=1 scenario A‘s log: Currently our analysis is as below:

  • Could observe only 1 Connection established
    • Aug 26 09:49:40 tbox100 kernel: wlan: HostMlme wlan0 Connected to bssid bc:XX:XX:XX:03:1a successfully 4-way HS completed and connected with AP 
    • Aug 26 09:49:40 tbox100 wpa_supplicant[809]: wlan0: CTRL-EVENT-CONNECTED - Connection to bc:a5:11:ad:03:1a completed [id=0 id_str=]
  • After this Connection is established there is no disconnection in the logs.

So from the logs it looks the AP-STA connection is intact and no disconnection occurs with STA-only mode. 

But according to your feedback, the iperf still disconnect and ping failed. We will discuss internally to see where we can add some debug info for debug further.

For drv_mode=1, auto_ds=2,ps_mode=2's logs:

We are under analysis and discussion internally. Will share our updates to you soon.

 

Best regards,

Christine.

0 Kudos
Reply

1,026 Views
Christine_Li
NXP TechSupport
NXP TechSupport

Hi,  @ArthurC

Update our status for this issue:

#1. with auto_ds and ps_mode in default value.

  • The provided logs is not sufficient for us to debug the issue further, We required the in-sync wireshark logs to map with the driver logs.
  • Can you please prepare a U16 setup with 8997 SOC to capture the sniffer logs using monitor mode? Below are the steps to capture the sniffer logs.
    • Load the driver
    • ./mlanutl mlan0 netmon

(Please refer the README_MLAN to set the specific channel for 2G and 5G based on the external_AP channel used)

(e.x for 2G = ./mlanutl mlan0 netmon 1 7 11 6 0 / for 5G = ./mlanutl mlan0 netmon 1 7 20 36 0 )

    • ifconfig rtap up
    • tcpdump -i rtap -w "filename".pcap

Make sure to start the sniffer before the connection and stop once the issue is observed.

 

Best regards,

Christine.

0 Kudos
Reply

914 Views
Christine_Li
NXP TechSupport
NXP TechSupport

Hi,  @ArthurC

As mentioned in Wechat, our SAE has confirmed our default release can support monitor mode . And also they have verified this feature locally.

Please refer to attached README for the steps to test monitor mode.

Also, I will do same test locally to double confirm so that can better support you.

 

Best regards,

Christine.

0 Kudos
Reply

898 Views
Christine_Li
NXP TechSupport
NXP TechSupport

Hi, @ArthurC

I have tested locally and confirmed that our Q2-2024 released Wi-Fi driver and FW can enter monitor mode to capture sniffer logs. My test is based on I.MX8MQ-EVK which is using Linux 6.6.23 yocto BSP.

Please refer to attachment for my test results and logs.

Please try on your side and let me know whether is ok on your side. If it is ok, please help to provide us sniffer logs and time synced dmesg logs ASAP so that we can move further on this case.

 

Best regards,

Christine.

0 Kudos
Reply