Patch Release v3.8.4
Pull Requests Since v3.8.3
Unlabeled
- #176 - V3.8.3 trigger pipeline fix
- #173 - Add Ruckus Flag to Load XCI Instead of DCP
- #172 - Updating code comments for Ultrascale/Ultrascale+ GTs wrapper
Pull Request Details
Updating code comments for Ultrascale/Ultrascale+ GTs wrapper
Author: | Larry Ruckman [email protected] |
Date: | Wed Sep 25 11:10:48 2024 -0700 |
Pull: | #172 (4 additions, 3 deletions, 4 files changed) |
Branch: | slaclab/stableClk-gt-comment |
Notes:
Description
- StableClk (which is GT's drpClk) in the IP core configured for 156.25MHz/2 (78.125MHz)
Add Ruckus Flag to Load XCI Instead of DCP
Author: | Larry Ruckman [email protected] |
Date: | Wed Oct 2 09:59:32 2024 -0700 |
Pull: | #173 (29 additions, 19 deletions, 3 files changed) |
Branch: | slaclab/xci-option |
Notes:
The ruckus.tcl files that load IP cores now look for an
LCLS_TIMING_XCI
environment variable.
If it is set to 1, then the XCI file is loaded instead of the DCP.This is useful in simulation. For example, add this line to the target makefile so that the XCI is loaded when building the project for VCS simulation.
vcs: export LCLS_TIMING_XCI=1
V3.8.3 trigger pipeline fix
Author: | Larry Ruckman [email protected] |
Date: | Thu Nov 14 12:48:51 2024 -0800 |
Pull: | #176 (90 additions, 50 deletions, 1 files changed) |
Branch: | slaclab/v3.8.3-trigger-pipeline-fix |
Notes:
I fixed a long standing problem (and a newly discovered one) where changing the trigger configuration parameters, namely delay and width, while the trigger pipeline is enabled causes errors that can overflow the pipeline (negative delay change) or produce the wrong delay (width change).
The one cycle push of delay onto the fifo was replaced with two pushes, each representing a transition of the output trigger state.