open-sdr / openwifi

open-source IEEE 802.11 WiFi baseband FPGA (chip) design: driver, software
GNU Affero General Public License v3.0
3.83k stars 648 forks source link

Hard to scan the SSID and cannot connect to the openwifi #113

Closed HC153Yuanyuan closed 2 years ago

HC153Yuanyuan commented 2 years ago

My board is antsdr b220. I am running the openwifi project and found that when I working in 5GHz, the sniffer could not capture any beacon. When I switched to 2.4GHz, although I could capture beacon frame through wireshark, it was difficult for the phone to scan the SSID. When I try to connect, it always fails.

2021-10-22 22-43-47屏幕截图

2021-10-22 22-44-27屏幕截图

What do you think about this ?

HC153Yuanyuan commented 2 years ago

2021-10-22 23-12-13 的屏幕截图

HC153Yuanyuan commented 2 years ago

1023

Frequency spectrum

MicroPhase commented 2 years ago

The older version of antsdr is not officially support supported by openwifi. This due to the lvds interface. The openwifi needs 40MSPS sample rate at lvds interface, however the antsdr-b220 not originally designed with an LVDS interface, so there were some hardware limitations. You need to change the change the linux kernel for digital Interface Timing Verification, and maybe also need to edit the openwifi project with a lower sample rate.

JiaoXianjun commented 2 years ago

1023

Frequency spectrum

Hello, This spectrum is due to the offset tuning: https://github.com/open-sdr/openwifi/blob/master/doc/README.md#analog-and-digital-frequency-design

You can fix the spectrum in this quick way (We are working on the final solution):

  1. Replace this line: https://github.com/open-sdr/openwifi/blob/c63537c4fbd39557a6010359c32c75673c74c5d8/driver/sdr.c#L2072 to
    priv->tx_intf_cfg = TX_INTF_BW_20MHZ_AT_0MHZ_ANT0;
  2. Replace this line: https://github.com/open-sdr/openwifi/blob/c63537c4fbd39557a6010359c32c75673c74c5d8/user_space/openwifi_ad9361_fir.ftr#L6 to
    BWTX 20172411
  3. Replace this line: https://github.com/open-sdr/openwifi/blob/c63537c4fbd39557a6010359c32c75673c74c5d8/user_space/rf_init.sh#L57 to
    echo 1 > out_voltage_filter_fir_en
  4. Recompile the sdr driver, and copy all the new .ko files, openwifi_ad9361_fir.ftr and rf_init.sh onto the board. Then run your normal test. You should see spectrum like this:

image

HC153Yuanyuan commented 2 years ago

The older version of antsdr is not officially support supported by openwifi. This due to the lvds interface. The openwifi needs 40MSPS sample rate at lvds interface, however the antsdr-b220 not originally designed with an LVDS interface, so there were some hardware limitations. You need to change the change the linux kernel for digital Interface Timing Verification, and maybe also need to edit the openwifi project with a lower sample rate.

2021-10-25 23-13-24 的屏幕截图

Should I do the IO timing calibration by myself? or it has been done by ADI driver

HC153Yuanyuan commented 2 years ago

1023 Frequency spectrum

Hello, This spectrum is due to the offset tuning: https://github.com/open-sdr/openwifi/blob/master/doc/README.md#analog-and-digital-frequency-design

You can fix the spectrum in this quick way (We are working on the final solution):

  1. Replace this line: https://github.com/open-sdr/openwifi/blob/c63537c4fbd39557a6010359c32c75673c74c5d8/driver/sdr.c#L2072 to
priv->tx_intf_cfg = TX_INTF_BW_20MHZ_AT_0MHZ_ANT0;
  1. Replace this line: https://github.com/open-sdr/openwifi/blob/c63537c4fbd39557a6010359c32c75673c74c5d8/user_space/openwifi_ad9361_fir.ftr#L6 to
BWTX 20172411
  1. Replace this line: https://github.com/open-sdr/openwifi/blob/c63537c4fbd39557a6010359c32c75673c74c5d8/user_space/rf_init.sh#L57 to
echo 1 > out_voltage_filter_fir_en
  1. Recompile the sdr driver, and copy all the new .ko files, openwifi_ad9361_fir.ftr and rf_init.sh onto the board. Then run your normal test. You should see spectrum like this:

image

Thank you for your suggestion. I made modified follow these, but i still cant scan the openwifi ssid in my phone. I think it may be other problems.

JiaoXianjun commented 2 years ago

If no further questions, I will close this issue.