Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
Intel Support hours are Monday-Fridays, 8am-5pm PST, except Holidays. Thanks to our community members who provide support during our down time or before we get to your questions. We appreciate you!

Need Forum Guidance? Click here
Search our FPGA Knowledge Articles here.
15331 Discussions

Quartus True and Simple DPRAM issue - does this affect Quartus II version 15.1 designs

CycloneICE
Beginner
164 Views

For Cyclone IV designs using dual port ram compiled with Quartus II v15.x (or v14.x),  are the True and simple DPRAM issues affecting Quartus Prime v18.1 and v20.1 relevant to the older revisions of compilers.

I am responsible for the sustaining of a number of mature products using cyclone IV FPGAs.

I would like to know whether time and effort need be expended to investigate this recent Quartus Prime PCN for DPRAM ram implementations using older revision compilers.

Most of the designs I am referring to were compiled using Quartus II v15.1

I would appreciate some feedback.

Thanks

 

 

0 Kudos
3 Replies
SyafieqS
Moderator
142 Views

Hi Stuart,


Are you referring to this KDB? Assuming it yes

https://www.intel.com/content/altera-www/global/en_us/index/support/support-resources/knowledge-base...


There is a screening patch to see if your design is affected.


CycloneICE
Beginner
131 Views

This KDB seems to pertain to Intel Quartus Prime software only.   

My mature design was compiled and implemented using Quartus II software revision 15.1 or earlier

Is this DPRAM bug only associated with version 18.1 or newer Intel Quartus Prime software ?

Does this KDB actually apply to the earlier Quartus II software releases ? 

I do not see a patch for vintage Quartus II ver 15.1 compiler to determine if this issue exist.

Please advise.

Thanks.

 

SyafieqS
Moderator
118 Views

Hi Stuart,


Yes, this KDB impacting prior Quartus stated. User is encourage to migrate to latest Quartus version for permanent fix


Reply