Forum Discussion

AGarm's avatar
AGarm
Icon for New Contributor rankNew Contributor
6 years ago

Internal Error: Sub-system: AMERGE, File: /quartus/atm/amerge/amerge_kpt_op.cpp, Line: 169

At the stage of Analysis&Synthesys of my VHDL project, the program Quartus Prime Lite 18.1 falls into an internal error. I give the report below. Pre-deleting db and incremental_db folders does not solve the problem. How do I get out of this deadlock?

Problem Details

Error:

Internal Error: Sub-system: AMERGE, File: /quartus/atm/amerge/amerge_kpt_op.cpp, Line: 169

map_kpt_db

Stack Trace:

0x66fa5: AMERGE_KPT_OP::work + 0x565 (atm_amerge)

0x6e1e9: AMERGE_MERGER_OP::perform_post_merge_operations + 0x979 (atm_amerge)

0x4c66: amerge_combine_netlist + 0x2e6 (atm_amerge)

0x4e7f: amerge_mini_merge + 0xf (atm_amerge)

0x12c90: QSYN_FRAMEWORK::do_mini_merge + 0x330 (quartus_map)

0x23202: QSYN_FRAMEWORK::write_qic_databases + 0x932 (quartus_map)

0x21f44: QSYN_FRAMEWORK::write_databases + 0x114 (quartus_map)

0x11378: qexe_do_normal + 0x2a8 (comp_qexe)

0x16142: qexe_run + 0x432 (comp_qexe)

0x16e51: qexe_standard_main + 0xc1 (comp_qexe)

0x1b08b: qsyn_main + 0x51b (quartus_map)

0x12e98: msg_main_thread + 0x18 (CCL_MSG)

0x1467e: msg_thread_wrapper + 0x6e (CCL_MSG)

0x16660: mem_thread_wrapper + 0x70 (ccl_mem)

0x12761: msg_exe_main + 0xa1 (CCL_MSG)

0x29872: __tmainCRTStartup + 0x10e (quartus_map)

0x17bd3: BaseThreadInitThunk + 0x13 (KERNEL32)

0x6ced0: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Executable: quartus_map

Comment:

None

System Information

Platform: windows64

OS name: Windows 10

OS version: 10.0

Quartus Prime Information

Address bits: 64

Version: 18.1.0

Build: 625

Edition: Lite Edition

18 Replies

Show More
  • KhaiChein_Y_Intel's avatar
    KhaiChein_Y_Intel
    Icon for Regular Contributor rankRegular Contributor
    6 years ago

    Hi,

    It is glad that you found a root cause of this error.

    Understand that you are using the Lite edition of the software. I tried to replicate the error in Standard and Pro edition of the software as well. Standard edition software issued the same internal error and Pro edition software compiled the design successfully. I have filed a case to report the error and observation to our engineering team. Thanks for reporting this to us.

    Thanks.

  • AGarm's avatar
    AGarm
    Icon for New Contributor rankNew Contributor
    6 years ago

    Thanks for the answer. And what exactly needs to be done so that users of Quartus, when using a third-party text editor, avoid possible inadequacy of parsing? This severe quartus error casts doubt on the correctness of the parsing of this software. In these situations, I and other Quartus Lite and Standard users need a specific recipe for action.

  • KhaiChein_Y_Intel's avatar
    KhaiChein_Y_Intel
    Icon for Regular Contributor rankRegular Contributor
    6 years ago

    Hi,

    I have yet to receive the feedback from the team. I will provide an update once I received the reply.

    Thanks.

  • KhaiChein_Y_Intel's avatar
    KhaiChein_Y_Intel
    Icon for Regular Contributor rankRegular Contributor
    6 years ago

    Hi,

    Below is the reply from the team:

    None of the tools in the Quartus tool chain support extended ASCII chararter set, not only the GUI, parsers, assignment utilities.

    Please cleanup the entire source code from these characters.

    You can use open source text editors to detect and fix the source code.

    Thanks

  • AGarm's avatar
    AGarm
    Icon for New Contributor rankNew Contributor
    6 years ago

    Hi,

    Does Intel ignore the problem of incorrect parsing when extended ASCII-codes are found in the source code?

  • KhaiChein_Y_Intel's avatar
    KhaiChein_Y_Intel
    Icon for Regular Contributor rankRegular Contributor
    6 years ago

    Hi,

    I have requested the fix for this internal error. Kindly edit the source file as a temporary workaround at the moment.

    Thanks.

  • AGarm's avatar
    AGarm
    Icon for New Contributor rankNew Contributor
    6 years ago

    Thanks. I am using a workaround. But I hope that Intel will solve the problem of incorrect parsing.