1<!-- 2Author: Xianjun jiao, Michael Mehari, Wei Liu 3SPDX-FileCopyrightText: 2019 UGent 4SPDX-License-Identifier: AGPL-3.0-or-later 5--> 6 7# openwifi 8<img src="./openwifi-arch.jpg" width="900"> 9 10**openwifi:** Linux mac80211 compatible full-stack IEEE802.11/Wi-Fi design based on SDR (Software Defined Radio). 11 12This repository includes Linux driver and software. **openwifi-hw** repository has the FPGA design. It is **YOUR RESPONSIBILITY** to follow your **LOCAL SPECTRUM REGULATION** or use **CABLE** to avoid potential interference over the air. 13 14[[Quick start](#Quick-start)] 15[[Project document](doc/README.md)] 16[[Application notes](doc/app_notes/README.md)] 17[[Videos](doc/videos.md)] 18[[Publications and How to Cite](doc/publications.md)] 19[[maillist](https://lists.ugent.be/wws/subscribe/openwifi)] 20 21Openwifi code has dual licenses. [AGPLv3](https://github.com/open-sdr/openwifi/blob/master/LICENSE) is the opensource license. For non-opensource and advanced feature license, please contact [email protected]. Openwifi project also leverages some 3rd party modules. It is user's duty to check and follow licenses of those modules according to the purpose/usage. You can find [an example explanation from Analog Devices](https://github.com/analogdevicesinc/hdl/blob/master/LICENSE) for this compound license conditions. [[How to contribute]](https://github.com/open-sdr/openwifi/blob/master/CONTRIBUTING.md). 22 23**Features:** 24 25- 802.11a/g/n [[IEEE 802.11n (Wi-Fi 4)](doc/app_notes/ieee80211n.md)] 26- 20MHz bandwidth; [70 MHz to 6 GHz frequency range](doc/README.md#let-openwifi-work-at-arbitrary-frequency) 27- Mode tested: [Ad-hoc](doc/app_notes/ad-hoc-two-sdr.md); [Station; AP](doc/app_notes/ap-client-two-sdr.md), Monitor 28- [DCF (CSMA/CA) low MAC layer in FPGA (10us SIFS is achieved)](doc/app_notes/frequent_trick.md) 29- [802.11 packet injection and fuzzing](doc/app_notes/inject_80211.md) 30- [CSI](doc/app_notes/csi.md): Channel State Information, freq offset, equalizer to computer 31- [CSI fuzzer](doc/app_notes/csi_fuzzer.md): Create artificial channel response in WiFi transmitter 32- [CSI radar](doc/app_notes/radar-self-csi.md): Moving detection. Joint radar and communication 33- [[IQ capture](doc/app_notes/iq.md)]: real-time AGC, RSSI, IQ sample to computer. [[Dual antenna version](doc/app_notes/iq_2ant.md)] 34- [Configurable channel access priority parameters](doc/app_notes/frequent_trick.md): 35 - CCA threshold, receiver sensitivity, etc 36 - duration of RTS/CTS, CTS-to-self 37 - SIFS/DIFS/xIFS/slot-time/CW/etc 38- [Time slicing based on MAC address (time gated/scheduled FPGA queues)](https://doc.ilabt.imec.be/ilabt/wilab/tutorials/openwifi.html#sdr-tx-time-slicing) 39- Easy to change bandwidth and [frequency](doc/README.md#let-openwifi-work-at-arbitrary-frequency): 40 - 2MHz for 802.11ah in sub-GHz 41 - 10MHz for 802.11p/vehicle in 5.9GHz 42- **802.11ax** under development 43 44**Performance (best case: aggregation/AMPDU on):** 45- iperf: TCP 40~50Mbps; UDP 50Mbps 46- EVM -38dB; MCS0 sensitivity -87dBm; MCS7 -72dBm. (FMCOMMS2 2.4GHz; cable and OTA test) 47 48**Supported SDR platforms:** (Check [Porting guide](#Porting-guide) for your new board if it isn't in the list) 49 50board_name|board combination|status|SD card img|Vivado license 51-------|-------|----|----|----- 52zc706_fmcs2|[Xilinx ZC706 board](https://www.xilinx.com/products/boards-and-kits/ek-z7-zc706-g.html) + [FMCOMMS2/3/4](https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/eval-ad-fmcomms2.html)|Done|[32bit img](https://users.ugent.be/~xjiao/openwifi-1.3.0-wilsele-32bit.img.xz)|Need 53zed_fmcs2|[Xilinx zed board](https://www.xilinx.com/products/boards-and-kits/1-8dyf-11.html) + [FMCOMMS2/3/4](https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/eval-ad-fmcomms2.html)|Done|[32bit img](https://users.ugent.be/~xjiao/openwifi-1.3.0-wilsele-32bit.img.xz)|**NO** need 54adrv9364z7020|[ADRV9364-Z7020 + ADRV1CRR-BOB](https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/adrv9364-z7020.html)|Done|[32bit img](https://users.ugent.be/~xjiao/openwifi-1.3.0-wilsele-32bit.img.xz)|**NO** need 55adrv9361z7035|[ADRV9361-Z7035 + ADRV1CRR-BOB/FMC](https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/ADRV9361-Z7035.html)|Done|[32bit img](https://users.ugent.be/~xjiao/openwifi-1.3.0-wilsele-32bit.img.xz)|Need 56zc702_fmcs2|[Xilinx ZC702 board](https://www.xilinx.com/products/boards-and-kits/ek-z7-zc702-g.html) + [FMCOMMS2/3/4](https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/eval-ad-fmcomms2.html)|Done|[32bit img](https://users.ugent.be/~xjiao/openwifi-1.3.0-wilsele-32bit.img.xz)|**NO** need 57antsdr|[MicroPhase](https://github.com/MicroPhase/) enhanced ADALM-PLUTO [Notes](kernel_boot/boards/antsdr/notes.md)|Done|[32bit img](https://users.ugent.be/~xjiao/openwifi-1.3.0-wilsele-32bit.img.xz)|**NO** need 58zcu102_fmcs2|[Xilinx ZCU102 board](https://www.xilinx.com/products/boards-and-kits/ek-u1-zcu102-g.html) + [FMCOMMS2/3/4](https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/eval-ad-fmcomms2.html)|Done|[64bit img](https://users.ugent.be/~xjiao/openwifi-1.3.0-wilsele-64bit.img.xz)|Need 59zcu102_9371|[Xilinx ZCU102 board](https://www.xilinx.com/products/boards-and-kits/ek-u1-zcu102-g.html) + [ADRV9371](https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/eval-adrv9371.html)|Future|Future|Need 60 61- board_name is used to identify FPGA design in openwifi-hw/boards/ 62- Don't have any boards? Or you like JTAG boot instead of SD card? Check our test bed [w-iLab.t](https://doc.ilabt.imec.be/ilabt/wilab/tutorials/openwifi.html) tutorial. 63 64[[Quick start](#Quick-start)] 65[[Basic operations](#Basic-operations)] 66[[Update FPGA](#Update-FPGA)] 67[[Update Driver](#Update-Driver)] 68[[Update sdrctl](#Update-sdrctl)] 69[[Easy Access and etc](#Easy-Access-and-etc)] 70 71[[Build openwifi Linux img from scratch](#Build-openwifi-Linux-img-from-scratch)] 72[[Special note for 11b](#Special-note-for-11b)] 73[[Porting guide](#Porting-guide)] 74[[Project document](doc/README.md)] 75[[Application notes](doc/app_notes/README.md)] 76 77## Quick start 78- Restore openwifi board specific img file (from the table) into a SD card. To do this, program "Disks" in Ubuntu can be used (Install: "sudo apt install gnome-disk-utility"). After restoring, the SD card should have two partitions: BOOT and rootfs. You need to config the **correct files in the BOOT partition** according to the **board you have** by operation on your computer: 79 - Copy files in **openwifi/board_name** to the base directory of BOOT partition. 80 - Copy **openwifi/zynqmp-common/Image** (zcu102 board) or **openwifi/zynq-common/uImage** (other boards) to the base directory of BOOT partition 81- Connect two antennas to RXA/TXA ports. Config the board to SD card boot mode (check the board manual). Insert the SD card to the board. Power on. 82- Login to the board from your PC (PC Ethernet should have IP 192.168.10.1) with password **openwifi**. 83 ``` 84 ssh [email protected] 85 ``` 86- Then, run openwifi AP and the on board webserver 87 ``` 88 cd openwifi 89 ./wgd.sh 90 ./fosdem.sh 91 (Use "./wgd.sh 1" to enable experimental AMPDU aggregation on top of 11n) 92 (Use "./fosdem-11ag.sh" to force 11a/g mode) 93 ``` 94 **NOTE** adrv9361z7035 has ultra low TX power in 5GHz. Move **CLOSER** when you use that board in 5GHz!!! 95- After you see the "openwifi" SSID on your device (Phone/Laptop/etc), connect it. Browser to 192.168.13.1 on your device, you should see the webpage hosted by the webserver on board. 96 - Note 1: If your device doesn't support 5GHz (ch44), please change the **hostapd-openwifi.conf** on board and re-run fosdem.sh. 97 - Note 2: After ~2 hours, the Viterbi decoder will halt (Xilinx Evaluation License). Just power cycle the board if it happens. (If output of "./sdrctl dev sdr0 get reg rx 20" is always the same, it means the decoder halts) 98- To give the Wi-Fi client internet access, configure routing/NAT **on the PC**: 99 ``` 100 sudo sysctl -w net.ipv4.ip_forward=1 101 sudo iptables -t nat -A POSTROUTING -o NICY -j MASQUERADE 102 sudo ip route add 192.168.13.0/24 via 192.168.10.122 dev ethX 103 ``` 104 **ethX** is the PC NIC name connecting the board ethernet. **NICY** is the PC NIC name connecting internet (WiFi or another ethernet). 105 106 If you want, uncommenting "net.ipv4.ip_forward=1" in /etc/sysctl.conf to make IP forwarding persistent on PC. 107- To monitor **real-time CSI (Chip State Information)**, such as timestamp, frequency offset, channel state, equalizer, please refer to [[CSI notes](doc/app_notes/csi.md)]. 108 109## Basic operations 110The board actually is an Linux/Ubuntu computer which is running **hostapd** to offer Wi-Fi AP functionality over the Wi-Fi Network Interface (NIC). The NIC is implemented by openwifi-hw FPGA design. We use the term **"On board"** to indicate that the commands should be executed after ssh login to the board. **"On PC"** means the commands should run on PC. 111- Bring up the openwifi NIC sdr0: 112 ``` 113 cd ~/openwifi && ./wgd.sh 114 (Use "./wgd.sh 1" to enable experimental AMPDU aggregation) 115 ``` 116- Use openwifi as client to connect other AP (Change wpa-connect.conf on board firstly): 117 ``` 118 route del default gw 192.168.10.1 119 wpa_supplicant -i sdr0 -c wpa-connect.conf & 120 dhclient sdr0 121 ``` 122- Use openwifi in ad-hoc mode: Please check **sdr-ad-hoc-up.sh**, **sdr-ad-hoc-join.sh** and [this app note](./doc/app_notes/ad-hoc-two-sdr.md). 123- Use openwifi in monitor mode: Please check **monitor_ch.sh** and [this app note](./doc/app_notes/inject_80211.md). 124- The Linux native Wi-Fi tools/Apps (iwconfig/ifconfig/iwlist/iw/hostapd/wpa_supplicant/etc) can run over openwifi NIC in the same way as commercial Wi-Fi chip. 125- **sdrctl** is a dedicated tool to access openwifi driver/FPGA, please check [project document](./doc/README.md) for more information. 126 127## Update FPGA 128 129(Check [Driver and FPGA dynamic reloading app note](./doc/app_notes/drv_fpga_dynamic_loading.md) for more convenient way of updating FPGA and driver files) 130 131Since the pre-built SD card image might not have the latest bug-fixes/updates, it is recommended to always copy the latest files in the [user_space](./user_space) directory on to the board. Then update the fpga bitstream and driver (see next section) on to the board. 132 133- Install Vivado/SDK 2018.3 (Vivado Design Suite - HLx Editions - 2018.3 Full Product Installation. If you don't need to generate new FPGA bitstream, WebPack version without license is enough) 134- Setup environment variables (use absolute path): 135 ``` 136 export XILINX_DIR=your_Xilinx_install_directory 137 (Example: export XILINX_DIR=/opt/Xilinx. The Xilinx directory should include sth like: Downloads, SDK, Vivado, xic) 138 export OPENWIFI_HW_DIR=your_openwifi-hw_directory 139 (The directory where you store the open-sdr/openwifi-hw repo via git clone) 140 export BOARD_NAME=your_board_name 141 ``` 142- Pick the FPGA bitstream from openwifi-hw, and generate BOOT.BIN and transfer it on board via ssh channel: 143 ``` 144 For Zynq 7000: 145 146 cd openwifi/user_space; ./boot_bin_gen.sh $OPENWIFI_HW_DIR $XILINX_DIR $BOARD_NAME 147 148 For Zynq MPSoC (like zcu102 board): 149 cd openwifi/user_space; ./boot_bin_gen_zynqmp.sh $OPENWIFI_HW_DIR $XILINX_DIR $BOARD_NAME 150 151 cd openwifi/kernel_boot/boards/$BOARD_NAME/output_boot_bin; scp ./BOOT.BIN [email protected]: 152 ``` 153- On board: Put the BOOT.BIN into the BOOT partition. 154 ``` 155 mount /dev/mmcblk0p1 /mnt 156 cp ~/BOOT.BIN /mnt 157 cd /mnt 158 sync 159 cd ~ 160 umount /mnt 161 ``` 162 **Power cycle** the board to load new FPGA bitstream. 163 164 To load FPGA dynamically without rebooting/power-cycle, check [Driver and FPGA dynamic reloading app note](./doc/app_notes/drv_fpga_dynamic_loading.md). 165 166## Update Driver 167 168(Check [Driver and FPGA dynamic reloading app note](./doc/app_notes/drv_fpga_dynamic_loading.md) for more convenient way of updating FPGA and driver files) 169 170Since the pre-built SD card image might not have the latest bug-fixes/updates, it is recommended to always copy the latest files in the [user_space](./user_space) directory on to the board. Then update the fpga bitstream (see previous section) and driver on to the board. 171 172- Prepare Analog Devices Linux kernel source code (only need to run once): 173 ``` 174 cd openwifi/user_space; ./prepare_kernel.sh $XILINX_DIR ARCH_BIT build 175 (For Zynq 7000, ARCH_BIT should be 32, for Zynq MPSoC, ARCH_BIT should be 64) 176 ``` 177 **Note**: In Ubuntu, gcc-10 might have issue ('yylloc' error), so use gcc-9 if you encounter error. 178- Compile the latest openwifi driver 179 ``` 180 cd openwifi/driver; ./make_all.sh $XILINX_DIR ARCH_BIT 181 (For Zynq 7000, ARCH_BIT should be 32, for Zynq MPSoC, ARCH_BIT should be 64) 182 (More arguments (max 5) beyond above two will be converted to "#define argument" in pre_def.h for conditional compiling) 183 ``` 184- Copy the driver files to the board via ssh channel 185 ``` 186 cd openwifi/driver; scp `find ./ -name \*.ko` [email protected]:openwifi/ 187 ``` 188 Now you can use **wgd.sh** on board to load the new openwifi driver. **wgd.sh** also tries to reload FPGA img if system_top.bit.bin presents in the same directory. 189 Find more information in [Driver and FPGA dynamic reloading app note](./doc/app_notes/drv_fpga_dynamic_loading.md). 190 191 **Note**: If you have symbol or version error while loadng the driver, it could be because the kernel in the SD card image is too old. In this case, you need to follow [[Build openwifi Linux img from scratch](#Build-openwifi-Linux-img-from-scratch)] to generate your new SD card image. 192 193## Update sdrctl 194- Copy the sdrctl source files to the board via ssh channel 195 ``` 196 cd openwifi/user_space/sdrctl_src; scp `find ./ -name \*` [email protected]:openwifi/sdrctl_src/ 197 ``` 198- Compile the sdrctl **on board**: 199 ``` 200 cd ~/openwifi/sdrctl_src/ && make && cp sdrctl ../ && cd .. 201 ``` 202## Easy Access and etc 203 204- Check [Driver and FPGA dynamic reloading app note](./doc/app_notes/drv_fpga_dynamic_loading.md) for more convenient way of updating FPGA and driver files. 205- FPGA and driver on board update scripts 206 - Setup [ftp server](https://ubuntu.com/server/docs/service-ftp) on PC, allow anonymous and change ftp root directory to the openwifi directory. 207 - On board: 208 ``` 209 ./sdcard_boot_update.sh $BOARD_NAME 210 (Above command downloads uImage, BOOT.BIN and devicetree.dtb, then copy them into boot partition. Remember to power cycle) 211 ./wgd.sh remote 212 (Above command downloads driver files, and brings up sdr0) 213 ``` 214- Access the board disk/rootfs like a disk: 215 - On PC: "File manager --> Connect to Server...", input: sftp://[email protected]/root 216 - Input password "openwifi" 217 218## Build openwifi Linux img from scratch 219- Install the devicetree compiler -- dtc. (For Ubuntu: sudo apt install device-tree-compiler) 220- Install the mkimage tool. (For Ubuntu: sudo apt install u-boot-tools) 221- Download [2019_R1-2020_06_22.img.xz](http://swdownloads.analog.com/cse/2019_R1-2020_06_22.img.xz) from [Analog Devices Wiki](https://wiki.analog.com/resources/tools-software/linux-software/zynq_images). Burn it to a SD card. 222- Insert the SD card to your Linux PC. Find out the mount point (that has two sub directories BOOT and rootfs), and setup environment variables (use absolute path): 223 ``` 224 export SDCARD_DIR=sdcard_mount_point 225 export XILINX_DIR=your_Xilinx_install_directory 226 export OPENWIFI_HW_DIR=your_openwifi-hw_directory 227 export BOARD_NAME=your_board_name 228 ``` 229- Run script to update SD card: 230 ``` 231 cd openwifi/user_space; ./update_sdcard.sh $OPENWIFI_HW_DIR $XILINX_DIR $BOARD_NAME $SDCARD_DIR 232 ``` 233- Config your board to SD card boot mode (check the board manual). Insert the SD card to the board. Power on. 234- Login to the board from your PC (PC Ethernet should have IP 192.168.10.1) with one time password **analog**. 235 ``` 236 ssh [email protected] 237 ``` 238- Setup routing/NAT **on the PC** for your board -- this internet connection is **important** for post installation/config. 239 ``` 240 sudo sysctl -w net.ipv4.ip_forward=1 241 sudo iptables -t nat -A POSTROUTING -o NICY -j MASQUERADE 242 sudo ip route add 192.168.13.0/24 via 192.168.10.122 dev ethX 243 ``` 244 **ethX** is the PC NIC name connecting the board ethernet. **NICY** is the PC NIC name connecting internet (WiFi or another ethernet). 245 246 If you want, uncommenting "net.ipv4.ip_forward=1" in /etc/sysctl.conf to make IP forwarding persistent on PC. 247- Run **one time** script on board to complete post installation/config (After this, password becomes **openwifi**) 248 ``` 249 cd ~/openwifi && ./post_config.sh 250 ``` 251- Now you can start from [Quick start](#Quick-start) (Skip the image download and burn step) 252 253## Special note for 11b 254 255Openwifi only applies OFDM as its modulation scheme and as a result, it is not backward compatible with 802.11b clients or modes of operation. This is usually the case during beacon transmission, connection establishment, and robust communication. 256 257As a solution to this problem, openwifi can be fully controlled only if communicating with APs/clients instantiated using hostapd/wpa_supplicant userspace programs respectively. 258 259For hostapd program, 802.11b rates can be suppressed using configuration commands (i.e. supported_rates, basic_rates) and an example configuration file is provided (i.e. hostapd-openwifi.conf). One small caveat to this one comes from fullMAC Wi-Fi cards as they must implement the *NL80211_TXRATE_LEGACY* NetLink handler at the device driver level. 260 261On the other hand, the wpa_supplicant program on the client side (commercial Wi-Fi dongle/board) cannot suppress 802.11b rates out of the box in 2.4GHz band, so there will be an issue when connecting openwifi (OFDM only). A patched wpa_supplicant should be used at the client side. 262``` 263sudo apt-get install libssl1.0-dev 264cd openwifi/user_space; ./build_wpa_supplicant_wo11b.sh 265``` 266## Porting guide 267 268This section explains the porting work by showing the differences between openwifi and Analog Devices reference design. openwifi is based on 2019_R1 of [HDL Reference Designs](https://github.com/analogdevicesinc/hdl). 269- Open the fmcomms2 + zc706 reference design at hdl/projects/fmcomms2/zc706 (Please read Analog Devices help) 270- Open the openwifi design zc706_fmcs2 at openwifi-hw/boards/zc706_fmcs2 (Please read openwifi-hw repository) 271- "Open Block Design", you will see the differences between openwifi and the reference design. Both in "diagram" and in "Address Editor". 272- The address/interrupts of FPGA blocks hooked to the ARM bus should be put/aligned to the devicetree file openwifi/kernel_boot/boards/zc706_fmcs2/devicetree.dts. Linux will parse the devicetree.dtb when booting to know information of attached device (FPGA blocks in our case). 273- We use dtc command to get devicetree.dts converted from devicetree.dtb in [Analog Devices Linux image](https://wiki.analog.com/resources/tools-software/linux-software/zynq_images), then do modification according to what we have added/modified to the reference design. 274- Please learn the script in [[Build openwifi Linux img from scratch](#Build-openwifi-Linux-img-from-scratch)] to understand how we generate devicetree.dtb, BOOT.BIN and Linux kernel uImage and put them together to build the full SD card image. 275 276## License 277 278This project is available as open source under the terms of the AGPL 3.0 Or later. However, some elements are being licensed under GPL 2-0 or later and BSD 3 license . For accurate information, please check individual files. 279
