Community
cancel
Showing results for 
Search instead for 
Did you mean: 
AGarm
Beginner
452 Views

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

0 Kudos
18 Replies
79 Views

Hi,

 

Can you provide a sample test case to replicate the error?

 

Thanks.

AGarm
Beginner
79 Views

Hello. I did not try to significantly reduce my project. This is not an easy task. I am sending the archive of the Quartus project to the address supportreplies@intel.com . I really hope that Intel will find a solution to this difficult problem!

79 Views

Hi,

 

I have sent you a message, please confirm.

Please be informed that all the documents/files uploaded to the forum are accessible by the Public, you have ensure that those document/file is not confidential.

 

Thanks.

AGarm
Beginner
79 Views

Hi,

I found a solution to the problem myself!

I used the external VHDL editor of the source text, because the Quartus editor does not work correctly with the Russian font.

When describing the signal

signal C1_ret_bits: std_logic_vector (4 downto 0);

I mistakenly used the Russian letter C.

But what is surprising is that the previous compilation of the project project was successful. This erroneous description of the signal did not immediately cause Quartus's internal error, but only with the next complication of my project.

I managed to localize the problem only after I saved the VHDL source code with the Quartus editor.

AGarm
Beginner
79 Views

Only after saving the source text with the quartus editor did you get a syntax error during compilation!

- This is a real surprise for me. I have been using Quartus for over 10 years.

AGarm
Beginner
79 Views

I created a simple example. If this source file created by an external editor is compiled in Quartus, then Quartus does not detect a syntax error. Quartus will detect a sitnax error only after saving this file with the quartus editor!

AGarm
Beginner
79 Views

If you complicate this project, then perhaps an internal quartus error will occur. But until this dead end event, the user has no problems!

AGarm
Beginner
79 Views

Based on the detected Quartus parsing problem, I would like to receive professional recommendations from Intel specialists for the case of preparing the source texts of a VHDL project using third-party text editor programs in a multilingual environment. What software can detect non-English letters inside project source code files, excluding comments, before compiling a project in Quartus?

It is extremely inconvenient to save files each time by the Quartus editor with possible damage to non-English comments.

AGarm
Beginner
79 Views

And here is a specially created simple project with Russian letters, leading to the above internal quartus error. I post the source code and a screenshot.scr.jpg

AGarm
Beginner
79 Views

Only after saving the file with the Quartus editor are syntax errors found correctly.scr1.jpg

79 Views

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
Beginner
79 Views

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.

79 Views

Hi,

 

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

 

Thanks.

79 Views

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
Beginner
79 Views

Hi,

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

79 Views

Hi,

 

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

 

Thanks.

AGarm
Beginner
79 Views

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

 

79 Views

Hi,

 

Yes. I have reported the issue to engineering.

 

Thanks.