Could you send email to xianjun.jiao@ugent.be to introduce your self?
Done
Issue description:
Although, AP mode works great.
I observe a lot of bad-fcs messages in tcpdump when openwifi is in monitor mode. All the 6Mbps packets are marked as bad-fcs when I use channel 44. When I switch to channel 6, packets with 6Mbps are marked ok but at the same time some packets with any other rates apart from 6Mbps are marked as bad-fcs.
Our image is used directly or you build your own image?
I used your image: openwifi-1.3.0-wilsele-32bit.img.xz
What is your own modification?
NA
Versions: OS, Vivado, openwifi/openwifi-hw repo branch and commit revision
NA
Board/hardware type
adrv9361z7035
WiFi channel number
44 and 6.
Steps to reproduce the issue, and the related error message, screenshot, etc
I enable all rx debugs and observe same fcs0 messages in dmesg. I also observe lots of WARNING messages with loop_count 2 and 0. Are they because the traffic load is high?
Any other thing we need to know for helping you better?
A related issue is that I am not able to capture packets from my laptop on the openwifi device.
When using 5GHz (ch 44) frequency range, I run inject_80211 application from my laptop's WiFi interface but openwifi does not receive any of these packets. I have tried different rate, packet_type, WiFi mode but nothing works.
When going to 2.4GHz, openwifi interface is able to capture all packets from my laptop's WiFi interface.
Are these observations due to ADRV9361-Z7035 having low gain in 5GHz range?
Thanks for the report. Your content is well aligned with our template!
Indeed ADRV9361-Z7035 has some 5GHz issue, but as far as I know it is mainly about super low Tx power. For Rx we haven't test it seriously. But, it always helps if you have other type of board to do cross check.
Could you try 1.3.1 image? (But I suppose more or less the same) That image support dynamic FPGA/Driver loading, which will ease you to load our future updates.
"loop_count 2 and 0. Are they because the traffic load is high?", indeed. But it should not be a big issue.
We are optimizing PHY Rx recently, and will have new release soon. This could help with the issue.
Regarding trying to capture the injected packet from your laptop, please make sure your laptop send 20MHz, single antenna (no MIMO/beamforming/etc), 802.11a/g/n packet. Openwifi now can not recognize the format with wider bandwidth or more antennas. You can double confirm this by another COTS device based sniffer.
A better antenna sometimes also helps. Make sure you have antenna that supports 5GHz or 2.4/5GHz dual band.
Adjust the distance (closer or further) could also help, because the AD9361 AGC dynamic range is limited.
Issue description: Although, AP mode works great.
I observe a lot of bad-fcs messages in tcpdump when openwifi is in monitor mode. All the 6Mbps packets are marked as bad-fcs when I use channel 44. When I switch to channel 6, packets with 6Mbps are marked ok but at the same time some packets with any other rates apart from 6Mbps are marked as bad-fcs.
Our image is used directly or you build your own image?
What is your own modification?
Versions: OS, Vivado, openwifi/openwifi-hw repo branch and commit revision
Board/hardware type
WiFi channel number
Steps to reproduce the issue, and the related error message, screenshot, etc
Describe your debug efforts by Linux native tools, such as tcpdump and "cat /proc/interrupts"
Describe your debug efforts by: https://github.com/open-sdr/openwifi/blob/master/doc/README.md#Debug-methods
Any other thing we need to know for helping you better?
A related issue is that I am not able to capture packets from my laptop on the openwifi device.
Are these observations due to ADRV9361-Z7035 having low gain in 5GHz range?