Difference: AMC13UserManual (24 vs. 25)

Revision 2523 Sep 2015 - EricHazen

Line: 1 to 1
 
META TOPICPARENT name="HcalDTC"
THIS MANUAL IS INCOMPLETE but what is written here should be more accurate and up to date than the old "functional specification". Please e-mail me if you find mistakes/omissions here (Eric H).
Line: 13 to 13
 

DAQ Outputs

Changed:
<
<
The AMC13 implements the S-Link Express protocol using a core provided by CMS CDAQ. This is currently a 5.0Gb/s link, received by the FedKit (see CMSFedkitManual) or by an AMC13v1 (Virtex-6 version only) running special firmware version 0xff.
>
>
The AMC13 implements the S-Link Express protocol using a core provided by CMS CDAQ (details here) This is currently a 5.0Gb/s link, received by the FedKit (see CMSFedkitManual).
  The AMC13 has 3 SFP transceivers which may be used for DAQ. There are 3 possible configurations, determined by the value written to CONF.SFP.ENABLE_MASK. In addition, CONF.EVB.ENABLE_DAQLSC must be set to '1'. The AMC13Tool2 command daq may be used to accomplish this configuration.
Line: 24 to 23
 
SFP0, 1 3 SFP0 for AMC1-AMC6, SFP1 for AMC7-AMC12
SFP0, 1, 2 7 SFP0 for AMC1-AMC4, SFP1 for AMC5-AMC8, SFP2 for AMC9-AMC12
Changed:
<
<
After changing the DAQ output configuration the logic and high-speed transceivers must be reset by writing to ACTION.RESETS.DAQ (AMC13Tool2 command rd).
>
>
At power-up the S-Link Express core and associated GTX SERDES will be enabled for any SFP which are installed. The AMC13 must still be configured to send data on the appropriate SFP by writing the registers described above. Normally, ACTION.RESETS.DAQ should not be written as this will cause the GTX to be reset again, possibly bringing the link down.

Before data can be acquired through the link, the S-Link Express core must be properly configured by taking action on the receiver side (see uFEDKIT documentation for details)

After changing the DAQ output configuration the logic and high-speed transceivers may be reset by writing to ACTION.RESETS.DAQ (AMC13Tool2 command rd) but after this the links must be reconfigured from the receiver end.

  The DAQ sender firmware itself was provided by the CMS cDAQ group. Links to the firmware in the CERN SVN and it's documentation may be found here:
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback