Xilinx Tools - Revision history

Dfe002: removed old files

2010-09-16T11:03:19Z

removed old files

@@ Line 33: / Line 33: @@
 [http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/psa3.pdf Internship Report] |
 ====Firmware packages====
-=====RCU 260710=====
+to come
-=====LSR_TRG 301109=====
+[[User:Dfe002|Dominik]] 11:03, 16 September 2010 (UTC)

Dfe002: updated file links

2010-09-16T10:51:48Z

updated file links

← Older revision		Revision as of 10:51, 16 September 2010
Line 28:		Line 28:
	===Download Section===		===Download Section===
	====Program, libraries and instructions====		====Program, libraries and instructions====
	[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/~~BitGui.zip BitGui.zip] \|~~		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/BitGui_Linux.tar.gz BitGui_Linux.tar.gz] \|
	~~[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/generateConfigFiles_Linux~~.tar.gz ~~generateConfigFiles_Linux~~.tar.gz~~] \|~~
	~~[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/generateConfigFiles_Windows.rar generateConfigFiles_Windows.rar~~] \|
	[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/libQtCore.tar.gz libQtCore.tar.gz] \|		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/libQtCore.tar.gz libQtCore.tar.gz] \|
	[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/libQtGUI.tar.gz libQtGUI.tar.gz] \|		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/libQtGUI.tar.gz libQtGUI.tar.gz] \|

Dfe002: removed wrong files

2010-08-24T07:45:51Z

removed wrong files

← Older revision		Revision as of 07:45, 24 August 2010
Line 43:		Line 43:
	=====LSR_TRG 301109=====		=====LSR_TRG 301109=====
	[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/lsr_trg/lsr_trg301109initconf.hex lsr_trg301109initconf.hex]<br>		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/lsr_trg/lsr_trg301109initconf.hex lsr_trg301109initconf.hex]<br>
	~~[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/lsr_trg/lsr_trg301109scrub.hex lsr_trg301109scrub.hex]<br>~~
	[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/lsr_trg/lsr_trg301109readback.hex lsr_trg301109readback.hex]<br>		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/lsr_trg/lsr_trg301109readback.hex lsr_trg301109readback.hex]<br>
	[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/lsr_trg/lsr_trg301109framefiles.tar.gz lsr_trg301109framefiles.tar.gz]<br>		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/lsr_trg/lsr_trg301109framefiles.tar.gz lsr_trg301109framefiles.tar.gz]<br>
Line 49:		Line 48:
	=====GPulser 301109=====		=====GPulser 301109=====
	[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserinitconf.hex 240310gpulserinitconf.hex]<br>		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserinitconf.hex 240310gpulserinitconf.hex]<br>
	~~[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserscrub.hex 240310gpulserscrub.hex]<br>~~
	[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserreadback.hex 240310gpulserreadback.hex]<br>		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserreadback.hex 240310gpulserreadback.hex]<br>
	[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserframefiles.tar.gz 240310gpulserframefiles.tar.gz]<br>		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserframefiles.tar.gz 240310gpulserframefiles.tar.gz]<br>
	[[User:Dfe002\|Dominik]] 11:42, 23 August 2010 (UTC)		[[User:Dfe002\|Dominik]] 11:42, 23 August 2010 (UTC)

Dfe002 at 11:42, 23 August 2010

2010-08-23T11:42:09Z

← Older revision		Revision as of 11:42, 23 August 2010
Line 47:		Line 47:
	[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/lsr_trg/lsr_trg301109framefiles.tar.gz lsr_trg301109framefiles.tar.gz]<br>		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/lsr_trg/lsr_trg301109framefiles.tar.gz lsr_trg301109framefiles.tar.gz]<br>

			=====GPulser 301109=====
	[[User:Dfe002\|Dominik]] 11:34, 23 August 2010 (UTC)		[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserinitconf.hex 240310gpulserinitconf.hex]<br>
			[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserscrub.hex 240310gpulserscrub.hex]<br>
			[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserreadback.hex 240310gpulserreadback.hex]<br>
			[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/fw/gpulser/240310gpulserframefiles.tar.gz 240310gpulserframefiles.tar.gz]<br>
			[[User:Dfe002\|Dominik]] 11:42, 23 August 2010 (UTC)

