Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Sign in
W
White Rabbit core collection
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 29
    • Issues 29
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Schedules
  • Wiki
    • Wiki
  • image/svg+xml
    Discourse
    • Discourse
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • Projects
  • White Rabbit core collection
  • Issues
  • #96

Closed
Open
Opened May 12, 2022 by Maciej Lipinski@lipinskimm
  • Report abuse
  • New issue
Report abuse New issue

Possible bug in streamers

From this code, it seems that the fixed latency value should be always configured in units of 8ns https://ohwr.org/project/wr-cores/blob/proposed_master/modules/wr_streamers/fixed_latency_ts_match.vhd#L152

while it seems that it might depend on the system clock (16ns for 62.5MHz, 8ns for 125MHz). This is what we observed with John in the wr2rf board. TO BE INVESTIGATED

Assignee
Assign to
wrpc-v5.0
Milestone
wrpc-v5.0
Assign milestone
Time tracking
None
Due date
No due date
2
Labels
bug feature
Assign labels
  • View project labels
Reference: project/wr-cores#96