Improve the GEM loader reliability with a pre-request (!112) · Merge requests · cmsgemonline / gem-daq / cmsgemos · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.

Laurent Petre requested to merge bugfix/gem-loader into develop Mar 09, 2021

Description

Title says it all. More details in the commit message:

It was shown that for yet undetermined reasons, the first bitstream sent
by the GEM loader IP core can be corrupted. This commit adds an additional
bitstream request before triggering any hard reset trying to improve the
reliability of the GEM loader.

Related Issue

How Has This Been Tested?

Deployed during the MWGR 2 at p5.

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

My code follows the code style of this project.
My change requires a change to the documentation.
I have updated the documentation accordingly.
I have read the CONTRIBUTING document.
I have added tests to cover my changes.
All new and existing tests passed.