- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quartus won't run a gate level simulation when using the Cyclone V family.
Is it possible to run gate level simulation with the Cyclone V devices? For other devices, Quartus generates simulation files: up_counter.vo up_counter_6_1200mv_0c_slow.vo up_counter_6_1200mv_85c_slow.vo up_counter_min_1200mv_0c_fast.vo But with the Cyclone V family it is only generating: up_counter.voLink Copied
8 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cyclone V = no gate level simulation
Rely on TimeQuest- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
--- Quote Start --- Cyclone V = no gate level simulation Rely on TimeQuest --- Quote End --- Thanks. Is there a reason that gate level is not supported?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
--- Quote Start --- Cyclone V = no gate level simulation Rely on TimeQuest --- Quote End --- Good info sharing. Dint aware of it till now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Reason is money, models for gate level simulation are $$$ and 28nm design is already $$$
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
you are right, think it is a way to save $$.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'd bet that Altera decided that Timequest was more accurate than gate level simulation so there was no reason to support both methods.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are right. Also the CV should be of the low cost FPGA series.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Static timing analysis alone does not allow for comprehensive verification. Among the issues
- STA cannot identify asynchronous interfaces - The error prone selection of false paths - Constraint requirements for multi-cycle paths - Common concurrence point along implementation flow to a known good test bench is lost.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page