HF RM igloo2 development Tullio Grassi, 5 Nov 2014 Univ of Maryland

Committed and tested v (hex) Added stuff on SVN doc/ folder Tested in bld 904

QIE clocks with individual phase control The twelve QIE clocks are sent from the igloo2 to the QIE chips. Inside the igloo2, the clocks are synthesised using a 320 MHz, as if they were normal data lines. Also the data from the QIE10 chips are acquired at 320 MHz (oversampling)  major redesign. At power-up the twelve QIE clocks are often bad, they do not even look like clock signals. Many QIE10 chips will report DLL NoLock = 1. You can fix this simply with a Backplane_RST (or also changing the set value of each phase). I tried many fw to have them good at powerup, but no success.

First test of phase control of the QIE (sampling) clocks Probed with the oscilloscope: MClk from the backplane as trigger; QIE1 and QIE2 clocks on test points (they look identical). settingclk1_ph [ns]step [ns]

Data acquired with uHTRtool RAW0 RAW1 100BC FF05 0FFFF BC FF04 0FFFF BC 005AA FF04 0FFFF BC 005FF FF04 0FFFF BC FF05 0FFFF BC FF04 0FFFF CapIds are good The rest looks good as well 4-channel data format

Mysteries and problems about igloo2 on the latest version, many Differential Input I/O Pairs changed from registered to non- registered [see file HF_RM_igloo2_top_bankrpt.rpt ]. Why ? according to the Max delay analysis performed by the sw tool, our 320 MHz clock does not meet the frequency constraint: in v 1.12 the simulated frequency is 278 MHz in worst-case conditions, and 318 MHz in typical case (the part number has Speed Grade -1, which is the fastest one) DEVRST_N input can be important but is not clear (seems more like a power_enable than a reset) Timing constrains are still confusing. Related to this, Synopsys has changed format for the timing constraints (sdf format is now obsolete). Microsemi Libero will probably follow. And many others…

There are still a mysteries also on the Bridge FPGA Issuing a DEVRST_N (Bottom_RESET_N) from the Bridge FPGA to the igloo2 often upsets the Bridge FPGA  recover with a power-cycle. All these problems are probably more critical for HE than HF.