To-Do List

• eye-scans for all transceivers
• work on high-speed-digitizer timing robustness using teststand
  • occasional need to restart hsdioc process
  • kcu1500 can lose link and hsd loses/regains power, and can only be recovered by power cycling cmp node
• check wave8 timing robustness
• (almost done) program hsd firmware over pcie?
• manufacture new xpm boards (4 for txi)
  • do we need another xpm/crate order for mfx? (separate from LCLS-II-HE?).  go from mfx hutch back to 208 or the mezzanine?
• reproduce/fix timing nodes assigning wrong timestamp to configure transition by 1 or 2 buckets
  • matt thinks this is on the receiver side: some fifos that carry daq data separate from timing data.  matt thinks perhaps we have to connect the resets to those fifos.
  • have seen this is hsd/wave8.  see both being problematic after a power outage here: /cds/home/opr/tmoopr/2024/03/04_17:11:56_drp-srcf-cmp030:teb0.log (and Riccardo saw it in his tests, below)
• (perhaps done by fixing reset logic?) reproduce/fix link-lock failure on timing system KCUs
• make pyxpm processes robust to timing outages?
• (done) ensure that Matt's latest xpm firmware fixes the xpm link-glitch storms
• (perhaps done by fixing reset logic ?) reproduce/fix TxLinkReset workaround
• (perhaps done by fixing reset logic?) reproduce/fix xpmmini-to-lcls2timing workaround
• (done, fixed with equalizer 0x3 setting) check/fix loopback fiber problem in production xpms in room 208
• after Julian's fixes in late 2023 on April 7 we had a failure where cmp002 kcu wouldn't lock to its timing link.  power cycling "fixed" the problem.
• (also after Julian's fixes in late 2023) this file shows a failure mode of a tdet kcu1500 on drp-srcf-cmp010 where its timestamps were off by one clock-tick: teb log file showing the cmp010 problem: /cds/home/opr/rixopr/scripts/logfiles/2024/04/08_11:58:28_drp-srcf-cmp013:teb0.log.  Powercycling "fixed" the problem.  Split event partial-output from that log (two Andor's on cmp010 timestamps were incorrect, since all other detectors showed 0x8ff3 at the end):

rix-teb[2111]: <W> Fixup Configure, 008a4a15bf8ff2, size 0, source 0 (andor_norm_0)
rix-teb[2111]: <W> Fixup Configure, 008a4a15bf8ff2, size 0, source 1 (andor_dir_0)
rix-teb[2111]: <W> Fixup Configure, 008a4a15bf8ff3, size 0, source 2 (manta_0)
rix-teb[2111]: <W> Fixup Configure, 008a4a15bf8ff3, size 0, source 3 (mono_encoder_0)

• XPM Link issues 2024/04/10-2024/04/11:
  • Around 14:00-14:10 on 2024/04/10, RIX Grafana page shows there were fairly global XPM issues (measured by XPM RxDspErrs  rates)
  • XPM5 link (XPM3-5) goes down around 14:07 on 2024/04/10
  • Other XPMs recover but 5 does not, and the link stays down.
  • xpmpva shows XPM5 looks mostly healthy except for the RxLinkUp 
  • Required TxLinkReset  to restore RxLinkUp  (on 2024/04/11 ~09:15). An earlier attempt on 2024/04/10 in the afternoon did not appear to have resolved the issue.
  • 

Summary Of Testing

These are the results of the tests that have been conducted in the FEE alcove to determine if the XPM glitch can be reproduced.
Every test is run from a starting behavior where the DAQ can allocate, configure, run, and disable.
Whenever the DAQ does not follow the starting behavior remedies are applied to recover it.

xpm10 and 11 connections

XPM schematics

Testing Details

In 2023/10/24 :

XPM firmware 3.5.4
Opal_config.py has xpm mini – timing2 hack

In 2023/10/26:

Observation Of Front-Panel XPM Link Glitch With Version 3.5.4

Perhaps fixed by Matt in later firmware version?

XPM11 glitches between 4pm and after 6pm and also around 10:10 am the next day

2023/10/27: updating firmware

xpm11  to xpm_noRTM-0x030601000-20231011111938-weaver-645bee8.mcs
xpm10 to xpm-0x030601000-20231011111954-weaver-645bee8.mcs

