Electronics for the Time Projection Chamber (TPC) - Revision history

Stud4729 at 11:56, 21 May 2013

2013-05-21T11:56:36Z

← Older revision		Revision as of 11:56, 21 May 2013
Line 582:		Line 582:
	<br>		<br>
	[http://web.ift.uib.no/firmware/alme/dcs_interface_v0.3.rar Firmware v 0.3 - VHDL files, including testbench]<br><br>		[http://web.ift.uib.no/firmware/alme/dcs_interface_v0.3.rar Firmware v 0.3 - VHDL files, including testbench]<br><br>



	== PHOS FEC Board Controller ==		== PHOS FEC Board Controller ==

Line 689:		Line 692:
	<li>Changed start condition of the readout command detect state machine to make it behave better in ppr simulations</li>		<li>Changed start condition of the readout command detect state machine to make it behave better in ppr simulations</li>
	<li>Removed debug counters and metastabilityfilter on ALTRO if (but kept information concverning lasted acked and last not acked transaction)</li>		<li>Removed debug counters and metastabilityfilter on ALTRO if (but kept information concverning lasted acked and last not acked transaction)</li>
			</ul>
			<br><br>
			'''v3.6 (21.05.2013)'''<br>
			<ul>
			<li>Redesign of the Slow Control interface. SCLK frequency should be 2.5 MHz (RCU reg 0x800C = 0x1). </li>
			<li>Bugfix of Sparse Readout. Added Debug functionality for low level test of Sparse readout.</li>
	</ul>		</ul>



	=== Download Section ===		=== Download Section ===
Line 723:		Line 734:
	[http://web.ift.uib.no/firmware/alme/phos_bc_v3.5_Quartus_project.rar Quartus Project - Firmware v 3.5]<br>		[http://web.ift.uib.no/firmware/alme/phos_bc_v3.5_Quartus_project.rar Quartus Project - Firmware v 3.5]<br>
	[http://web.ift.uib.no/firmware/alme/phos_bc_v3.5_programming_files.rar Programming files - Firmware v 3.5]<br>		[http://web.ift.uib.no/firmware/alme/phos_bc_v3.5_programming_files.rar Programming files - Firmware v 3.5]<br>
			<br><br>
			[http://web.ift.uib.no/~alme/wiki/phos_bc_v3.6_specification.pdf Specification/design documentation for Firmware version 3.6] <br>
			[http://web.ift.uib.no/~alme/wiki/phos_bc_v3.6_source.zip Firmware v 3.6 - VHDL files, including testbench]<br>
			[http://web.ift.uib.no/~alme/wiki/phos_bc_v3.6_Quartus_project.zip Quartus Project - Firmware v 3.6]<br>
			[http://web.ift.uib.no/~alme/wiki/phos_bc_v3.6_programming_files.zip Programming files - Firmware v 3.6]<br>
	<br>		<br>
			[http://web.ift.uib.no/~alme/wiki/phos_bc_v3.6_programming_user_guide.pdf Programming User Guise for Firmware version 3.6] <br>
			[http://web.ift.uib.no/~alme/wiki/12.0_178_programmer_windows.exe Altera Programmer v12.0] <br>
			[http://web.ift.uib.no/~alme/wiki/ug_usb_blstr.pdf Altera USB Blaster User Guide]<br>



	Source files: [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/alice-fw/trunk/phos_bc/ SVN database]		Source files: [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/alice-fw/trunk/phos_bc/ SVN database]

Dfe002: /* Download Section */ added link to rcS file

2012-01-31T12:21:26Z

Download Section: added link to rcS file

← Older revision		Revision as of 12:21, 31 January 2012
Line 307:		Line 307:
	<li>'''Version 2.9: '''<br>		<li>'''Version 2.9: '''<br>
	[http://web.ift.uib.no/~dominik/files/dcs_fw/dcsflash_boardrev164_firmware2.9uib_dcs0031.hex hex file for dcs0031] \|		[http://web.ift.uib.no/~dominik/files/dcs_fw/dcsflash_boardrev164_firmware2.9uib_dcs0031.hex hex file for dcs0031] \|
	[[Firmware files for boards 30 - 1400]]		[[Firmware files for boards 30 - 1400]] \|
			[http://web.ift.uib.no/~dominik/files/dcs_fw/rcS rcS file for new udhcpc, boot script order]
	</li>		</li>
	<br>		<br>

Dfe002: /* Download Section */

2012-01-30T11:02:25Z

Download Section

← Older revision		Revision as of 11:02, 30 January 2012
Line 304:		Line 304:
	[http://web.ift.uib.no/firmware/alme/epxa1db_v2.84.rar epxa1db_v2.84.sbi] \|		[http://web.ift.uib.no/firmware/alme/epxa1db_v2.84.rar epxa1db_v2.84.sbi] \|
	[http://web.ift.uib.no/firmware/alme/dcs1.52_busylogic_v2.84.qar Quartus Project (Archive)]		[http://web.ift.uib.no/firmware/alme/dcs1.52_busylogic_v2.84.qar Quartus Project (Archive)]
			</li>
			<li>'''Version 2.9: '''<br>
			[http://web.ift.uib.no/~dominik/files/dcs_fw/dcsflash_boardrev164_firmware2.9uib_dcs0031.hex hex file for dcs0031] \|
			[[Firmware files for boards 30 - 1400]]
	</li>		</li>
	<br>		<br>
Line 338:		Line 342:
	The Quartus project needs to be opened with a version of Quartus prior to 4.2, or else the Excalibur device is not supported.		The Quartus project needs to be opened with a version of Quartus prior to 4.2, or else the Excalibur device is not supported.
	<br><br>		<br><br>

	== DCS board Lattice CPLD-firmware for TPC and PHOS ==		== DCS board Lattice CPLD-firmware for TPC and PHOS ==

Dfe002: Added version 2.9 changes

2012-01-30T10:56:31Z

Added version 2.9 changes

@@ Line 187: / Line 187: @@
 <li> Added a register on ttcrx_rdy to reduce the load on the net, hence removing the problem with channel A/channel B errors. (otherwise equal to 2.83)</li>
 </ul>
 <br>

Stud4729 at 08:45, 20 January 2012

2012-01-20T08:45:53Z

@@ Line 453: / Line 453: @@
 <li>Minor change to sequence validator only. CIT bit is no longer verified against arrival of pre-pulse. (Specified in mail correspondance with Terry Awes 23.03.2010). </li>
 </ul>
 '''v 1.5 (17.08.2010)'''<br>
 <ul>
@@ Line 463: / Line 464: @@
 </li>
 </ul>
 <br><br>
@@ Line 509: / Line 520: @@
 <br>
 [http://web.ift.uib.no/firmware/alme/trigger_receiver_v1.5_source_files.rar Firmware v 1.5 - VHDL files, including testbench]<br>
 All source files and more can be downloaded from the [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/alice-fw/trunk/trigger_receiver/ SVN database].

Dfe002: /* Updating the Actel Firmware */

2010-11-12T12:32:58Z

Updating the Actel Firmware

← Older revision		Revision as of 12:32, 12 November 2010
Line 701:		Line 701:
	=== Updating the Actel Firmware ===		=== Updating the Actel Firmware ===
	[[Image:FlashProLite.jpg\|thumb\|left\|200px\|Actel FlashPro Lite]]		[[Image:FlashProLite.jpg\|thumb\|left\|200px\|Actel FlashPro Lite]]
	The only possible option to update the Actel Firmware is by using the JTAG connector on the board and the FlashPro Lite programmer, together with the [http://www.actel.com/custsup/updates/flashpro/index.html flashpro software tool].<br>		The only possible option to update the Actel Firmware is by using the JTAG connector on the board and the FlashPro Lite programmer, together with the [http://www.actel.com/custsup/updates/flashpro/index.html flashpro software tool]. Note that version 9.0 gives errors when trying to program the FPGA. [ftp://ftp.actel.com/downloads/flashpro/FlashPro86.zip Version 8.6] is the last version that works for the Actel on the RCU.<br>
	Download the correct version of stp file found on the download section, and start a new project in the flashpro software. Select the stp-file and choose action "program". Wait for a couple of minutes and the Actel should be updated. This can be verified by reading the version-number register.		Download the correct version of stp file found on the download section, and start a new project in the flashpro software. Select the stp-file and choose action "program". Wait for a couple of minutes and the Actel should be updated. This can be verified by reading the version-number register.
	<br><br><br><br><br>		<br><br><br><br><br>

Stud4729 at 06:36, 17 August 2010

2010-08-17T06:36:50Z

← Older revision		Revision as of 06:36, 17 August 2010
Line 452:		Line 452:
	<ul>		<ul>
	<li>Minor change to sequence validator only. CIT bit is no longer verified against arrival of pre-pulse. (Specified in mail correspondance with Terry Awes 23.03.2010). </li>		<li>Minor change to sequence validator only. CIT bit is no longer verified against arrival of pre-pulse. (Specified in mail correspondance with Terry Awes 23.03.2010). </li>
			</ul>
			'''v 1.5 (17.08.2010)'''<br>
			<ul>
			<li>Fix done by Attiq Ur Rehman:<br>
			There is minor change in the "fifo wrapper":<br>
			Line #73 new signal cnt_dn<br>
			Line #91 comparison with "read_counter"<br>
			Line #170,172,174 check of possible logical conditions<br>
			This file was used for the RCU firmware (from 10th July and on wards) to fix the Erroneous behavior causing busy condition.
			</li>
	</ul>		</ul>
	<br><br>		<br><br>
Line 495:		Line 505:
	[http://web.ift.uib.no/firmware/alme/trigger_receiver_v1.3_source_files.rar Firmware v 1.3 - VHDL files, including testbench]<br>		[http://web.ift.uib.no/firmware/alme/trigger_receiver_v1.3_source_files.rar Firmware v 1.3 - VHDL files, including testbench]<br>
	<br>		<br>
	[http://web.ift.uib.no/firmware/alme/sequence_validator2010-03-24.rar Firmware v 1.4 - sequence_validator.vhd and trigger_receiver_pkg.vhd]. <i>Download version 1.3 and replace the two files.</i><br>		[http://web.ift.uib.no/firmware/alme/sequence_validator2010-03-24.rar Firmware v 1.4 - sequence_validator.vhd and trigger_receiver_pkg.vhd]. <i>Download version 1.3 and replace the two files.</i>
			<br>
			<br>
			[http://web.ift.uib.no/firmware/alme/trigger_receiver_v1.5_source_files.rar Firmware v 1.5 - VHDL files, including testbench]<br>

	All source files and more can be downloaded from the [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/alice-fw/trunk/trigger_receiver/ SVN database].		All source files and more can be downloaded from the [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/alice-fw/trunk/trigger_receiver/ SVN database].

Nfyku: Changed from CVS to SVN

2010-04-07T09:26:09Z

Changed from CVS to SVN

← Older revision		Revision as of 09:26, 7 April 2010
Line 198:		Line 198:

	Source files:		Source files:
	[http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/~~vhdlcvs~~/messagebuffer/ ~~CVS~~ database]		[http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/alice-fw/trunk/messagebuffer/ SVN database]
	<br><br>		<br><br>
	<ul>		<ul>
Line 497:		Line 497:
	[http://web.ift.uib.no/firmware/alme/sequence_validator2010-03-24.rar Firmware v 1.4 - sequence_validator.vhd and trigger_receiver_pkg.vhd]. <i>Download version 1.3 and replace the two files.</i><br>		[http://web.ift.uib.no/firmware/alme/sequence_validator2010-03-24.rar Firmware v 1.4 - sequence_validator.vhd and trigger_receiver_pkg.vhd]. <i>Download version 1.3 and replace the two files.</i><br>

	All source files and more can be downloaded from the [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/~~vhdlcvs~~/trigger_receiver/ ~~CVS~~ database].		All source files and more can be downloaded from the [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/alice-fw/trunk/trigger_receiver/ SVN database].
	<br><br>		<br><br>
	== RCU DCS Interface Module ==		== RCU DCS Interface Module ==
Line 674:		Line 674:
	<br>		<br>

	Source files: [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/~~vhdlcvs~~/phos_bc/ ~~CVS~~ database]		Source files: [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/alice-fw/trunk/phos_bc/ SVN database]
	<br>		<br>
	<br>		<br>
Line 859:		Line 859:
	[http://web.ift.uib.no/firmware/alme/actel_v1-4.stp Firmware v 1.4 programming file]		[http://web.ift.uib.no/firmware/alme/actel_v1-4.stp Firmware v 1.4 programming file]
	<br><br>		<br><br>
	Source files: [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/~~vhdlcvs~~/rcu_cpld/ CVS database]		Source files: [http://web.ift.uib.no/kjekscgi-bin/viewvc.cgi/alice-fw/trunk/rcu_cpld/ CVS database]
	<br><br>		<br><br>
	For assosiated information concerning software and software tool download section, go to: [[The Actel software device in the FeeServer CE]]		For assosiated information concerning software and software tool download section, go to: [[The Actel software device in the FeeServer CE]]

Nfyku at 08:55, 24 March 2010

2010-03-24T08:55:10Z

← Older revision		Revision as of 08:55, 24 March 2010
Line 20:		Line 20:
	====Updating the DCS boards:====		====Updating the DCS boards:====
	# Using the exc_flash_programmer tool from Altera together with the Byteblaster programmer. <br>		# Using the exc_flash_programmer tool from Altera together with the Byteblaster programmer. <br>
	Then you do as described in under Firmware download - exc_flash_programmer in the link given above. In addition it is of high importance that you use Quartus II versions older or equal to ~~<b>~~4.1~~</b>~~. At least this is the last version of Quartus II that support the device on the DCS board. Unfortunately Altera won't support us on this any longer since the device is outdated so it is hard to give a precise answer to what might be wrong in case it fails.</li>		#: Then you do as described in under Firmware download - exc_flash_programmer in the link given above. In addition it is of high importance that you use Quartus II versions older or equal to ''4.1''. At least this is the last version of Quartus II that support the device on the DCS board. Unfortunately Altera won't support us on this any longer since the device is outdated so it is hard to give a precise answer to what might be wrong in case it fails.</li>
	# Using the tool remoteupdate4.sh<br>		# Using the tool remoteupdate4.sh<br>
	This is to be run on a remote linux system in the same network as the dcs system. "Srec cat" tool is mandatory. (Can be downloaded from the page of Tobias)		This is to be run on a remote linux system in the same network as the dcs system. "Srec cat" tool is mandatory. (Can be downloaded from the page of Tobias)

Nfyku at 08:51, 24 March 2010

2010-03-24T08:51:11Z

← Older revision		Revision as of 08:51, 24 March 2010
Line 1:		Line 1:
	== Overview ==		== Overview ==
	[[Image:RCU_DCS_sketch.png\|thumb\|500px\|center\|Sketch of the Readout Control Unit]]		[[Image:RCU_DCS_sketch.png\|thumb\|500px\|center\|Sketch of the Readout Control Unit]]
	~~<br><br>~~
	== DCS board firmware for TPC and PHOS ==		== DCS board firmware for TPC and PHOS ==
	=== Overview ===		=== Overview ===
	[[Image:DCS_FW.png\|thumb\|350px\|Schematic Overview of the DCS firmware for TPC/PHOS]]		[[Image:DCS_FW.png\|thumb\|350px\|Schematic Overview of the DCS firmware for TPC/PHOS]]
	The communication to the firmware in both the Xilinx FPGA and the Actel FPGA on the RCU board is done with the RCU Communication Module. This is done by using a memory mapped interface. The Linux driver writes blocks of data down to a memory in the RCU Communication Module where it is decoded and executed; hence data is being written to or read from the RCU Firmware.~~<br><br>~~		The communication to the firmware in both the Xilinx FPGA and the Actel FPGA on the RCU board is done with the RCU Communication Module. This is done by using a memory mapped interface. The Linux driver writes blocks of data down to a memory in the RCU Communication Module where it is decoded and executed; hence data is being written to or read from the RCU Firmware.

			Historically the RCU Communication Module only consisted of the Memory Mapped Communication Mode, but as the reconfiguration circuitry on the RCU board was designed, the need of using the bus lines in different ways arose. In addition to this normal communication path, two other ways to communicate is added, namely the RCU flash interface or the Selectmap interface of the RCU. There are several reasons for having these two interfaces on the DCS board

			* Speed. Using the default memory mapped mode to communicate with the flash memory is not very efficient. Simply moving the flash interface and the selectmap interface to the DCS board, using the Actel as a route-through firmware makes it much faster.
			* Space. The Actel APA075 has limited capacity. To be able to fit in all the needed functionality, all modules that is not needed in the Actel should be removed.
			* Robustness. Since the Actel is not possible to update after installation, doing potential bugfixes is impossible. Moving firmware modules to the DCS board ensures that communication paths to the Selectmap Interface and the Flash Device will always be available.

	<p>Historically the RCU Communication Module only consisted of the Memory Mapped Communication Mode, but as the reconfiguration circuitry on the RCU board was designed, the need of using the bus lines in different ways arose. In addition to this normal communication path, two other ways to communicate is added, namely the RCU flash interface or the Selectmap interface of the RCU. There are several reasons for having these two interfaces on the DCS board.<br><br>
	~~<ul>~~
	<li>Speed. Using the default memory mapped mode to communicate with the flash memory is not very efficient. Simply moving the flash interface and the selectmap interface to the DCS board, using the Actel as a route-through firmware makes it much faster.</li>
	~~<li>Space. The Actel APA075 has limited capacity. To be able to fit in all the needed functionality, all modules that is not needed in the Actel should be removed.</li>~~
	<li>Robustness. Since the Actel is not possible to update after installation, doing potential bugfixes is impossible. Moving firmware modules to the DCS board ensures that communication paths to the Selectmap Interface and the Flash Device will always be available. </li>
	~~</ul>~~
	~~<br>~~
	=== Update of the DCS Board Flash Device ===		=== Update of the DCS Board Flash Device ===
	There are two ways of updating the DCS board. The cards that are properly set up should read firmware version 2.6uib when logging in, if intended to use together with the RCU. For the Trigger OR and the BusyBox a special firmware has been made. This firmware is available here so in principle is possible to do the updates when needed, but if any questions, please don't hesitate to ask us. If you get cards directly from Heidelberg where they are produced, updates are needed if intended to use with TPC/PHOS.<br><br>		There are two ways of updating the DCS board. The cards that are properly set up should read firmware version 2.6uib when logging in, if intended to use together with the RCU. For the Trigger OR and the BusyBox a special firmware has been made. This firmware is available here so in principle is possible to do the updates when needed, but if any questions, please don't hesitate to ask us. If you get cards directly from Heidelberg where they are produced, updates are needed if intended to use with TPC/PHOS.<br><br>
Line 19:		Line 18:
	The ways of updating the boards are given at the DCS page of [http://frodo.nt.fh-koeln.de/~tkrawuts/firmware/index.html Tobias Krawutschke]. The important thing is that the .hex file is generated here in Bergen. It should be matching the board number written on the board with felt pen.<br><br>		The ways of updating the boards are given at the DCS page of [http://frodo.nt.fh-koeln.de/~tkrawuts/firmware/index.html Tobias Krawutschke]. The important thing is that the .hex file is generated here in Bergen. It should be matching the board number written on the board with felt pen.<br><br>

	~~<ol>~~Updating the DCS boards:		====Updating the DCS boards:====
	~~<li>~~ Using the exc_flash_programmer tool from Altera together with the Byteblaster programmer. <br>		# Using the exc_flash_programmer tool from Altera together with the Byteblaster programmer. <br>
	Then you do as described in under Firmware download - exc_flash_programmer in the link given above. In addition it is of high importance that you use Quartus II versions older or equal to <b>4.1</b>. At least this is the last version of Quartus II that support the device on the DCS board. Unfortunately Altera won't support us on this any longer since the device is outdated so it is hard to give a precise answer to what might be wrong in case it fails.</li>		Then you do as described in under Firmware download - exc_flash_programmer in the link given above. In addition it is of high importance that you use Quartus II versions older or equal to <b>4.1</b>. At least this is the last version of Quartus II that support the device on the DCS board. Unfortunately Altera won't support us on this any longer since the device is outdated so it is hard to give a precise answer to what might be wrong in case it fails.</li>
	~~<li>~~ Using the tool remoteupdate4.sh<br>		# Using the tool remoteupdate4.sh<br>
	This is to be run on a remote linux system in the same network as the dcs system. "Srec cat" tool is mandatory. (Can be downloaded from the page of Tobias)		This is to be run on a remote linux system in the same network as the dcs system. "Srec cat" tool is mandatory. (Can be downloaded from the page of Tobias)
	The important thing here is that the DCS board needs to be running "correctly" in the first place to be able to do this. Correctly means that you have the network working seamlessly.</li>		The important thing here is that the DCS board needs to be running "correctly" in the first place to be able to do this. Correctly means that you have the network working seamlessly.</li>
	~~</ol>~~

	Please note that these two ways update the complete Flash Memory, meaning the firmware, the boot section, the Kernel and the file system (the last way makes it possible to choose what part to update). This is sometimes mandatory depending on the firmware version - and it is a lot more "safe" since you then get the latest drivers and software etc...		Please note that these two ways update the complete Flash Memory, meaning the firmware, the boot section, the Kernel and the file system (the last way makes it possible to choose what part to update). This is sometimes mandatory depending on the firmware version - and it is a lot more "safe" since you then get the latest drivers and software etc...
	~~<br>~~

	=== Version history ===		=== Version history ===

	'''1.0 (~april 2004)''' <br>		'''1.0 (~april 2004)''' <br>
	<ul>		<ul>
Line 868:		Line 864:

	[[Category:Alice]]		[[Category:Alice]]
			[[Category:Mikroelektronikk]]