cdc vioaltions for caliptra_ss_top

[weih1234]

i got some cdc violations for caliptra_ss_top between jtag clock and caliptra clock. CaliptraIntegration helped to solve the violations in caliptra_top, however CaliptraSSIntegrationSpecification doesn't have guide for caliptra_ss_top level jtag and main clock crossing. can you provide the guide?

I attached the violations for your information. Thanks!

cailptra_ss_cdc.csv

[bharatpillilli]

@weih1234 2.0 or 2.1 question?

[weih1234]

It is 2.0

[clayton8]

@weih1234 - @ravithakurAMD is actively updating the CDC documentation to help you address these CDC errors. We do not consider this an RTL issue; rather, the documentation simply needs to be updated for your reference.

We will update this ticket once the revised documentation is ready.

[calebofearth]

Documentation for this was updated in #955.

@weih1234 please review it and let us know if you have additional feedback. We'll close this issue on 2025/12/8 if we don't hear from you.

[weih1234]

I applied new constrain and it works well. Thank you! Thanks, Wei

…

________________________________ From: Caleb ***@***.***> Sent: Monday, December 1, 2025 6:21 PM To: chipsalliance/caliptra-ss ***@***.***> Cc: Wei Huang (PROTINGENT INC) ***@***.***>; Mention ***@***.***> Subject: Re: [chipsalliance/caliptra-ss] cdc vioaltions for caliptra_ss_top (Issue #811) [https://avatars.githubusercontent.com/u/11879229?s=20&v=4]calebofearth left a comment (chipsalliance/caliptra-ss#811)<#811 (comment)> Documentation for this was updated in #955<#955>. @weih1234<https://github.com/weih1234> please review it and let us know if you have additional feedback. We'll close this issue on 2025/12/8 if we don't hear from you. — Reply to this email directly, view it on GitHub<#811 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BW6GVSS4LPLUZZMNS2DWXTD37TLPZAVCNFSM6AAAAACIY4G6I2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKOJZGU2TGOBSGY>. You are receiving this because you were mentioned.Message ID: ***@***.***>