XPM firmware 3.6.0 (?3.6.1?)
Opal config does not have xpm mini -timing2 hack
cnf file uses -D fakecam for additional timing nodes

in 2023/10/30

example of the timing shift in the timing nodes (before -D fakecam).

in 2023/11/14

in 2023/11/17

New opal_config.py: remove sleep while requesting mini/v2 introduce check for RxId instead with timeout of 10 repeats.

in 2023/11/21 switching XPM firmware

from drp-neh-ctl002

~weaver/FirmwareLoader/rhel6/FirmwareLoader -a 10.0.5.104 /cds/home/w/weaver/mcs/xpm//xpm_noRTM-0x03050400-20230409095511-weaver-dirty.mcs
~weaver/FirmwareLoader/rhel6/FirmwareLoader -a 10.0.5.102 /cds/home/w/weaver/mcs/xpm//xpm-0x03050400-20230419122542-weaver-c6987c4.mcs

then fru-restart from psdev xpm 10 and xpm 11 in sequence, not together.

first light presents a problem with XPMPVA and GROUPCA

xpmpva XPM11 does not work 
fru-restart bring it back alive
OPAL does not respond to roll call,
TXLINKRESET XPM11 in XPM10 brings OPAL back to live

observing the logs there are several instances of :
21_10:02:16_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 3245855222 3245855222 resetting. Iteration: 1
21_10:02:16_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 3249109743 3249109743 resetting. Iteration: 2
21_10:11:36_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 3561772053 3561772053 resetting. Iteration: 1
21_10:11:36_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 3565026528 3565026528 resetting. Iteration: 2
21_10:11:36_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 3568281227 3568281227 resetting. Iteration: 3
21_10:11:36_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 3571538383 3571538383 resetting. Iteration: 4
21_10:36:38_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 0 0 resetting. Iteration: 1
21_10:36:38_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 3255210 3255210 resetting. Iteration: 2
21_11:34:43_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 94190235 94190235 resetting. Iteration: 1
21_11:34:43_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 97444648 97444648 resetting. Iteration: 2
21_11:34:43_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 100699006 100699006 resetting. Iteration: 3
21_11:34:43_drp-neh-cmp005:fee_fzpopal_0.log:*** Timing link stuck: 103957466 103957466 resetting. Iteration: 4

switching XPM firmware back to 3.6.1

~weaver/FirmwareLoader/rhel6/FirmwareLoader -a 10.0.5.102 /cds/home/w/weaver/mcs/xpm/xpm-0x030601000-20231011111954-weaver-645bee8.mcs
~weaver/FirmwareLoader/rhel6/FirmwareLoader -a 10.0.5.104 /cds/home/w/weaver/mcs/xpm/xpm_noRTM-0x030601000-20231011111938-weaver-645bee8.mcs

no instances of "*** Timing link stuck" in the logs

Power-on the tixel computer (the equivalent of cmp005) with the fiber unplugged, then we plugged in the fiber and it didn’t lock until we did xpmmini→lcls2. It appears that yanking the timing fiber can cause disturbances in the system, but they are not repeatable 100% of the time. XPMs Power spikes can set the DAQ in a behavior similar to the XPM glitch, but only if pyxpms are running. To be repeated.

Upgrading XPM firmware seems to have mitigated all the issues (to 3.6.0 from 3.5.4). The bucket issue becomes more prominent, probably because other issues are not happening. This issue appears when power cycling the xpm11. Also, xpmmini issue could appear when connecting already powered up nodes.

in 2023/11/27

testing double offence.
rebooting a node with cameralink without the fiber connected and connect the fiber after

Brainstorming Session

Nov. 16, 23 with mona, dan, weaver, caf, claus, melchior, cpo

proposal:

- move ric/mona/christos to xpm10 (for the future)
- give riccardo the whole system for the day and he messes with xpm10
- add startupMode=1 kwarg to opal

new xpm firmware (leaving xpm10 alone, no xpmmini->lcls2 hack):
riccardo can't reproduce the errors, except for bucket skipping
(txlinkreset fixed it for matt, but not riccardo and ric)

old xpm firmware (also messing with xpm10 with xpmmini->lcls2): riccardo could reproduce
xpm link glitch and txlinkreset (once) and (likely) xpmmini issue

