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
  • #403

Closed
Open
Created Feb 06, 2021 by Ille, Ondrej, Ing.@illeondrOwner0 of 5 tasks completed0/5 tasks

CAN Clock

Split CAN FD IP Core into two clock domains:

  1. CAN Clock
  2. System Clock

This is needed to meet oscillator tolerance requirements of CAN Bus. If this is not done, then also Memory bus needs to be clocked from oscillator which meets bit timing requirements on CAN bus! Typical MCU usage would however require two clock domains!

  1. Update System architecture with decision how it will be done (list all signals crossing CDC, and their CDC handling protocol). Decide about best/worst case clock frequencies ratio!
  2. Update User-guide to take "CAN clock" into account.
  3. Implement the change in RTL.
  4. Debug existing tests.
  5. Create tests / regressions which verify minimal/maximal ratios of clock frequencies.
Edited Jun 19, 2021 by Ille, Ondrej, Ing.
Assignee
Assign to
Time tracking