Setup for reading the ITkPixV1 quad module with YARR

Physical components:

Image Removed

The module

Image Removed

Power adapter

Image Removed

...

...

Notes: 

• The birth ID of 20UPGR91101015 was 20UPGR92101015 (which should be used for DB search) and the module ID changed when shipped to CERN. 
• eFuse burning of Chip 1 0x15448 ID had a mistake that burnt 0x15408 instead. ChipNameCheck during configuration may complain.

• Use the 16x1 configuration in both software and firmware (you can check the firmware with ./bin/specComTest, and reflash the firmware if needed)

...

• .

• The 1 DP readout adaptor had 10KOhm resistor pulldown for each data line leg. This is deemed unnecessary and may introduce more noise. So they were remove as of May/12/2023. 
• There is an inconsistency in the 1DP readout adaptor design files. The DP pin numbers printed on adaptor PCB next to the DP connector disagree with the schematics (see table below).    

Module Powering:

Image Removed

Power supply. Set to 2V (possibly more depending on loss in the wires) and 6.1A (1.526A per chip)

Image Added

Running digital scans

Use the following tool to pull the config cards from the production database:

...

With fan + thermal pad, the module runs very hot at 36  - 38 C after configuration.

Digital scan:

bin/scanConsole -r configs/controller/specCfg-rd53b-16x1.json -c configs/20UPGR91101015/20UPGR91101015_L2_warm.json -s configs/scans/rd53b/std_digitalscan.json -p -n 1

...

Can be solved by boosting the amplitude and preemphasis of the CMD CML driver. According to Timon, the default ones are sufficient for the SCC but not for the quad module because of the additional flex + adapter card. Timon's recommended quad settings are:

...

From tests, 3 chips on this module work pretty consistently with these settings while the last one (0x15448) always has some issues (only tested digital scans so far). Following Alex's initial observations, further setup checks seems to indicate chip 4 (0x15448) prefers cmlBias0/1=500/0.  

An explanation on the connectivity:

In each of the chip configs, you have a DataMergeOutMux variable which tells you the mapping between the internal data lanes and the external GTX lanes. For example, looking at the first row for chip1, this means that internal lane 2 is matched to GTX0, lane 3 to GTX1, lane 0 to GTX2, lane 1 to GTX3. Also, SerEnLane is set to the bit that will only enable the internal lane 0 (in this example, 4 = 0100). In  In particular, since we usually only use the internal lane 0 for scanning on a chip, this tells us that we should expect to see data on Chip1 GTX2, Chip2 GTX0, Chip3 GTX3, Chip4 GTX0.

Next, If you look at the top left of the data adapter, you can see the following information: 

Chip#, External data lane,  DP pins

Chip3: GTX3 (1, 3)

Chip2: GTX0 (4,6)

Chip1: GTX2 (7,9)

Chip4: GTX0 (10,12)

The ITkPixV1.1 Digital Quad is based on the V2.4 common Quad hybrid design with its schematics  indicating that only two GTX output of each chip are physically connected to the module ZIF. The quad module ZIF interface and further connectivity details of the to the V1.0 Quad Readout Adaptor with 1 DP connector serving 1 line per FE (schematics) via straight-through module Q/C data flex is captured in the "ITkPixV1-Quad" tab of the RD53A Ring Connectivity Stanford Drive GoogleSheet. The Quad Readout Adaptor further down selects the data GTX channels to only keep one data GTX per FE to form the 4 channels on the single DP connector:  

• There was an inconsistency in adaptor V1.0 documentation between schematics and silkscreen labels which turned out to be a problem of schematic PDF copy for v1.0 which was fixed by Aleksandra on May/22/2023. Actual schematic and PCB prints were OK all along.   

Note: Note that these GTX and Chip maps are the same as what we expect from DataMergeOutMux. In the standard DP cable pin mapping, (1,3) is data0, (4,6) is data1, (7,9) is data2,  and (10,12) is data3. That's why in our config file, we have: chip1 rx2, chip2 rx1, chip3 rx0, chip4 rx3. This means that as long as we are using this adapter with the same config files, we should expect 1 data lane per chip while scanning, with no data merging.

Some notes from schematics reading: For the readout adaptor in module QC setup with ZIF facing the module ZIF, the ZIF pin orders are reversed between two sides when connecting with a straight QC flex. This looks like is handled coherently (unlike RD53A) between the module and adaptor. Single polarity also preserved p->p,n→n for all data lines, but it looks like CMD deliberately flipped polarity at the adaptor as needed for ITkPix vs RD53A.    

Setup for reading the ITkPixV1 quad module with YARR + type0 ring + pp0

Image RemovedImage Added

Use the special ITkPix → type0 ring flex from Steven (not the one for RD53A)

...