Quartus 19.2 back-annotation

[Mircea]

Hello,

I have a question about the Stratix10Mx, HBM example design, that I generate with Quarts 19.2.

I compile the Quarts generated project, and it compiles OK.

Device is: 1SM21BHN3F53E3VG.

After compilation, if I do a back-annotate device and pins, Quartus will crash.

On the same project, but without the HBM part instantiated, Quartus will back-annotate fine.

After I instantiate the HBM part, the project will compile, but will crash during back-annotation.

It's true that I need to back-annotate only once, but is this something we should worry about?

I can provide the projects, if needed.

Thank you very much,

Best regards,

Mircea

[Kenny_Tan]

Theoretically, it should not crash.

Can you use the latest release of Quartus Prime Pro 20.2?

If you were still seeing the crash, you will need to send us the design.qar file for duplication and the fix.

[Mircea]

Hi Kenny,

Attached is the design.qar.

Please, try to back-annotate it and see what it does.

Is this a known issue with Quartus?

Can there be more stuff that's wrong?

Thanks,

Mircea

[Kenny_Tan]

Can you post the crash message here? I will test your design in the latest release version to see if it had been fixed?

[Mircea]

Hi Kenny,

Here it what Quartus said:

Problem Details
Error:
Internal Error: Sub-system: IOO, File: /quartus/tsm/ioo/ioo_pin.cpp, Line: 481

retval != nullptr

Stack Trace:

    0x1385b: IOO_PIN::get_io_standard_desc + 0x12b (tsm_ioo)

   0x10b000: ADB_CDB_INTERFACE_BODY_IMPL::back_annotate_io_atom + 0x150 (ace_adb)

   0x10a799: ADB_CDB_INTERFACE_BODY_IMPL::back_annotate_atom + 0x629 (ace_adb)

   0x10a036: ADB_CDB_INTERFACE_BODY_IMPL::back_annotate_all + 0x336 (ace_adb)

     0x9207: ASL_BACK_ANNOTATER::do_back_annotate + 0x5f7 (prj_asl)

     0x4578: asl_back_annotate + 0x498 (prj_asl)

     0x9cd5: qatm_back_annotate + 0x435 (quartus_cdb)

     0x8847: QATM_FRAMEWORK::execute_pin_backannotation_pro + 0x217 (quartus_cdb)

     0x8d59: QATM_FRAMEWORK::execute_pro + 0x139 (quartus_cdb)

    0x137d9: qexe_do_normal + 0x1e9 (comp_qexe)

    0x19cef: qexe_run + 0x4cf (comp_qexe)

    0x1ad8a: qexe_standard_main + 0x26a (comp_qexe)

     0xa994: qatm_main + 0xa4 (quartus_cdb)

    0x14a08: msg_main_thread + 0x18 (CCL_MSG)

    0x160ae: msg_thread_wrapper + 0x6e (CCL_MSG)

    0x20fb0: mem_thread_wrapper + 0x70 (ccl_mem)

    0x13f8d: msg_exe_main + 0x20d (CCL_MSG)

     0xd7d8: __scrt_common_main_seh + 0x11c (quartus_cdb)

    0x17bd3: BaseThreadInitThunk + 0x13 (KERNEL32)

    0x6ce50: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Executable: quartus_cdb
Comment:
None

System Information
Platform: windows64
OS name: Windows 10
OS version: 10.0

Quartus Prime Information
Address bits: 64
Version: 19.2.0
Build: 57
Edition: Pro Edition

[Kenny_Tan]

I look into the database, it should be fixed in the latest release of Quartus Prime pro. Can you try to use that? https://www.intel.com/content/www/us/en/programmable/downloads/download-center.html

[Mircea]

Kenny,

Can you try and see if back-annotation works on the latest release, and then tell me for sure what the situation is?

Is this a known issue with Q19.2 that has been addressed later?

Thanks,

Mircea

[Kenny_Tan]

Yes, I had try it on the Q20.3. This quartus will be release soon.

It should be a known issue since it is not happening on Q20.3.

I will file a kdb/documentation for this.

[Kenny_Tan]

Do you have further queries on this?

[Mircea]

Hi Kenny,

I think we are set for now and we'll wait for the new Quartus 20.3.

Thanks,

Mircea

[Kenny_Tan]

Thanks, closing the case