Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ultrafast CDC checks do not check from "no clock" to a clock #244

Open
johnblaine opened this issue Apr 28, 2014 · 3 comments
Open

Ultrafast CDC checks do not check from "no clock" to a clock #244

johnblaine opened this issue Apr 28, 2014 · 3 comments
Assignees

Comments

@johnblaine
Copy link

Primitives like the MMCM generate signals where the clock is not modeled by Vivado. E.g., Locked. This should be covered by a CDC when it is used.

cdc
Thanks.
John

@GregDaughtry
Copy link
Contributor

David, did you look into this? I don't know if you should own this - perhaps we should assign this to johnblane to fix? ;-) It might also be covered by the new report_cdc tool

@johnblaine
Copy link
Author

Hi folks,

Yes I could own this. Not sure what the process is though.

John

John Blaine
Staff Tools & Methodology Application Engineer
Office: +44 (0) 1932 574 633
Mobile: +44 (0)7900 582 059

[cid:[email protected]]

From: Greg Daughtry [mailto:[email protected]]
Sent: 17 September 2014 20:06
To: Xilinx/XilinxTclStore
Cc: John Blaine
Subject: Re: [XilinxTclStore] Ultrafast CDC checks do not check from "no clock" to a clock (#244)

David, did you look into this? I don't know if you should own this - perhaps we should assign this to johnblane to fix? ;-) It might also be covered by the new report_cdc tool


Reply to this email directly or view it on GitHubhttps://github.com//issues/244#issuecomment-55943886.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

@dpefour
Copy link
Contributor

dpefour commented Oct 1, 2014

Hi John,

Thanks, that would be nice.

I suppose that one way would be:

  1.  Check whether report_cdc already covers the request or not. You might still have the testcases for the issue you reported.
    
  2.  Follow instructions from Online Wiki https://github.com/Xilinx/XilinxTclStore/wiki/Xilinx-Tcl-Store-Home . The starting point would be the Contributor Setup Steps followed by Modify an App in the Repository or Adding a New App to the Repository that might have few more information inside
    

By following the instructions, you will get from GitHub the latest version of the script.

I can help you if you have any question.

Thanks,
David

From: johnblaine [mailto:[email protected]]
Sent: Wednesday, October 01, 2014 1:36 AM
To: Xilinx/XilinxTclStore
Cc: David Pefourque
Subject: Re: [XilinxTclStore] Ultrafast CDC checks do not check from "no clock" to a clock (#244)

Hi folks,

Yes I could own this. Not sure what the process is though.

John

John Blaine
Staff Tools & Methodology Application Engineer
Office: +44 (0) 1932 574 633
Mobile: +44 (0)7900 582 059

[cid:[email protected]]

From: Greg Daughtry [mailto:[email protected]]
Sent: 17 September 2014 20:06
To: Xilinx/XilinxTclStore
Cc: John Blaine
Subject: Re: [XilinxTclStore] Ultrafast CDC checks do not check from "no clock" to a clock (#244)

David, did you look into this? I don't know if you should own this - perhaps we should assign this to johnblane to fix? ;-) It might also be covered by the new report_cdc tool


Reply to this email directly or view it on GitHubhttps://github.com//issues/244#issuecomment-55943886.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


Reply to this email directly or view it on GitHubhttps://github.com//issues/244#issuecomment-57434258.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants