- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In building the intel_rtile_cxl_top_cxltyp3_ed with the ooo enabled we get some design assistant failures around the timing, of concern are these:
TMC-20023 - Invalid Set Net Delay Assignment
TMC-20025 - Ignored or Overridden Constraints
TMC-20026 - Empty Collection Due To Unmatched Filter
Are there any updates to the constraints for this design?
- Tags:
- Quartus 23.2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have checked with the internal team. These DRC messages are expected. The engineering team is still working on cleaning up the sdc constraints in 23.3. The DRC violations should not impact timing, and not cause any functionality problem.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @brian1211
Is this related to https://community.intel.com/t5/FPGA-Intellectual-Property/CXL-type-3-design-example-Design-Assistant-Errors/m-p/1502466#M27791
These DRC Checks were enabled late in 22.4 onwards. These errors are expected for 23.1 and expected to be fixed by 23.3. DRC violations are not impacting the functionality so far.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @JonWay_C_Intel ,
Not worried about the DRC checks, it's the 700+ timing constraints from the various *.sdc files that aren't being used that I have issue with. They are below the DRC checks you mention that have been around for a while, the ones below (#7-9):
TMC-20023 - Invalid Set Net Delay Assignment
TMC-20025 - Ignored or Overridden Constraints
TMC-20026 - Empty Collection Due To Unmatched Filter
Are the new ones that are concerning.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the elaboration. Let me check and get back to you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have checked with the internal team. These DRC messages are expected. The engineering team is still working on cleaning up the sdc constraints in 23.3. The DRC violations should not impact timing, and not cause any functionality problem.
![](/skins/images/45C6C2D737ED71F4C51F0145C8CB1E9C/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page