theories:
- maybe ConfigLclsTimingV2 isn't reliable (should perhaps poll
  on something like rxid!=0xffffffff) 
- either new xpm firmware makes things better
- or we need to mess with xpm10 to reproduce problems
- or we're unlucky and can't reproduce (or we're not doing the right
  things to reproduce)
- might need a minimum length of time to tickle the issues (matt says
  try 30 minutes to 1 hour)

matt has an idea for bucket-jumps.  could direct julian.

Results from Julian

• has kcu1500 xpm (not xpmmini) transmitting to txi epixHR
• with Dawood observed RxLinkUp never came up until they added debugging stuff
  • saw something weird with the logic that reset the GTH on errors (state machine stayed in reset): this is fixed
  • never saw any 929kHz frames counted (perhaps similar to xpmmini→lcls2timing issue we also observed?): not fixed
    
    • matt asks: are they stuck at zero? polarity wrong? two-byte sequences aligned on wrong byte?
• also saw that the ConfigLclsTimingV2 button in devGui didn't work correctly (a missing register) and found a software bug which he has fixed for epixHR, but which may be broken elsewhere (fixed for epixHR)
  • Julian will check camera link as well.

Going Forward

(from mtg on Nov. 27, 2023)

• Julian:
  • focus on the stuck frames in the epixHR system
  • four prototype XPM boards are in production with new connector (only 1 so far?).  Larry will work with Julian (with advice from Matt) to test the boards.  One goes to BPM group, another to low-level-RF test stand.  Not clear who these are going to (we're not the only customer)
  • will implement bucket-hopping fix (with advice from Matt)
• Riccardo
  • will test when bucket-hopping fix is available
  • non-self-locking xpm ports
  • longer term: add hsd/wave8 systems to test stand
• cpo will try to reproduce the stuck-frames (which we "fix" with xpmmini→lcls2 workaround) with the tixel system that Christos Bakalis is using.  Now scheduled for Dec. 12

Touch Base on Jan. 5, 2024

(Julian, matt, Riccardo, cpo)

• from Julian:
  • fixed off-by-one word problem for epixhr only
  • found an issue with all firmware (including camlink).  has fix for camlink as well but not pushed to git (should go into lcls2-pgp-pcie-apps).  aim for a new official version by Wednesday jan. 10 2024.
  • has played with latest XPM ATCA carrier board with multiple old AMC boards (6 boards).  the XPM has the new connector.  changed equalizer parameters to get almost all the AMC cards (5) working (one does not boot at all).  used same ATCA board.
  • equalizer parameters may fix room 208 XPM link issues: have one parameter that works for all boards, but using fiber loopback.  equalizer settings might need to change depending on fiber length?
    • equalizer parameters are visible in rogue (xpm python should set these, currently use the defaults?)
  • some older AMC cards (C02 is the old version, currently on C04?) may need a re-work which we may not have?  might also explain the room 208 issues?
  • don't know the status of the other 3 prototype XPM boards
• from Matt:
  • have a new xpm version with the "Julian fix".  test in fee alcove?
  • for the bucket-hopping fix need to connect a reset to a FIFO
• fixes we would like before start of running in early Feb. 2024:
  • fixes we would like:
    • equalizer, "Julian fix", bucket-hopping 
  • systems we like to fix:
    • xpm, camlink (now generic in lcls2-pgp-pcie-apps), timing, hsd, wave8, tpr system
    • other systems that need it: epixhr, epixm, epixuhr, high-rate encoder, ued epix kcu1500, tixel
  • we think maybe were can do this by early Feb. 2024

To do:

• Julian:
  • provides equalizer parameters
  • works on remaining 3 XPM prototypes to make sure they're good
  • provides lcls2-pgp-pcie-apps firmware for camlink
• Riccardo:
  • check the room 208 xpm fiber-loopback with the new equalizer parameters when they are available
  • check the bucket hopping fix when it is available
  • (lower priority) ideally add hsd/wave8 to the teststand
    • to try to get the data links to be robust to power outages and fiber-unplugs
    • possibility to put it in an existing drp node (if we remove infiniband card) or cpo thinks we may have a spare chassis (setup from Omar might block us)
• Matt:
  • provides new firmware with above fixes, and programming of equalizer values
• Chris:
  • work with Christos to get the fixes in the tixel