xref: /openwifi/doc/app_notes/iq.md (revision 5deb8d18f6d13bc809afd5109593e0982888373c)
1We implement the **IQ sample capture** with interesting extensions: many **trigger conditions**; **RSSI**, RF chip **AGC** **status (lock/unlock)** and **gain**.
2
3## Quick start
4- Power on the SDR board.
5- Connect a computer to the SDR board via Ethernet cable. The computer should have static IP 192.168.10.1. Open a terminal on the computer, and then in the terminal:
6  ```
7  ssh [email protected]
8  (password: openwifi)
9  cd openwifi
10  ./wgd.sh
11  (Wait for the script completed)
12  ./monitor_ch.sh sdr0 11
13  (Monitor on channel 11. You can change 11 to other channel that is busy)
14  insmod side_ch.ko iq_len_init=8187
15  (for zed, adrv9364z7020, zc702 board, 8187 should be 4095 because they have smaller FPGA)
16
17  ./side_ch_ctl wh11d4094
18  (Above command is needed only when you run with zed, adrv9364z7020, zc702 board)
19
20  ./side_ch_ctl g
21  ```
22  You should see on board outputs like:
23  ```
24  loop 64 side info count 61
25  loop 128 side info count 99
26  ...
27  ```
28  If the second number (side info count 61, 99, ...) keeps increasing, that means the trigger condition is met from time to time and the IQ sample is going to the computer smoothly.
29
30- Open another terminal on the computer, and run:
31  ```
32  cd openwifi/user_space/side_ch_ctl_src
33  python3 iq_capture.py
34  (for zed, adrv9364z7020, zc702 board, add 4095 as parameter!)
35  ```
36  The python script needs "matplotlib.pyplot" and "numpy" packages installed. Now you should see 3 figures showing run-time **IQ sample**, **AGC gain and lock status** and **RSSI (uncalibrated)**. Meanwhile the python script prints the **timestamp**.
37
38  While running, all informations are also stored into a file **iq.txt**. A matlab script **test_iq_file_display.m** is offered to help you do analysis on the IQ Information offline. For zed, adrv9364z7020, zc702 board, do not forget to change the **iq_len** in the matlab script to 4095.
39
40## Understand the IQ capture feature
41  The IQ information is extracted via the openwifi **side channel** infrastructure. This figure explains the related modules (also related source code file name) and how the information goes from the SDR board to the computer.
42  ![](./iq-architecture.jpg)
43
44  The IQ information format is shown in this figure.
45  ![](./iq-information-format.jpg)
46
47  For each element, the actual size is 64bit.
48  - timestamp: 64bit TSF timer value when the capture is triggered.
49  - IQ
50    - The first two 16bit are used for I/Q sample from the antenna currently used
51    - The 3rd 16bit is AD9361 AGC gain (bit7 -- lock/unlock; bit6~0 -- gain value)
52    - The 4th 16bit is RSSI (half dB, uncalibrated). Please check xpu.v and sdr.c to understand how the raw RSSI value is finally calibrated and reported to Linux mac80211.
53
54  The python and Matlab scripts are recommended for you to understand the IQ packet format precisely.
55
56## Config the IQ capture and interval
57  The quick start guide captures a period of history IQ when the packet FCS checksum is checked by Wifi receiver (no matter pass or fail). To initiate the capture with different trigger conditions and length, configuration commands should be issued before executing "**side_ch_ctl g**". The configuration command is realized by feeding a different parameter to "**side_ch_ctl**". The main parameters that are configurable are explained in this figure.
58  ![](./iq-capture-parameter.jpg)
59
60  **iq_len** is the number of IQ samples captured per trigger condition met. The capture is started from the time **pre_trigger_len** IQ samples before the trigger moment. **iq_len** is set only one time when you insert the side_ch.ko. Please check the next section for **iq_len** configuration. This section introduces the setting of pre_trigger_len and trigger condition.
61  - pre_trigger_len
62  ```
63  ./side_ch_ctl wh11dY
64  ```
65  The parameter **Y** specifies the pre_trigger_len. Valid range 0 ~ 8190. It is limited by the FPGA fifo size. For **small FPGA** (zed_fmcs2, adrv9364z7020, zc702), the valid range is 0 ~ **4094**.
66  - trigger condition
67  ```
68  ./side_ch_ctl wh8dY
69  ```
70  The parameter **Y** specifies the trigger condition. Valid range 0 ~ 31, which is explained in this table.
71
72  value|meaning
73  -----|-------
74  0 |receiver gives FCS checksum result. no matter pass/fail
75  1 |receiver gives FCS checksum result. pass
76  2 |receiver gives FCS checksum result. fail
77  3 |receiver gives SIGNAL field checksum result. no matter pass/fail
78  4 |receiver gives SIGNAL field checksum result. pass
79  5 |receiver gives SIGNAL field checksum result. fail
80  6 |receiver gives SIGNAL field checksum result. no matter pass/fail. HT packet
81  7 |receiver gives SIGNAL field checksum result. no matter pass/fail. non-HT packet
82  8 |receiver gives  long preamble detected
83  9 |receiver gives short preamble detected
84  10|RSSI (half dB uncalibrated) goes above the threshold
85  11|RSSI (half dB uncalibrated) goes below the threshold
86  12|AD9361 AGC from lock to unlock
87  13|AD9361 AGC from unlock to lock
88  14|AD9361 AGC gain goes above the threshold
89  15|AD9361 AGC gain goes below the threshold
90  16|phy_tx_started signal from openofdm tx core
91  17|phy_tx_done signal from openofdm tx core
92  18|positive edge of tx_bb_is_ongoing from xpu core
93  19|negative edge of tx_bb_is_ongoing from xpu core
94  20|positive edge of tx_rf_is_ongoing from xpu core
95  21|negative edge of tx_rf_is_ongoing from xpu core
96  22|phy_tx_started and this tx packet needs ACK
97  23|phy_tx_done and this tx packet needs ACK
98  24|positive edge of tx_bb_is_ongoing and this tx packet needs ACK
99  25|negative edge of tx_bb_is_ongoing and this tx packet needs ACK
100  26|positive edge of tx_rf_is_ongoing and this tx packet needs ACK
101  27|negative edge of tx_rf_is_ongoing and this tx packet needs ACK
102  28|tx_bb_is_ongoing and I/Q amplitude from the other antenna is above rssi_or_iq_th
103  29|tx_rf_is_ongoing and I/Q amplitude from the other antenna is above rssi_or_iq_th
104  30|demod_is_ongoing from openofdm_rx and phy_tx_start is issued
105  31|demod_is_ongoing from openofdm_rx and tx_bb_is_ongoing from xpu core is valid
106
107  To set the RSSI threshold
108  ```
109  ./side_ch_ctl wh9dY
110  ```
111  The parameter **Y** specifies the RSSI threshold. Valid range 0 ~ 2047.
112
113  To set the AGC gain threshold
114  ```
115  ./side_ch_ctl wh10dY
116  ```
117  The parameter **Y** specifies the AGC gain threshold. Valid range 0 ~ 127.
118
119  The command "**side_ch_ctl g**" will perform IQ capture every 100ms until you press ctrl+C. To use a different capture interval:
120  ```
121  side_ch_ctl gN
122  ```
123  The interval will become N*1ms
124
125## Config the iq_len
126  The **iq_len** (number of IQ sample per capture) is configurable in case you want less IQ samples per capture so that it can be triggered more times during a specific analysis period. The valid value is 1~**8187**. For **small FPGA** (zed_fmcs2, adrv9364z7020, zc702), the valid range is 0 ~ **4095**. It is independant from pre_trigger_len, and it can be less than pre_trigger_len if you want. You should align the **iq_len** value at the side_ch.ko, iq_capture.py and test_iq_file_display.m.
127  - When insert the kernel module, use:
128  ```
129  insmod side_ch.ko iq_len_init=3000
130  ```
131  Here 3000 is an example. **ATTENTION:** You need to specify **iq_len_init** explicitly to turn on IQ capture, which will turn off the default CSI mode. Insert the side_ch.ko without any parameter will run the default CSI mode.
132  - When launch the python script, use:
133  ```
134  python3 iq_capture.py 3000
135  ```
136  - When use the matlab script, please change the **iq_len** variable in the script to 3000.
137
138## Compile the side channel driver and user space program
139  - side_ch.ko
140  ```
141  $OPENWIFI_DIR/driver/side_ch/make_driver.sh $OPENWIFI_DIR $XILINX_DIR ARCH_BIT
142(For Zynq 7000, ARCH_BIT should be 32, for Zynq MPSoC, ARCH_BIT should be 64)
143  ```
144  - side_ch_ctl (take user_space/side_ch_ctl_src/side_ch_ctl.c and compile it on board!)
145  ```
146  gcc -o side_ch_ctl side_ch_ctl.c
147  ```
148
149## Run the IQ capture together with modes other than monitor
150  The openwifi IQ capture feature could run with not only monitor mode but also other modes, such as AP-Client or ad-hoc mode. After the communication functionality is fully up in those modes, you can start IQ capture from "**insmod side_ch.ko**" and "**./side_ch_ctl g**" on board as described in the previous sections to extract IQ information to your computer.
151
152## Map the IQ information to the WiFi packet
153  If you want to relate the IQ information to the WiFi packet, you need to capture WiFi packets (tcpdump/wireshark/etc) while capturing IQ. Then you can relate the timestamp between WiFi packet and IQ information. Please be noticed that the timestamp in the IQ information is the moment when capture is triggered, which could be different from the timestamp reported in the packet capture program. But since they share the same time base (TSF timer), you can relate them easily by analyzing the WiFi packet and IQ sample sequence.
154
155  Please learn the python and Matlab script to extract IQ information per capture according to your requirement.
156