Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Sign in
P
Platform-independent core collection
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 11
    • Issues 11
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • Wiki
    • Wiki
  • image/svg+xml
    Discourse
    • Discourse
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • Projects
  • Platform-independent core collection
  • Issues
  • #23

Closed
Open
Opened Apr 20, 2020 by Javier Serrano@serrano
  • Report abuse
  • New issue
Report abuse New issue

Regression introduced in gc_sync_ffs.vhd

gc_sync_ffs now uses gc_sync, gc_posedge and gc_negedge. In the case where g_sync_edge = "negative", gc_sync_ffs uses the falling edge of the clock signal, but the underlying blocks use the rising one.

Edited Apr 20, 2020 by Javier Serrano
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: project/general-cores#23