Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C CTU CAN FD IP Core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • canbus
  • CTU CAN FD IP Core
  • Issues
  • #434

Closed
Open
Created Sep 19, 2021 by Ille, Ondrej, Ing.@illeondrOwner

Re-work operating modes

Currently, there is only single bit which enables operation of CTU CAN FD (SETTINGS[ENA]). All modes (ROM, LOM, STM, etc...) are handled by dedicated bits in MODE register, and the protection of these bits is added to disallow their change during run-time.

It would be better, to have operating mode FSM, which would be communicating with protocol control FSM, and have this FSM-state (device operating mode) exposed to user.

Right now it is unclear what is the behavior if multiple special modes are combined together.

It still needs to be re-though what will be the granularity of operating modes of the device.

Assignee
Assign to
Time tracking