Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C cmsgemos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 17
    • Merge requests 17
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cmsgemonline
  • gem-daq
  • cmsgemos
  • Merge requests
  • !291

Bring basic X2O compatibility

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Laurent Petre requested to merge feature/x2o-compatibility into main Sep 29, 2022
  • Overview 2
  • Commits 3
  • Pipelines 6
  • Changes 13

Description

This merge brings basic compatibility with the X2O v1 (as well as the APEX) back-end board. Except for the addition of a sysroot, CMake toolchain file, and basic build, including the CI, the MGT polarities configuration routine has been updated. Instead of relying on hard-coded values, the MGT polarities and now taken from the link configuration description exposed by the firmware is specific registers.

Related Issue

Fixes #228 (closed), #229 (closed), and #230 (closed).

How Has This Been Tested?

Taking runs on the GE1/1 integration setup in b904 backed up by a CTP7 is still working seamlessly. The MGT TX & RX polarities have been compared before and after this MR. Optionally pending tests on an APEX or an X2O v1 board.

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.
Edited Oct 21, 2022 by Laurent Petre
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/x2o-compatibility