AMC13 Initialization
Here is what Mr Wu has said recently about initializing the AMC13:
Hi,
From the attached data, it is likely a problem of the run start procedure:
1. There appears to be a clear counter command sent to amc13(write bit 1 to register 0) after 0xbf L1A have been sent, which makes dump data difficult to interpret. (Never clear counters after L1A started)
2. The AMC modules sent a reset to its DAQ_link module after L1A started. It has been repeatedly emphasized that AMC
modules should finish its initialization before amc13 is reset
Then he says:
It seems that your run start control had a problem: AMC modules sent reset to DAQ_link module
after amc13 getting the last general reset before L1A is enabled.
Remember always initialize AMC modules first,when they are all ready send a general reset to amc13.
L1A can be enabled only when amc13 TTS is ready again.
So I think the take-away is that you should do it this way:
- Make sure there are no L1A happening
- Initialize the uHTR, including sending a reset to the DAQ link firmware module (in the uHTR)
- Initialize the AMC13. Issue a general reset and counter reset (not sure the order matters; I think it doesn't)
- Enable L1A
Some more notes about what to do after TCDS clock interruption (perform these steps with no
L1A coming in):
- resetPLL or reconfigure FPGAs to resync AMC13 to TCDS stream
- reset TTC receiver logic of all AMC modules
- general reset to AMC13
--
Eric Hazen - 07 Oct 2022
Comments