RFSoC QPSK Transceiver
This repo contains all the files needed to build and run the RFSoC QPSK demonstrator that was presented at both FPL and XDF conferences in 2018. The design is a full QPSK transceiver, which transmits and receives randomly-generated pulse-shaped symbols with full carrier and timing synchronisation. PYNQ is used to visualise the data at both the DAC and ADC side of the RFSoC data converters, as well as visualising various DSP stages throughout the transmit and receive signal path.
Connect to the board with Jupyter Lab in a browser (not Jupyter Notebook) @
Open a terminal in Jupyter Lab and run:
pip3 install --upgrade git+https://github.com/strath-sdr/rfsoc_qpsk.git jupyter labextension install @firstname.lastname@example.org jupyter labextension install email@example.com jupyter labextension install @firstname.lastname@example.org
Use Chrome if possible — the rendering performance is important.
We use DAC2 from tile 229 to transmit and ADC0 from tile 224 to receive. These correspond to connections J5 and J4 on the HW-FMC-XM500 daughter board respectively. SW6 on the ZCU111 must be set to boot from SD card (as shown in the image below).
Using the Project Files
All software builds have been tested on Ubuntu 16.04
- Vivado Design Suite 2018.3
- System Generator for DSP
- MATLAB 2017b
The Tx and Rx IPs are in separate directories in
rfsoc_qpsk/board/sysgen/ that can be opened using the appropriate System Generator dialogue. Due to the large amount of decimation and interpolation in both IPs, simulating the output can take an extraordinarily long time. A less extreme multirate system would simulate much faster!
This project can be built with Vivado from the command line:
cd rfsoc_qpsk/board/ZCU111/ source <Xilinx_dir>/Vivado/2018.3/settings64.sh vivado -mode batch -nojournal -nolog -source write_project.tcl
The tcl file creates a new project and builds the IPI block design, but does not generate a bitstream as there is already a valid one in the repo.
- Live plots are currently quite demanding of the client browser (but not the RFSoC). A hefty desktop helps a lot in the meantime!
- There is a large drop in gain between the ADC and the final output