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.
15481 Discussions

Quartus programmer bug report: 13 crashes of Quartus in 3 days + solution

JOHI
New Contributor II
1,994 Views

Hello,

I share this info because it might be of help to the developers to get Quartus more stable:

Symptom:  Q17.1 Q18.1 crash at the end of the compile cycle. The program is compiled, but just after compilation Quartus crashes.

*** Fatal Error: Access Violation at 0X000007FEFD7038D8

Module: quartus.exe

Stack Trace:

    0x38d7: GetLengthSid + 0x27 (KERNELBASE)

   0x1500a: MultiByteToWideChar + 0x1a (kernel32)

   0x22265: __setusermatherr + 0xd5 (MSVCR120)

   0x26ff5: _access_s + 0x21 (MSVCR120)

   0x26fc8: _access + 0x8 (MSVCR120)

    0xb772: FIO_PATH::fullpath + 0x82 (CCL_FIO)

   0x3bad6: PGME_PROGRAMMER::engage_ocpp_mode + 0x8d6 (pgm_pgme)

   0x295b7: QThread::start + 0x427 (QtCore4)

   0x24f7e: _beginthreadex + 0x106 (MSVCR120)

   0x25125: _endthreadex + 0x191 (MSVCR120)

   0x159cc: BaseThreadInitThunk + 0xc (kernel32)

   0x5385c: RtlUserThreadStart + 0x1c (ntdll)

 

Multiple times, the crash report contains PGME_PROGRAMMER.

 

Observation:

Quartus Lite 17.1 & 18.1 = Crash

Quartus Standard 18.1 = Crash  (license Nios / Uart license was missing)

Quartus Standard + all necessary licenses = No Crash Anymore = solved 100 %.

It seems that when all is fully licensed, crash do not happen any more.

Project crashing can be shared if needed.

Added to this report: 13 stack traces of practically identical crashes.

Best Regards,

Johi.

 

0 Kudos
3 Replies
KhaiChein_Y_Intel
216 Views

Hi Johi,

 

Do you see the crash after cleaning the project?

 

Thanks.

JOHI
New Contributor II
216 Views

Hello KYeoh,

No, cleaning did not make any difference.

But, as explained in detail above, when I no longer needed the time-limited sof, because I obtained the necessary licenses, the crashes did no longer happen.

Since crashes seem to happen in the programmer part (see stack traces), your question regarding the relationship between cleaning and crashing during compile is something I am very interested in to know more about; After restarting Quartus, I could download the .sof that was generated during compile, and is was OK.

Can you explain the background of your question?

To be clear: Buying the software solved my issue but it would be nice is the lite version of Quartus also became more stable.

Best Regards,

Johi.

 

 

KhaiChein_Y_Intel
216 Views

Hi Johi,

 

Crash might happen if the compilation database is corrupted. Cleaning the project will clear the database for the previous compilation.

 

Thanks.

Reply