Gateware/Software for Event Fanout/Receiver
This repository contains both gateware and software for the Event Fanout/Receiver
To build the gateware the following dependencies are needed:
- GNU Make
- Xilinx Vivado (2020.2.2 tested), available here
- Xilinx Vitis (2020.2.2 tested), available here
Make sure vivado and vitis are in PATH.
To build the software the following dependencies are needed:
- mb-gcc toolchain, bundled within Vitis
With the dependencies in place a simple make should be able to generate
both gateware and software:
makeA suggestion in running the make command is to measure the time
and redirect stdout/stderr to a file so you can inspect it later:
ARM_TOOLCHAIN_LOCATION=/media/Xilinx/Vivado/2020.2.2/Vitis/2020.2/gnu/microblaze/lin
(time make CROSS_COMPILE=${ARM_TOOLCHAIN_LOCATION}/bin/mb- APP=evfr PLATFORM=marble && notify-send 'Compilation SUCCESS' || notify-send 'Compilation ERROR'; date) 2>&1 | tee make_outputFor now the following combinations of PLATFORM and APP are supported:
| APP / PLATFORM | marble |
|---|---|
| evfr | x |
| kd | x |
So, for example, to generate the EVFR application for the Marble board:
ARM_TOOLCHAIN_LOCATION=/media/Xilinx/Vivado/2020.2.2/Vitis/2020.2/gnu/microblaze/lin
(time make CROSS_COMPILE=${ARM_TOOLCHAIN_LOCATION}/bin/mb- APP=evfr PLATFORM=marble && notify-send 'Compilation SUCCESS' || notify-send 'Compilation ERROR'; date) 2>&1 | tee make_outputAdd TESTING_OPTION=USE_QSFP_FANOUT to the make command to enable the fanout via QSFP2. Note that it's a testing feature and the fanout latency is not fully deterministic but can vary by approximately one clock period.
To deploy the gateware and the software we can use a variety of methods. For development, JTAG is being used.
The following script can download the gateware/software via JTAG:
cd scripts
./deploy.sh software/app/<APP>/download<APP_UPPERCASE>.bitUsually, APP=evfr or APP=kd depending on the desired target.