Testing Clock Cards - Revision history

Mandana: /* lvds rx/tx or command/reply lines */

2018-08-01T17:21:16Z

‎lvds rx/tx or command/reply lines

Mandana: /* lvds rx/tx or command/reply lines */

2018-08-01T17:19:19Z

‎lvds rx/tx or command/reply lines

Mandana: /* lvds rx/tx or command/reply lines */

2018-08-01T17:19:02Z

‎lvds rx/tx or command/reply lines

Dvw at 01:58, 1 September 2016

2016-09-01T01:58:29Z

Dvw at 00:59, 31 August 2016

2016-08-31T00:59:59Z

Dvw at 23:12, 30 August 2016

2016-08-30T23:12:32Z

Mandana at 20:55, 7 June 2013

2013-06-07T20:55:00Z

Mandana at 18:47, 7 June 2013

2013-06-07T18:47:19Z

Mandana at 17:21, 7 June 2013

2013-06-07T17:21:36Z

Mandana at 23:39, 6 June 2013

2013-06-06T23:39:23Z

← Older revision		Revision as of 17:21, 1 August 2018
Line 70:		Line 70:
	copy the results into the test logfile and record the card_id on [[MCE CARD Serial-Number Lookup]]		copy the results into the test logfile and record the card_id on [[MCE CARD Serial-Number Lookup]]

		+	== testing communication with backplane silicon_id chip==
		+	issue following commands to make sure clock card can read the silicon_id and temperature from the id chip on the backplane:
		+	mce_cmd -x rb cc box_id
		+	mce_cmd -x rb cc box_temp
		+
		+	record the results in logfile
	== lvds rx/tx or command/reply lines==		== lvds rx/tx or command/reply lines==

← Older revision		Revision as of 17:19, 1 August 2018
Line 69:		Line 69:

	copy the results into the test logfile and record the card_id on [[MCE CARD Serial-Number Lookup]]		copy the results into the test logfile and record the card_id on [[MCE CARD Serial-Number Lookup]]
−
−	~~== testing backplane communication ==~~
−	~~Use following commands to read back the temperature and silicon_id of the backplane:~~
−	~~mce_cmd -x rb cc box_id~~
−	~~mce_cmd -x rb cc box_temp~~

	== lvds rx/tx or command/reply lines==		== lvds rx/tx or command/reply lines==

← Older revision		Revision as of 17:19, 1 August 2018
Line 69:		Line 69:

	copy the results into the test logfile and record the card_id on [[MCE CARD Serial-Number Lookup]]		copy the results into the test logfile and record the card_id on [[MCE CARD Serial-Number Lookup]]
		+
		+	== testing backplane communication ==
		+	Use following commands to read back the temperature and silicon_id of the backplane:
		+	mce_cmd -x rb cc box_id
		+	mce_cmd -x rb cc box_temp

	== lvds rx/tx or command/reply lines==		== lvds rx/tx or command/reply lines==

@@ Line 121: / Line 121: @@
 log results
-[[Category:Firmware]]
+[[Category:Clock Card]]
 [[Category:MCE Script]]
 [[Category:Testing]]

← Older revision		Revision as of 00:59, 31 August 2016
Line 122:		Line 122:

	[[Category:Firmware]]		[[Category:Firmware]]
−	[[Category:~~Software~~]]	+	[[Category:MCE Script]]
		+	[[Category:Testing]]

← Older revision		Revision as of 23:12, 30 August 2016
Line 120:		Line 120:

	log results		log results
		+
		+	[[Category:Firmware]]
		+	[[Category:Software]]

← Older revision		Revision as of 20:55, 7 June 2013
Line 113:		Line 113:

	Press the switch on the front panel and you should see the green LED go off and red LED go on indicating configuration file reloaded. After few seconds, the red one should go off and green one come back on indicating that the reset switch works properly.		Press the switch on the front panel and you should see the green LED go off and red LED go on indicating configuration file reloaded. After few seconds, the red one should go off and green one come back on indicating that the reset switch works properly.
		+
		+	To make sure brst line on Clock Card is working, toggle the LEDs from their default state and then issue a reset command and make sure the LEDs go to their default state (only Green on) which would mean the reset worked.
		+	wb rc1 led 7
		+	(red and amber LED go on, green goes off)
		+	mce_cmd -x mce_reset
		+
	log results		log results

@@ Line 45: / Line 45: @@
 The Green LED should momentarily go off, the red LED should momentarily turn on and then when firmware is loaded, green LED would be on and red is off.
 This shows that '''application configuration is loaded successfully'''.
 == Testing General Features (card_all_test)==
@@ Line 67: / Line 70: @@
 copy the results into the test logfile and record the card_id on [[MCE CARD Serial-Number Lookup]]
-== Testing lvds rx/tx or command/reply lines==
+== lvds rx/tx or command/reply lines==
 run mce_status -s|grep fw_rev
@@ Line 85: / Line 88: @@
 Record the result in logfile.
-== Testing Sync Box communication ==
+== Sync Box communication and clock circuitry ==
 Check the amber LED and it should be on if the Sync input is not connected or if the Sync Box is off. Check to see the LED go off when the Sync Box is turned on and the fiber cable is connected to the Sync input. Now on mas PC, issue the following commands:
   wb cc select_clk 1
@@ Line 93: / Line 96: @@
 The last command should return 1 which means the Clock Card is still running from the Sync Box clk.
 Take some data to verify that the manchester decoder is working:
   mce_run test_data_xxxx 100 1
