Proton Calorimetry/Equipment/FPGAs DDC232 - Revision history

SimonJolly at 16:11, 29 May 2024

2024-05-29T16:11:56Z

← Older revision		Revision as of 16:11, 29 May 2024
Line 2:		Line 2:
	==Technical Documents==		==Technical Documents==
	*[https://www.ti.com/lit/gpn/ddc232 DDC232 datasheet]. This contains essential information from which the FPGA design was created.		*[https://www.ti.com/lit/gpn/ddc232 DDC232 datasheet]. This contains essential information from which the FPGA design was created.
			*[https://digilent.com/shop/usb104-a7-artix-7-fpga-development-board-with-syzygy-compatible-expansion/ USB104 FPGA product page].
			*[https://digilent.com/reference/programmable-logic/usb104a7/ USB104 Resource Centre].
			*[https://digilent.com/reference/programmable-logic/usb104a7/reference-manual USB104 Reference Manual].
			*[https://digilent.s3-us-west-2.amazonaws.com/resources/programmable-logic/usb104a7/USB104_A7_sch.pdf USB104 Schematics].
	*[https://reference.digilentinc.com/reference/programmable-logic/nexys-video/reference-manual Nexys Video manual].		*[https://reference.digilentinc.com/reference/programmable-logic/nexys-video/reference-manual Nexys Video manual].
	*[https://www.xilinx.com/support/documentation/ip_documentation/clk_wiz/v5_3/pg065-clk-wiz.pdf Xilinx Clocking Wizard manual].		*[https://www.xilinx.com/support/documentation/ip_documentation/clk_wiz/v5_3/pg065-clk-wiz.pdf Xilinx Clocking Wizard manual].

SimonJolly: SimonJolly moved page Proton Calorimetry/Equipment/ZyboZ7 DDC232 to Proton Calorimetry/Equipment/FPGAs DDC232: Misspelled title

2024-05-29T16:07:41Z

SimonJolly moved page Proton Calorimetry/Equipment/ZyboZ7 DDC232 to Proton Calorimetry/Equipment/FPGAs DDC232: Misspelled title

← Older revision		Revision as of 16:07, 29 May 2024
(No difference)

SoniaEscribano: /* Configuring the FPGA */

2024-02-15T10:54:36Z

Configuring the FPGA

← Older revision		Revision as of 10:54, 15 February 2024
Line 118:		Line 118:
	*More conveniently, the .bit file found in the implementation runs folder in the Vivado project can be loaded onto an SD card to automatically program the Nexys Video without Vivado when powered on.		*More conveniently, the .bit file found in the implementation runs folder in the Vivado project can be loaded onto an SD card to automatically program the Nexys Video without Vivado when powered on.
	**JP4 must be in the USB/SD card position and JP3 must be in the SD card position.		**JP4 must be in the USB/SD card position and JP3 must be in the SD card position.
			* All the bit files can be found on: /unix/www/html/pbt/wikiData/fpga

	==Installing libFTDI==		==Installing libFTDI==

SaadShaikh: /* Uploading Data to HEP Server */

2022-11-09T14:12:41Z

Uploading Data to HEP Server

@@ Line 172: / Line 172: @@
 *Once compiled, useful combination of scripts can be conveniently run simultaneously using a bash script, see the file <code>prog.sh</code> for more details.
 *To exit the programs prematurely and cleanly, quit any ROOT plots before using CTRL-C to exit the FTDI script.
 =Legacy Information=

SaadShaikh: /* Compiling and Running FTDI Code */

2022-07-26T17:35:29Z

Compiling and Running FTDI Code

← Older revision		Revision as of 17:35, 26 July 2022
Line 162:		Line 162:
	==Compiling and Running FTDI Code==		==Compiling and Running FTDI Code==
	*The files required for DAQ are <code>tools.h</code> and <code>FTDI.cpp</code>.		*The files required for DAQ are <code>tools.h</code> and <code>FTDI.cpp</code>.
	*On MacOS, the code is compiled with g++ using: <code>g++ -L/opt/local/lib -I/opt/local/include/libftdi1 -lftdi1 -std=c++17 FTDI.cpp -o FTDI</code>		*On MacOS, the code is compiled with g++ using: <code>g++ -L/opt/local/lib -I/opt/local/include/libftdi1 -lftdi1 -std=c++17 -O3 FTDI.cpp -o FTDI</code>
	*On PiOS, the code is compiled with g++ using: <code>g++ -L/usr/lib -I/usr/include/libftdi1 -lftdi1 -pthread -std=c++17 -Wno-psabi FTDI.cpp -o FTDI</code>		*On PiOS, the code is compiled with g++ using: <code>g++ -L/usr/lib -I/usr/include/libftdi1 -lftdi1 -pthread -std=c++17 -O3 -Wno-psabi FTDI.cpp -o FTDI</code>
	**Note: adjust library and include paths according to your installation of libFTDI		**Note: adjust library and include paths according to your installation of libFTDI
	*To run the code execute: <code>./FTDI 4 350 170 100000 50 (test)</code>		*To run the code execute: <code>./FTDI 4 350 170 100000 50 (test)</code>

SaadShaikh: /* Raspbian */

2021-10-15T09:27:02Z

Raspbian

← Older revision		Revision as of 09:27, 15 October 2021
Line 140:		Line 140:

	*Install dependencies:		*Install dependencies:
	<code> sudo apt-get install libusb-1.0~~-dev~~ libconfuse-dev swig python-dev libboost-all-dev</code>		<code> sudo apt-get install libusb-1.0 libconfuse-dev swig python-dev libboost-all-dev</code>

	*Clone the git repository:		*Clone the git repository:

SaadShaikh: /* Raspbian */

2021-10-15T09:25:52Z

Raspbian

← Older revision		Revision as of 09:25, 15 October 2021
Line 137:		Line 137:
	===Raspbian===		===Raspbian===
	*Install the build tools:		*Install the build tools:
	<code>sudo apt-get install build-essential		<code>sudo apt-get install build-essential git-core cmake doxygen </code>

	~~sudo apt-get install~~ git-core

	~~sudo apt-get install~~ cmake

	~~sudo apt-get install~~ doxygen ~~(for building documentations)~~ </code>

	*Install dependencies:		*Install dependencies:
	<code> sudo apt-get install libusb-1.0-dev ~~</code>~~		<code> sudo apt-get install libusb-1.0-dev libconfuse-dev swig python-dev libboost-all-dev</code>

	~~<code> sudo apt-get install~~ libconfuse-dev ~~(for ftdi-eeprom)~~

	~~sudo apt-get install~~ swig python-dev ~~(for python bindings)~~

	~~sudo apt-get install~~ libboost-all-dev ~~(for C++ binding and unit test)~~ </code>

	*Clone the git repository:		*Clone the git repository:
Line 160:		Line 148:

	git clone git://developer.intra2net.com/libftdi </code>		git clone git://developer.intra2net.com/libftdi </code>

	~~If you are building the release tar ball, just extract the source tar ball.~~

	*Rename git source folder		*Rename git source folder

SaadShaikh: /* Raspbian */

2021-10-15T09:24:26Z

Raspbian

← Older revision		Revision as of 09:24, 15 October 2021
Line 137:		Line 137:
	===Raspbian===		===Raspbian===
	*Install the build tools:		*Install the build tools:
	<code>sudo apt-get install build-essential ~~(yum install make automake gcc gcc-c++ kernel-devel)~~		<code>sudo apt-get install build-essential

	sudo apt-get install git-core ~~(yum install git)~~		sudo apt-get install git-core

	sudo apt-get install cmake ~~(yum install cmake)~~		sudo apt-get install cmake

	sudo apt-get install doxygen (for building documentations~~) (yum install doxygen~~) </code>		sudo apt-get install doxygen (for building documentations) </code>

	*Install dependencies:		*Install dependencies:
	<code> sudo apt-get install libusb-1.0-~~devel (yum install libusb-devel)~~ </code> ~~(if the system comes with older version like 1.0.8 or earlier, it is recommended you build libusbx-1.0.14 or later).~~		<code> sudo apt-get install libusb-1.0-dev </code>

	<code> sudo apt-get install libconfuse-dev (for ftdi-eeprom~~) (yum install libconfuse-devel~~)		<code> sudo apt-get install libconfuse-dev (for ftdi-eeprom)

	sudo apt-get install swig python-dev (for python bindings~~) (yum install swig python-devel~~)		sudo apt-get install swig python-dev (for python bindings)

	sudo apt-get install libboost-all-dev (for C++ binding and unit test~~) (yum install boost-devel~~) </code>		sudo apt-get install libboost-all-dev (for C++ binding and unit test) </code>

	*Clone the git repository:		*Clone the git repository:
Line 163:		Line 163:
	If you are building the release tar ball, just extract the source tar ball.		If you are building the release tar ball, just extract the source tar ball.

	*~~Build the~~ git source ~~and install~~		*Rename git source folder
	<code> cd libftdi		<code> mv libftdi src

	mkdir build		mkdir build
Line 170:		Line 170:
	cd build		cd build

	cmake -DCMAKE_INSTALL_PREFIX="/usr" ../		cmake -DCMAKE_INSTALL_PREFIX="/usr" ../src

	~~make~~		sudo make install -j4</code>

	sudo make install </code>

	==Compiling and Running FTDI Code==		==Compiling and Running FTDI Code==

SaadShaikh: /* Compiling and Running FTDI Code */

2021-10-15T09:21:24Z

Compiling and Running FTDI Code

← Older revision		Revision as of 09:21, 15 October 2021
Line 179:		Line 179:
	*The files required for DAQ are <code>tools.h</code> and <code>FTDI.cpp</code>.		*The files required for DAQ are <code>tools.h</code> and <code>FTDI.cpp</code>.
	*On MacOS, the code is compiled with g++ using: <code>g++ -L/opt/local/lib -I/opt/local/include/libftdi1 -lftdi1 -std=c++17 FTDI.cpp -o FTDI</code>		*On MacOS, the code is compiled with g++ using: <code>g++ -L/opt/local/lib -I/opt/local/include/libftdi1 -lftdi1 -std=c++17 FTDI.cpp -o FTDI</code>
	*On PiOS, the code is compiled with g++ using: <code>g++ -L/~~opt/local~~/lib -I/~~opt/local~~/include/libftdi1 -lftdi1 -pthread -std=c++17 -Wno-psabi FTDI.cpp -o FTDI</code>		*On PiOS, the code is compiled with g++ using: <code>g++ -L/usr/lib -I/usr/include/libftdi1 -lftdi1 -pthread -std=c++17 -Wno-psabi FTDI.cpp -o FTDI</code>
	**Note: adjust library and include paths according to your installation of libFTDI		**Note: adjust library and include paths according to your installation of libFTDI
	*To run the code execute: <code>./FTDI 4 350 170 100000 50 (test)</code>		*To run the code execute: <code>./FTDI 4 350 170 100000 50 (test)</code>

SaadShaikh: /* Raspbian */

2021-07-12T16:09:26Z

Raspbian

← Older revision		Revision as of 16:09, 12 July 2021
Line 174:		Line 174:
	make		make

	sudo make install <code>		sudo make install </code>

	==Compiling and Running FTDI Code==		==Compiling and Running FTDI Code==