Dfe002 at 11:34, 23 August 2010

2010-08-23T11:34:59Z

@@ Line 27: / Line 27: @@
 ===Download Section===
 [http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/BitGui.zip BitGui.zip] |
 [http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/generateConfigFiles_Linux.tar.gz generateConfigFiles_Linux.tar.gz] |
@@ Line 33: / Line 34: @@
 [http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/libQtGUI.tar.gz libQtGUI.tar.gz] |
 [http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/psa3.pdf Internship Report] |
-[[User:Dfe002|Dominik]] 11:16, 23 August 2010 (UTC)
+=====LSR_TRG 301109=====

Dfe002 at 11:16, 23 August 2010

2010-08-23T11:16:12Z

← Older revision		Revision as of 11:16, 23 August 2010
Line 25:		Line 25:
	The remote directory must exist and local directories that contain subdirectories can not be loaded up<br>		The remote directory must exist and local directories that contain subdirectories can not be loaded up<br>
	E.g. you want to load the files to “/tmp/test” the “test” directory has to be created before uploading.		E.g. you want to load the files to “/tmp/test” the “test” directory has to be created before uploading.

			===Download Section===
			[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/BitGui.zip BitGui.zip] \|
			[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/generateConfigFiles_Linux.tar.gz generateConfigFiles_Linux.tar.gz] \|
			[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/generateConfigFiles_Windows.rar generateConfigFiles_Windows.rar] \|
			[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/libQtCore.tar.gz libQtCore.tar.gz] \|
			[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/libQtGUI.tar.gz libQtGUI.tar.gz] \|
			[http://web.ift.uib.no/~dominik/files/detectorlabwiki/bitgui/psa3.pdf Internship Report] \|

			[[User:Dfe002\|Dominik]] 11:16, 23 August 2010 (UTC)

Dfe002 at 10:57, 23 August 2010

2010-08-23T10:57:46Z

← Older revision		Revision as of 10:57, 23 August 2010
Line 2:		Line 2:
	===General===		===General===
	This tool can be used to generate frames for any Xilinx Virtex-II Pro FPGA. Therefore an XML based configuration file exists. To generate frame files the type of FPGA has to be added to the XML file.		This tool can be used to generate frames for any Xilinx Virtex-II Pro FPGA. Therefore an XML based configuration file exists. To generate frame files the type of FPGA has to be added to the XML file.
	This is done in the following way:
	<Device DeviceName="XC2VP7" DeviceID="0124A093" numFrames="1320" frameLength="106" IOBColumns="2" IOBFrames="4" IOIColumns="2" IOIFrames="22" CLBColumns="34" CLBFrames="22" BRAMColumns="6" BRAMFrames="64" BRAMICColumns="6" BRAMICFrames="22" GCLKColumns="1" GCLKFrames="4"~~><br~~><br>		This is done in the following way:<br>
			<Device DeviceName="XC2VP7" DeviceID="0124A093" numFrames="1320" frameLength="106" IOBColumns="2" IOBFrames="4" IOIColumns="2" IOIFrames="22" CLBColumns="34" CLBFrames="22" BRAMColumns="6" BRAMFrames="64" BRAMICColumns="6" BRAMICFrames="22" GCLKColumns="1" GCLKFrames="4"><br>
	The device name can be found directly on the chip. The other values are provided in the Xilinx User Guide in the chapter “Configuration – Configuration Details”. There you will find two tables in which all frame and column sizes are listed. The device IDs you will also find in a table in this chapter.		The device name can be found directly on the chip. The other values are provided in the Xilinx User Guide in the chapter “Configuration – Configuration Details”. There you will find two tables in which all frame and column sizes are listed. The device IDs you will also find in a table in this chapter.
	For different types of Virtex FPGAs the names of the frame types can vary. The names shown above are an example for Virtex-II Pro frames.		For different types of Virtex FPGAs the names of the frame types can vary. The names shown above are an example for Virtex-II Pro frames.
Line 9:		Line 10:
	===Creating frames===		===Creating frames===
	Generating the frames is done in these steps:		Generating the frames is done in these steps:
	1. Load the bit-file for the FPGA		# Load the bit-file for the FPGA
	2. Type the name of the device as you can see above in “DeviceName”		# Type the name of the device as you can see above in “DeviceName”
	3. Load the XML configuration file		# Load the XML configuration file
	4. Type the directory where the frames are saved to		# Type the directory where the frames are saved to
	5. Press the “Split” button		# Press the “Split” button
	If the frames were generated successfully or an error occurred you will see a message.		If the frames were generated successfully or an error occurred you will see a message.

Dfe002 at 10:56, 23 August 2010

2010-08-23T10:56:39Z

← Older revision		Revision as of 10:56, 23 August 2010
Line 1:		Line 1:
	~~'''~~Frame Generation Tool~~'''<br><br>~~		==Frame Generation Tool==
	~~'''''~~General~~'''''<br>~~		===General===
	This tool can be used to generate frames for any Xilinx Virtex-II Pro FPGA. Therefore an XML based configuration file exists. To generate frame files the type of FPGA has to be added to the XML file.		This tool can be used to generate frames for any Xilinx Virtex-II Pro FPGA. Therefore an XML based configuration file exists. To generate frame files the type of FPGA has to be added to the XML file.
	This is done in the following way:~~<br><br>~~		This is done in the following way:
	<Device DeviceName="XC2VP7" DeviceID="0124A093" numFrames="1320" frameLength="106" IOBColumns="2" IOBFrames="4" IOIColumns="2" IOIFrames="22" CLBColumns="34" CLBFrames="22" BRAMColumns="6" BRAMFrames="64" BRAMICColumns="6" BRAMICFrames="22" GCLKColumns="1" GCLKFrames="4"><br><br>		<Device DeviceName="XC2VP7" DeviceID="0124A093" numFrames="1320" frameLength="106" IOBColumns="2" IOBFrames="4" IOIColumns="2" IOIFrames="22" CLBColumns="34" CLBFrames="22" BRAMColumns="6" BRAMFrames="64" BRAMICColumns="6" BRAMICFrames="22" GCLKColumns="1" GCLKFrames="4"><br><br>
	The device name can be found directly on the chip. The other values are provided in the Xilinx User Guide in the chapter “Configuration – Configuration Details”. There you will find two tables in which all frame and column sizes are listed. The device IDs you will also find in a table in this chapter.		The device name can be found directly on the chip. The other values are provided in the Xilinx User Guide in the chapter “Configuration – Configuration Details”. There you will find two tables in which all frame and column sizes are listed. The device IDs you will also find in a table in this chapter.
	For different types of Virtex FPGAs the names of the frame types can vary. The names shown above are an example for Virtex-II Pro frames.~~<br>~~		For different types of Virtex FPGAs the names of the frame types can vary. The names shown above are an example for Virtex-II Pro frames.
	<br>		<br>
	~~'''''~~Creating frames~~'''''<br>~~		===Creating frames===
	Generating the frames is done in these steps:~~<br>~~		Generating the frames is done in these steps:
	1. Load the bit-file for the FPGA~~<br>~~		1. Load the bit-file for the FPGA
	2. Type the name of the device as you can see above in “DeviceName”~~<br>~~		2. Type the name of the device as you can see above in “DeviceName”
	3. Load the XML configuration file~~<br>~~		3. Load the XML configuration file
	4. Type the directory where the frames are saved to~~<br>~~		4. Type the directory where the frames are saved to
	5. Press the “Split” button~~<br>~~		5. Press the “Split” button
	If the frames were generated successfully or an error occurred you will see a message.~~<br>~~		If the frames were generated successfully or an error occurred you will see a message.
	~~<br>~~
	~~'''''~~Creating binary command blocks~~'''''<br>~~		===Creating binary command blocks===
	This part can be found on the second tab on the right side. To create these command blocks just follow the steps 1-3 above. After you have done this enter the name (and path) of the command file and press the “Generate ...” button right beside. If the block was generated successfully or an error occurred you will see a message.<br>		This part can be found on the second tab on the right side. To create these command blocks just follow the steps 1-3 above. After you have done this enter the name (and path) of the command file and press the “Generate ...” button right beside. If the block was generated successfully or an error occurred you will see a message.<br>
	<br>		<br>
	~~'''''~~Uploading to a dedicated location~~'''''<br>~~		===Uploading to a dedicated location===
	To load the files that were generated to the place they are needed an uploading feature was introduced. Here you enter the hostname to where you want to load the files up. Authenticating at the host is done by entering username and password. After that you are able to specify a local file/folder that has to be loaded up and a remote directory where the files/folder is saved to.<br><br>		To load the files that were generated to the place they are needed an uploading feature was introduced. Here you enter the hostname to where you want to load the files up. Authenticating at the host is done by entering username and password. After that you are able to specify a local file/folder that has to be loaded up and a remote directory where the files/folder is saved to.<br><br>
	~~'''~~NOTE~~''': the~~ remote directory must exist and local directories that contain subdirectories can not be loaded up<br>		===NOTE===
			The remote directory must exist and local directories that contain subdirectories can not be loaded up<br>
	E.g. you want to load the files to “/tmp/test” the “test” directory has to be created before uploading.		E.g. you want to load the files to “/tmp/test” the “test” directory has to be created before uploading.

Nfyku: New page: '''Frame Generation Tool'''

'''''General'''''
This tool can be used to generate frames for any Xilinx Virtex-II Pro FPGA. Therefore an XML based configuration file exists. To g...

2009-02-18T10:07:08Z

New page: '''Frame Generation Tool''' '''''General''''' This tool can be used to generate frames for any Xilinx Virtex-II Pro FPGA. Therefore an XML based configuration file exists. To g...

New page

'''Frame Generation Tool''' 
'''''General''''' 
This tool can be used to generate frames for any Xilinx Virtex-II Pro FPGA. Therefore an XML based configuration file exists. To generate frame files the type of FPGA has to be added to the XML file.
This is done in the following way: 
<Device DeviceName="XC2VP7" DeviceID="0124A093" numFrames="1320" frameLength="106" IOBColumns="2" IOBFrames="4" IOIColumns="2" IOIFrames="22" CLBColumns="34" CLBFrames="22" BRAMColumns="6" BRAMFrames="64" BRAMICColumns="6" BRAMICFrames="22" GCLKColumns="1" GCLKFrames="4"> 
The device name can be found directly on the chip. The other values are provided in the Xilinx User Guide in the chapter “Configuration – Configuration Details”. There you will find two tables in which all frame and column sizes are listed. The device IDs you will also find in a table in this chapter.
For different types of Virtex FPGAs the names of the frame types can vary. The names shown above are an example for Virtex-II Pro frames. 
 
'''''Creating frames''''' 
Generating the frames is done in these steps: 
1. Load the bit-file for the FPGA 
2. Type the name of the device as you can see above in “DeviceName” 
3. Load the XML configuration file 
4. Type the directory where the frames are saved to 
5. Press the “Split” button 
If the frames were generated successfully or an error occurred you will see a message. 
 
'''''Creating binary command blocks''''' 
This part can be found on the second tab on the right side. To create these command blocks just follow the steps 1-3 above. After you have done this enter the name (and path) of the command file and press the “Generate ...” button right beside. If the block was generated successfully or an error occurred you will see a message. 
 
'''''Uploading to a dedicated location''''' 
To load the files that were generated to the place they are needed an uploading feature was introduced. Here you enter the hostname to where you want to load the files up. Authenticating at the host is done by entering username and password. After that you are able to specify a local file/folder that has to be loaded up and a remote directory where the files/folder is saved to. 
'''NOTE''': the remote directory must exist and local directories that contain subdirectories can not be loaded up 
E.g. you want to load the files to “/tmp/test” the “test” directory has to be created before uploading.