@@ Line 104: / Line 110: @@
 and the result should be 0 which means the clock has fallen back on the internal clock on clock card.
-== ==
+== reset switch and brst line ==
 log results

@@ Line 58: / Line 58: @@
    Firmware Revision:  5.0.e
    card_id          :  0x20be502
-   slot_id          :  [1]
+   slot_id          :  [8]
-   card_type        :  [1]
+   card_type        :  3
    card_rev         :  D
    fpga_temp        :  34 C pass
@@ Line 70: / Line 70: @@
 run mce_status -s|grep fw_rev
-and you should see all cards listed:
+and you should see all cards listed, make sure there are 9 replies.
-<RB cc fw_rev> 83886094
+cc fw_rev : 0x500000e
-<RB rc1 fw_rev> 83951616
+rc1 fw_rev : 0x5010005
-<RB rc2 fw_rev> 83951616
+rc2 fw_rev : 0x5010005
-<RB bc1 fw_rev> 83886087
+rc3 fw_rev : 0x5010005
-<RB bc2 fw_rev> 83886087
+rc4 fw_rev : 0x5010005
-<RB bc3 fw_rev> 00000000
+bc1 fw_rev : 0x5000000
-<RB ac fw_rev> 83886084
+bc2 fw_rev : 0x5000000
 Record the result in logfile.

@@ Line 21: / Line 21: @@
 === Programming via Front-panel JTAG connector===
 # Load FPGA firmware using Quartus. Firmware is located at http://e-mode.phas.ubc.ca/mce_firmware/. Run auto-detect and you should see list of devices. The part at the bottom of the list corresponts to Clock card FPGA and the part above it in the list is EPC16 or the "application configuration device". Right click on the row and choose a file to program. Load following firmware from the above directory: CC firmware 5.0.e, '''cc_v0500000e_15may2012.sof''' for FPGA and '''cc_v0500000e_15may2012.pof''' for EPC16. Then checkmark the program button for both devices and press start programming. The green LED should come up when programming is done.
 # If the tx/rx fibers are connected right, the red LED is off and the green LED is on. If the Sync Box fiber is connected and Sync Box is on, then the amber LED is also off.
 # Now make sure that the card communicates with the PC.
    mce_cmd -x rb cc fw_rev
@@ Line 30: / Line 28: @@
    Line   0 : ok : 0x500000e
-So far, you confirmed that FPGA is programmed correctly.
+So far, '''you confirmed that FPGA is programmed successfully and the fiber interface is working.'''
 Now, proceed to programming the factory-configuration device.
@@ Line 39: / Line 37: @@
 # Power on the MCE.
 # In Quartus, press on auto-detect and you should only see two devices listed. Choose the same pof file for EPC16.
-'''cc_v0500000e_15may2012.sof'''
+'''cc_v0500000e_15may2012.pof'''
 == Testing General Features (card_all_test)==
-We run a scrip on the mas PC to issue commands over the fibre to test the Readout Card unit under test. In this script, the following circuits are tested: LEDs, silicon ID chip, slot-id and pcb-revision identification pins, FPGA and board temperature sense circuitry, LVDS communication pairs.
+The following script is used to test features that are common to all MCE cards: LED, silicon id, card_type, PCB revision, LEDs, dip switches, etc.
-On mas PC, type: '''card_all_test'''
+On mas PC, type:
 The output should look like:
    ****** Check to make sure the LEDs on the target card switched status! ****
-   Unit Under Test  :  rc1
+   Unit Under Test  :  CC
-   Serial Number    :  SRC-216
+   Serial Number    :  SCC-069
-   Firmware Revision:  -0xfffa
+   Firmware Revision:  5.0.e
    card_id          :  0x20be502
-   slot_id          :  [4]
+   slot_id          :  [1]
-   card_type        :  [2]
+   card_type        :  [1]
-   card_rev         :  0
+   card_rev         :  D
    fpga_temp        :  34 C pass
    card_temp        :  28 C pass
-   results are in   :  /data/cryo/current_data/SRC-216_1285959943_all_test
+   results are in   :  /data/cryo/current_data/SCC-069_1285959943_all_test
 copy the results into the test logfile and record the card_id on [[MCE CARD Serial-Number Lookup]]
-== Testing Serial Configuration device and FPGA reconfiguration ==
+== Testing lvds rx/tx or command/reply lines==
-Load firmware into the configuration device as oppose to the FPGA now. The parallel configuration device, EPC16, is programmed through the JTAG port on the Clock-Card front panel. Here are the steps:
-* Run Quartus programmer and click on auto-detect. You should see 4 devices in the list.
+run mce_status -s|grep fw_rev
-* Select EPC16 device on top and click on change file to choose ''' cc_v05030001_12apr2012.pof''' (found in http://e-mode.phas.ubc.ca/mce_firmware/ )
+and you should see all cards listed:
-* Now select the device and click on program.
+<RB cc fw_rev> 83886094
-* When programming is done, turn off the power and turn it back on. If the Green Light is on, it means that you have successfully programmed the configuration device.
+<RB rc1 fw_rev> 83951616
-* on mas prompt, type:''' mce_cmd -x rb bc1 fw_rev''' and you should see the firmware revision of the firmware you loaded. This is usually noted in the filename of the file you chose.
+<RB rc2 fw_rev> 83951616
 Record the result in logfile.
 log results