# Project Structure * **doc** Contains all releavnt documentation need for this project * **download** Contains various files downloaded for this project * **corebundle-mst_lab.zip** First version of Custom Xillybus IP Core implementation generated by "IP Core Factory" * `xillybus_debug`: Upstream, 32-bits, 256 B/s, General Purpose * `xillybus_config`: Downstream, 16-bits, 204.8 kB/s, Address/Data Interface (16 address bits) * `xillybus_audio`: Upstream/Downstream, 32-bits, 204.8 kB/s, Data acquisition/Playback * `xillybus_smb`: Upstream/Downstream, 8-bits, 10.24 kB/s, Command and Status * **corebundle-mst_lab2.zip** Second version of Custom Xillybus IP Core implementation generated by "IP Core Factory". Currently in use * `xillybus_debug`: Upstream, 32-bits, 256 B/s, General Purpose * `xillybus_config`: Downstream, 32-bits, 204.8 kB/s, Address/Data Interface (16 address bits) * `xillybus_audio`: Upstream/Downstream, 32-bits, 204.8 kB/s, Data acquisition/Playback * `xillybus_smb`: Upstream/Downstream, 8-bits, 10.24 kB/s, Command and Status * **CypressDriverInstaller_1.exe** Windows drivers for zedboard USB-UART * **xillinux-2.0.img.gz** Xillinux SD Card image * **xillinux-eval-zedboard-2.0c.zip** Zedboard Xillybus demo project * **modelsim** Contains .do files for modelsim simulation * **src** Constains the actual vhdl source files for this project * **sim** Contains the simulation testbenches * **UNUSED** Contains (partially) implemented logic that is not used in the final version * **sw** Contains the software that allows to communicate with the FPGA logic from Linux through the Xillybus API * **syn** Contains a zedboard Vivado test project used to test various parts of the VHDL implementation * **xillinux-syn** Contains the final Vivado project implementing the xillybus IP core, ZYNQ System, and instantiating our FPGA logic. This is a modified version of the xillybus-demo project * **vivado** Contains the actual Vivado Project file * **vhdl/src** Cotains the project top entity (`xillydemo.vhd`). The FPGA logic in instantiated in this file * The rest of the directories are taken verbatim from the demo project and are necessary for all the peripheral components used by xillinux. # Board Mapping JC1 PMOD Connector (Upper Row) | PMOD-AD1 Board JD1 PMOD Connector (Upper Row) | PMOD-DA3 Board JA1 PMOD JA1 Pin | Optional External Clock [NOTE: Clk has to be connected in VHDl and PLL has to be reconfigured accordingly] JA1 PMOD JA4 Pin | External SYNC Pulse [NOTE: if pin is left unconnected (floating), it will register as a pulse] SW7 | Standby / Write Mode (Allows xillinux to write configuration) LED7 | Standby Status BTNC | Global reset BTNU | Debug value reset # Project Description ![alt text](feedback.png "Feed back Loop") This project implements the above feedback loop in FPGA logic. The components of the feedback loop are analysed below: * **ADC** The ADC (PMOD-AD1) is capable of operating at a maximum frequency of 20 MHz, and converting an analog signal every 18 clock cycles (ca 1.1 MHz Sampling Frequency). All PMOD Connectors on the Zedboard are fixed to 3.3V, hence the ADC can convert analog signals in the range 0V-3.3V to 12-bits. * **ADC** The DAC (PMOD-DA3) is capable of operating at a maximum frequency of 50 MHz, and converting a digital signal every 16 clock cycles (ca 1.25 MHz). The DAC uses an internal 2.5 V Voltage reference (uncorrelated to the used VCC Voltage), and can thus convert 16-bits to 0V-2.5V. * **DELAY LINE** The delay line allows to delay the converted ADC values by a pre-specified amount of clock cycles. * **SCALER** The scaler allows the converted ADc values to be downscaled. It uses a 5-bit multiplication factor that is intepreted as a 1Q4 (1-Bit Integer, 4-Bit Fractional) fixed point number. Note that the factor should only take values between 0 and 16 (decimal), as due to the internal connection (truncat highest bit) using higher numbers can (and will) result to overflow conditions. e.g. A value of 16(decimal) is intepreted as scaling by 1, a value of 15 (decimal) is intepreted as scaling by 0.9375, and a value of 8 is is intepreted as scaling by 0.5. * **ADD/SUB** The ADD/SUB allows to either add or subtract the scaler output from the MUX output. (Allowing to either implement a positive, or negative feedback loop). * **MUX** The MUX selects between the second ADC channel or zero (GND), allowing a "neutral" feedback. ## Timing Considerations The whole system is clocked at 20 MHz (highest supported frequency of ADC). The *ADD/SUB* and *Scaler* have a 1-stage pipeline, meaning that if the *Delay Line* is configured with 0 delay, the feedback loop follows the 18 clock cycle cadence of the ADC without additional delay. In order to re-align the inputs of the *ADD/SUB*, the second channel of the ADC is latched (delayed) for one clock cycle (not shown in diagram). # USAGE ## Preperation * Write the image contained in `download/xillinux-2.0.img.gz` to the SD card. * Copy the files in the `xillinux-syn/bootfiles` directory into the first partition of the SD Card * Open the Vivado Project under `xillinux-syn/vivado/xillydemo.xpr` and generate the Bitstreamfile * Copy the Bitstreamfile into the first partition of the SD Card * Follow the instruction in Chapter 4 of `doc/Xillybus/xillybus_getting_started_zynq.pdf` to set the correct switch/jumper positions * Connect SD Card to Zedboard * Connect the USB cable to the *UART* port. The UART uses the 8N1 format and a baudrate of 115200. * Optionally you can also connect VGA monitor, audio, keyboard/mouse (using USB-OTG), as the xillinux is a fully fledged Linux OS. ## Boot The UART should automatically connect to a root shell (after U-Boot did it's thing). The root user has no password set. The system should be halted (using the `halt` or `shutdown now` command) before powering off the board. ## Configuration The FPGA logic contains a configuration memory with a pre-defined (changable in `typedef_package.vhd`) number of configuration "slots". Each slot contains the configuration for the feedback loop (Delay Line clock count, scaler factor, add/sub selection, MUX selection), and a timestamp. The timestamp defines the number of clock cycles from the rising edge of the SYNC pulse signal after which the configuration described by the slot is applied. It makes sense for the first configuration slot to have a timestamp of 0. The slots are processed in write order, and not in timestamp order. (Thus slots should have increasing timestamp values). NOTE: It is valid for a configuration slot to have a timestamp lower than the previous. The slot will be applied for at least 1 clock cycle before the next slot can be applied. The `xillybus_config` linux device file is used to write to the configuration memory of the FPGA. Note that the standby switch has to be enabled (Standby status led on). As long as the standby switch is enabled, the feedback loop is held in reset. The `write_config.c` C program can be used to write the configuration memory of the FPGA. e.g. `./write_config config /dev/xillybus_config` ### Config File Each line of this file defines a configuration slot and consists of integer numbers delimited by white spaces in the following order: ADDSUB_MODE ADD_INPUT_MUX DELAY FACTOR TIMESTAMP * ADDSUB_MODE: Select feedback mode (0=negative, 1=positive) * ADD_INPUT_MUX: Select feedback input (0=GND[only ADC Input 1], 1=ADC Input 2[Both ADC inputs are used]) * DELAY: Clock cycles counts (50 ns period) to delay the feedback signal [0-255] * FACTOR: Multiplication factor to apply to the feedback signal [0-16] (NOTE: Integer is intepreted as a 1Q4 Fixed Point Number!) * TIMESTAMP: Defines the clock count number from the sync pulse from which on the configurations settings will be applied. [32-bit unsigned integer] ## Debug The FPGA logic allows debug values to be sent to the Linux via the `xillybus_debug` device file. Currently the FPGA logic sends every second the max values of the both ADC channels, Scaler output, and DAC. The max values can be externally reset (see Mapping). The `read_debug.c` C program can be used to read the debug values. Since the program enters an endless loop, a signal handler has beeen implemented and the program can be safely terminated with `CTRL-C` and co. e.g. `./read_debug /dev/xillybus_debug`