Skip to content

GitLab

  • Menu
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 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cmsgemonline
  • gem-daq
  • cmsgemos
  • Issues
  • #62
Closed
Open
Created May 04, 2020 by Laurent Petre@lpetreOwner

Generate artifacts for the back-end boards

Summary

The new (and old) software architecture requires artifacts to be pushed to the back-end board to ensure correct operations. These artifacts include (not exclusive list):

  • The firmware bitstreams
  • The software RPC modules
  • The address table (as long as it useful on the back-end board)

Depends on #61, although the work on the RPC modules could be started before.

What is the expected correct behavior?

The artifacts are copied to a well-known location during the installation process so that high-level software can use them to configure the back-end board.

The well-know location prefix is likely to be ${CMAKE_INSTALL_FULL_DATAROOTDIR}, i.e. /opt/cmsgemos/share. The precise suffix should be discussed here and must be able to cope with the different GEM stations and back-end boards (let's call the combinations, flavors).

Assignee
Assign to
Time tracking