Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
20688 Discussions

Cyclone V and Gate Level Simulation

Altera_Forum
Honored Contributor II
2,674 Views

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.vo 

 

 

 

 

 

 

 

 

 

 

 

0 Kudos
8 Replies
Altera_Forum
Honored Contributor II
913 Views

Cyclone V = no gate level simulation 

 

Rely on TimeQuest
0 Kudos
Altera_Forum
Honored Contributor II
913 Views

 

--- Quote Start ---  

Cyclone V = no gate level simulation 

 

Rely on TimeQuest 

--- Quote End ---  

 

 

Thanks. 

 

Is there a reason that gate level is not supported?
0 Kudos
Altera_Forum
Honored Contributor II
913 Views

 

--- Quote Start ---  

Cyclone V = no gate level simulation 

 

Rely on TimeQuest 

--- Quote End ---  

 

 

Good info sharing. Dint aware of it till now.
0 Kudos
Altera_Forum
Honored Contributor II
913 Views

Reason is money, models for gate level simulation are $$$ and 28nm design is already $$$

0 Kudos
Altera_Forum
Honored Contributor II
913 Views

you are right, think it is a way to save $$.

0 Kudos
Altera_Forum
Honored Contributor II
913 Views

I'd bet that Altera decided that Timequest was more accurate than gate level simulation so there was no reason to support both methods.

0 Kudos
Altera_Forum
Honored Contributor II
913 Views

You are right. Also the CV should be of the low cost FPGA series.

0 Kudos
Altera_Forum
Honored Contributor II
913 Views

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