Skip to content

GitLab

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

Closed
Open
Opened May 02, 2020 by Ille, Ondrej, Ing.@illeondrOwner

Non-synchronisation on dominant transmitted bit

An exception to re-synchronisation rule is not to perform resync with positive phase error when node does transmitt dominant bit.

In current implementation, this exception is driven in protcol control fsm when node is transmitter and it does transmit dominant bit.

This however does not cover all cases of dominant bit transmission! E.g. when node transmitts an error frame it also does transmitt dominant bit (it does not even have to be transmitter) and it should NOT perform positive resynchronisation!

This should be fixed although there is no test for this in compliance sequence (if e.g. node is receiver).

Assignee
Assign to
ISO optimizations
Milestone
ISO optimizations
Assign milestone
Time tracking
None
Due date
None
Reference: canbus/ctucanfd_ip_core#357