Forum Discussion
Error: quartus_map ended unexpectedly
Hi there,
I'm running Quartus II 10sp1 on ArchLinux. . When I'm trying to compileLIBRARY IEEE;
USE IEEE.STD_LOGIC_1164.ALL;
ENTITY my_and2 is
PORT(A, B: IN STD_LOGIC;
C: OUT STD_LOGIC);
END my_and2;
ARCHITECTURE behav of my_and2 IS
BEGIN
PROCESS(A, B)
BEGIN
C <= A AND B;
END PROCESS;
END behav; I've got this error --- Quote Start --- Error: Current module quartus_map ended unexpectedly --- Quote End --- Here is full log --- Quote Start --- Info: ******************************************************************* Info: Running Quartus II Analysis & Synthesis Info: Version 10.0 Build 262 08/18/2010 Service Pack 1 SJ Web Edition Info: Processing started: Tue Sep 21 18:00:11 2010 Info: Version 10.0 Build 262 08/18/2010 Service Pack 1 SJ Web Edition Info: Processing started: Tue Sep 21 18:00:11 2010 Info: Command: quartus_map --read_settings_files=on --write_settings_files=off my_and2 -c my_and2 Info: Found 2 design units, including 1 entities, in source file my_and2.vhd Info: Found design unit 1: my_and2-behav Info: Found entity 1: my_and2 Info: Found design unit 1: my_and2-behav Info: Found entity 1: my_and2 Info: Elaborating entity "my_and2" for the top level hierarchy Error: Current module quartus_map ended unexpectedly --- Quote End --- Do you have any suggestions how to fix this error?11 Replies
- Altera_Forum
Honored Contributor
Causes problems in Quartus 11 as well, when using SOPC_BUILDER or QSYS to add custom components. The error messages will complain about missing TOP_LEVEL_MODULE or multiple modules when actual quartus_map writes /etc/issue into the PLATFORM tag in a temporary xml file. When the next stage parses the xml to create the interface it barfs on the screen clear commands.
- Altera_Forum
Honored Contributor
Holy cow this bug just wasted a lot of my time, thank you so much for posting about it.
On Quartus 10.1 SP1, running quartus_map with special characters in /etc/issue will cause a segfault. Running quartus_map with an empty /etc/issue will cause quartus_map to run forever. I cannot fathom why an FPGA technology mapper needs to read the system's /etc/issue file. If you are trying to figure out our OS/distro, there are about 1,000 other sensible ways to do this. - Altera_Forum
Honored Contributor
Is it archLinux i686 ou x86_64 ? Mine is i686.
What is the stack trace ? How do you start Quartus ? Do you have installed libpng12 ? (I do not remember for which sofwares...) I use these sofware without any problem : matlab, modelsim, quartus xilinx ISE. I had more trouble with ISE... - Altera_Forum
Honored Contributor
Thanks for the answer, I did the echo... it was just that it didn't help, so I thought I haven't understood, or had missed something. It seems I have already solved it by adding release information to the file /etc/arch-release, which is void for kind of arch philosophical reasons, and I don't get why, but quartus seems to need it. Have you had any other problem with quartus so far?. I'm in my way to install modelsim and nios and I'm the only guy who went nuts and installed arch when everyone else uses fedora (tought I guess it'll pay in the end). Thanks!.
- Altera_Forum
Honored Contributor
Google translate is your friend (Do not work anymore because of the https...).
But to solve the problem, you just need to do the echo. The file /etc/issue contain special char to clear the screen at boot (not ascii) and Quartus can not handle it. Why Quartus need to read this file ? I don't know and it doesn't make sens for me... So the solution it's to remove special char into that file. You can do hexdump /etc/issue to see these specials char. You can save the file before if you want :
But anyway you just need to do as root this command :cp /etc/issue /etc/issue.back
Any way if you didn't understand this post too, I can't help you more (I am french)echo "Arch Linux \r (\n) (\l)" > /etc/issue - Altera_Forum
Honored Contributor
Hello, I have the same problem with archlinux, I've just installed it and need quartus for my HDL course. I didn't understand the last response in the post, and I've seen what seems to be the solution in a chinese page... and I don't know chinese!... could anybody give me hint?. Thanks in advance!.
- Altera_Forum
Honored Contributor
I found the solution of the problem :-P:)
The solution is there : wiki.archlinux org/index.php/Quartus_(简体中文) Just do
The problem is into this function : GEN_MACHINE_INFO::get_os_name Please fix this problem to allow special character into /etc/issue Thank youecho "Arch Linux \r (\n) (\l)" > /etc/issue - Altera_Forum
Honored Contributor
Hi,
I am on ArchLinux too (i686) and I have exactly the same problem. Friends of mine try on Ubuntu and didn't have any problem: To add more information, i have try to run quartus_map in command line/opt/elec/quartus/quartus/bin/quartus_map galileoCPLD -c galileoCPLD Info: ******************************************************************* Info: Running Quartus II Analysis & Synthesis Info: Version 10.0 Build 262 08/18/2010 Service Pack 1 SJ Web Edition . . . . Info: Implemented 571 device resources after synthesis - the final resource count might be different Info: Implemented 25 input pins Info: Implemented 52 output pins Info: Implemented 494 logic cells *** Fatal Error: Unhandled exception 0xade3: ERR_STACKWALKER::get_stack_trace(void const**, int, int, void*) + 0x8f (ccl_err) 0xd6f6: err_terminator() + 0x62 (ccl_err) 0x17a0e: std::terminate() + 0x1e (dinkum_alt) 0x2a6f3: _Dinkum_std::_String_base::_Xran() const + 0x1a3 (dinkum_alt) 0x3bbeb: _Dinkum_std::basic_string<char, _Dinkum_std::char_traits<char>, _Dinkum_std::allocator<char> >::assign(_Dinkum_std::basic_string<char, _Dinkum_std::char_traits<char>, _Dinkum_std::allocator<char> > const&, unsigned int, unsigned int) + 0x3b (ccl_gen) 0x32e96: GEN_MACHINE_INFO::get_os_name(_Dinkum_std::basic_string<char, _Dinkum_std::char_traits<char>, MEM_STL_ALLOCATOR<char> >*) + 0xbe6 (ccl_gen) 0x32350: qcu_report_operating_system(QCU_FRAMEWORK*) + 0x43c (comp_qcu) 0x664eb: qcu_add_common_panels(QCU_FRAMEWORK*, ACF_FILE_CATEGORY_ENUM*, ACF::REPORT_TYPES::TYPE*, bool, bool) + 0xd5 (comp_qcu) 0x26833: QSYN_FRAMEWORK::write_reports(bool, char const*) + 0x193 (quartus_map) 0xd45c: qexe_do_normal(QEXE_FRAMEWORK*, char const*) + 0x210 (comp_qexe) 0x17cfd: qexe_standard_main(QEXE_FRAMEWORK*, QEXE_OPTION_DEFINITION const**, int, char const**) + 0x437 (comp_qexe) 0x18b8b: qsyn_main(int, char const**) + 0x9b (quartus_map) 0x1ea58: msg_main_thread(void*) + 0x18 (ccl_msg) 0x57c8: thr_final_wrapper + 0xe (ccl_thr) 0x201c2: msg_thread_wrapper(void* (*)(void*), void*) + 0x72 (ccl_msg) 0x62570: mem_thread_wrapper(void* (*)(void*), void*) + 0xd0 (quartus_map) 0x9b20: err_thread_wrapper(void* (*)(void*), void*) + 0x2a (ccl_err) 0x57fb: thr_thread_wrapper + 0x2f (ccl_thr) 0x32cd1: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0x97 (ccl_msg) 0x131df: main + 0x4f (quartus_map) 0x16c76: __libc_start_main + 0xe6 (c.so.6) Exiting... Abandon - Altera_Forum
Honored Contributor
looks like you will need to install support for Stratix II devices even though you are not actually targeting that family (there are still some shared files in current releases). similar issues are covered in the Quartus II Release Notes
- Altera_Forum
Honored Contributor
I browsed project's directory and found another error log. It might be helpful
--- Quote Start --- <internal_error> <sub_system>ERR</sub_system> <callstack> 0xac657de3: ccl_err + 0xade3 (_ZN15ERR_STACKWALKER15get_stack_traceEPPKviiPv + 0x8f) 0xac65a6f6: ccl_err + 0xd6f6 (_Z14err_terminatorv + 0x62) 0xac5cca0e: dinkum_alt + 0x17a0e (_ZSt9terminatev + 0x1e) 0xab729c0a: stdc++.so.6 + 0xb4c0a 0xac5df6f3: dinkum_alt + 0x2a6f3 (_ZNK11_Dinkum_std12_String_base5_XranEv + 0x1a3) 0xac6e8beb: ccl_gen + 0x3bbeb (_ZN11_Dinkum_std12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE6assignERKS5_jj + 0x3b) 0xac6dfe96: ccl_gen + 0x32e96 (_ZN16GEN_MACHINE_INFO11get_os_nameEPN11_Dinkum_std12basic_stringIcNS0_11char_traitsIcEE17MEM_STL_ALLOCATORIcEEE + 0xbe6) 0xb365a350: comp_qcu + 0x32350 (_Z27qcu_report_operating_systemP13QCU_FRAMEWORK + 0x43c) 0xb368e4eb: comp_qcu + 0x664eb (_Z21qcu_add_common_panelsP13QCU_FRAMEWORKP22ACF_FILE_CATEGORY_ENUMPN3ACF12REPORT_TYPES4TYPEEbb + 0xd5) 0x806e833: quartus_map + 0x26833 (_ZN14QSYN_FRAMEWORK13write_reportsEbPKc + 0x193) 0xb360b45c: comp_qexe + 0xd45c (_Z14qexe_do_normalP14QEXE_FRAMEWORKPKc + 0x210) 0xb3615cfd: comp_qexe + 0x17cfd (_Z18qexe_standard_mainP14QEXE_FRAMEWORKPPK22QEXE_OPTION_DEFINITIONiPPKc + 0x437) 0x8060b8b: quartus_map + 0x18b8b (_Z9qsyn_mainiPPKc + 0x9b) 0xac8a6a58: ccl_msg + 0x1ea58 (_Z15msg_main_threadPv + 0x18) 0xac6167c8: ccl_thr + 0x57c8 (thr_final_wrapper + 0xe) 0xac8a81c2: ccl_msg + 0x201c2 (_Z18msg_thread_wrapperPFPvS_ES_ + 0x72) 0x80aa570: quartus_map + 0x62570 (_Z18mem_thread_wrapperPFPvS_ES_ + 0xd0) 0xac656b20: ccl_err + 0x9b20 (_Z18err_thread_wrapperPFPvS_ES_ + 0x2a) 0xac6167fb: ccl_thr + 0x57fb (thr_thread_wrapper + 0x2f) 0xac8bacd1: ccl_msg + 0x32cd1 (_Z12msg_exe_mainiPPKcPFiiS1_E + 0x97) 0x805b1df: quartus_map + 0x131df (main + 0x4f) 0xab50fc76: c.so.6 + 0x16c76 (__libc_start_main + 0xe6) 0x805aca1: quartus_map + 0x12ca1 </callstack> <error>*** Fatal Error: Unhandled Exception</error> <date>Tue Sep 21 20:14:45 2010 </date> <version>Version 10.0 Build 262 08/18/2010 Service Pack 1 SJ Web Edition</version> </internal_error> --- Quote End ---