Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
The Intel sign-in experience is changing in February to support enhanced security controls. If you sign in, click here for more information.
15800 Discussions

Internal Error: Sub-system: QSYN, File: /quartus/synth/qsyn/qsyn_cmd.cpp, Line: 1803

Honored Contributor II

I am using opencl 16.1 and quartus 16.1 prime lite for the DE1 soc board. 


I try to compile the boardtest example in the de1soc examples. and got the following internal error. This may be an example independent issue. 

Any suggestion ? 






Info: Quartus Prime Analysis & Synthesis was successful. 0 errors, 119 warnings 

Info: Peak virtual memory: 1193 megabytes 

Info: Processing ended: Wed Jan 25 08:56:21 2017 

Info: Elapsed time: 00:03:22 

Info: Total CPU time (on all processors): 00:02:25 

Internal Error: Sub-system: QSYN, File: /quartus/synth/qsyn/qsyn_cmd.cpp, Line: 1803 

Stack Trace: 

0x17d8d: QSYN_FRAMEWORK::initialize_parallel_helper + 0x88d (quartus_map) 

0x13853: QSYN_FRAMEWORK::execute + 0x233 (quartus_map) 

0x11067: qexe_do_grunt + 0xa7 (comp_qexe) 

0x16063: qexe_run + 0x353 (comp_qexe) 

0x16e51: qexe_standard_main + 0xc1 (comp_qexe) 

0x1b06b: qsyn_main + 0x51b (quartus_map) 

0x13328: msg_main_thread + 0x18 (CCL_MSG) 

0x14b0e: msg_thread_wrapper + 0x6e (CCL_MSG) 

0x15b00: mem_thread_wrapper + 0x70 (ccl_mem) 

0x12a11: msg_exe_main + 0xa1 (CCL_MSG) 

0x29862: __tmainCRTStartup + 0x10e (quartus_map) 

0x8363: BaseThreadInitThunk + 0x13 (KERNEL32) 

0x670d0: RtlUserThreadStart + 0x20 (ntdll) 






Error (281039): Finished parallel synthesis of 1 partition(s). 1 partitions did not finish parallel synthesis because there were errors 

Error (281040): Partition "system_acl_iface_hps_hps_io_border:border" did not complete synthesis due to errors
0 Kudos
10 Replies
Honored Contributor II

Are you using 16.1 or 16.1.1? 16.1 has a known issue with OpenCL compilation and all OpenCL compilations fail. You must install the 16.1.1 update for both Quartus and AOCL if you haven't.

Honored Contributor II

Hello dears,I am encountering the same errors, did you mange to solve this issue?I am using Quartus 17.1 and OpenCL SDK for FPGA 17.1


Hello all,


I am also facing the similar error when I tried to run a basic AND gate program in Quartus 17.1, the tool keep crashing.



Problem Details
Internal Error: Sub-system: DCALC, File: /quartus/ddb/dcalc/dcalc_bcm_modules_cache.cpp, Line: 110

Could not load pdb file - c:/intelfpga_pro/17.1/quartus/common/devinfo/cyclone10gx/ddb_cyclone10gx_io_48_lvds_tile_hps-ss-2p5-100-hs_model

Stack Trace:

    0x5d3a3: DCALC_TIMING_MODULES_CACHE::get_model + 0x21d4f (ddb_dcalc)

    0x2f2cb: DCALC_TIMING_NETLIST_MANAGER_IMPL::load_model + 0x43 (ddb_dcalc)

    0x41631: <lambda_27927aa62a013f38f2f5db62a47234ba>::operator() + 0x71 (ddb_dcalc)

    0x2f919: DCALC_TIMING_NETLIST_MANAGER_IMPL::load_corners + 0x49 (ddb_dcalc)

    0x2f132: DCALC_TIMING_NETLIST_MANAGER_IMPL::load_timing_corner + 0x4a (ddb_dcalc)

    0x30028: DCALC_TIMING_NETLIST_MANAGER::load_timing_corner + 0x14 (ddb_dcalc)

    0x4d460: PTI_PHYSICAL_TIMING_API::lazy_load_netlist_type + 0xb8 (tsm_pti)

    0x48035: tbb::internal::do_iteration_task_iter<QTL_HASH_SET_LITE_ITERATOR<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,QTL_OPS<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >,tbb::internal::parallel_for_each_body<<lambda_0f378206216e20c5c02cec778cb5f832>,QTL_HASH_SET_LITE_ITERATOR<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,QTL_OPS<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > >,std::basic_string<char,std::char_traits<char>,std::allocator<char> > >::execute + 0x1d (tsm_pti)

    0x1c1f3: tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all + 0x193 (tbb) at d:\sj\nightly\17.1\240\w64\acds\quartus\extlibs64\tbb\tbb42_20131118oss_altera\src\tbb\custom_scheduler.h:472

    0x19afe: tbb::internal::arena::process + 0x18e (tbb) at d:\sj\nightly\17.1\240\w64\acds\quartus\extlibs64\tbb\tbb42_20131118oss_altera\src\tbb\arena.cpp:105

    0x16867: tbb::internal::market::process + 0xf7 (tbb) at d:\sj\nightly\17.1\240\w64\acds\quartus\extlibs64\tbb\tbb42_20131118oss_altera\src\tbb\market.cpp:479

    0x10eac: tbb::internal::rml::private_worker::run + 0x6c (tbb) at d:\sj\nightly\17.1\240\w64\acds\quartus\extlibs64\tbb\tbb42_20131118oss_altera\src\tbb\private_server.cpp:283

    0x1111a: tbb::internal::rml::private_worker::thread_routine + 0x5a (tbb) at d:\sj\nightly\17.1\240\w64\acds\quartus\extlibs64\tbb\tbb42_20131118oss_altera\src\tbb\private_server.cpp:240

    0x24f7e: _beginthreadex + 0x106 (MSVCR120)

    0x25125: _endthreadex + 0x191 (MSVCR120)

    0x17033: BaseThreadInitThunk + 0x13 (KERNEL32)

    0x526a0: RtlUserThreadStart + 0x20 (ntdll)



Executable: quartus_fit

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

Quartus Prime Information
Address bits: 64
Version: 17.1.0
Build: 240
Edition: Pro Edition



Honored Contributor II

Attach your quartus_sh_compile.log.

Honored Contributor II


--- Quote Start ---  

Attach your quartus_sh_compile.log. 

--- Quote End ---  



the log is in the attachments "quartus_sh_compile.log". 


many thanks in advance.
Honored Contributor II

Compilation seems to be crashing with an internal error; however, the following line in your log seems strange to me: 


Info (125068): Revision "top" was previously opened in Quartus II software version 14.1. Created Quartus Prime Default Settings File 


What is your target board? Is your BSP compatible with the version of Quartus you are using? 


Also, have you tried updating to 17.1.2 (you have to update Quartus and AOC separately)? 


Finally, if you have a license for Quartus, it is proffered to use Quartus Prime Standard or Pro, depending on your target board.
Honored Contributor II

I am trying with c5soc as the target board, since the BSP was installed by default ( I tried on de0_nano_soc after I got the BSP from terasic but the same problem occured). 


Since the BSP was already included in the SDK I assumed it's compatible with Quartus & SDK version 17.1. 


For the license, I don't have one, since as I understood that the Quartus Lite is free and the SDK didn't ask for a license ( I am targeting Cyclone V board (DE0-Nano SoC)). 


However, Now I am updating Quartus and SDK, I will test again and post the log.
Honored Contributor II

Hello HRZ, 


I updated both AOC and Quartus to 17.1.1 (latest version on website), 


I performed the following : 


1- trying to compile for board c5soc resulted with the log in the "quartus_sh_compile_c5soc" file in the attachments (same errors). 

2- trying to compile for board de0_nano_soc (using the BSP in the following link: ( resulted with different error message (less errors and more progress) as shown in the "quartus_sh_compile_de0_nano" log. 


By comparing, the de0_nano progressed more but the error (Error in adjust_plls.tcl!) crashed the whole thing as I understand. 


Appreciate your kind help and advice and many thanks for your help.
Honored Contributor II

If you are using the reference BSPs, then they are compatible with the version of Quartus they are shipped with. I hope updating Quartus solves your problem. 


P.S. How much memory do you have on the machine you use for compilation?
Honored Contributor II


--- Quote Start ---  

P.S : Regarding the memory used for compilation, my PC has 4 GB RAM and I'm using it all, it's enough isn't it ? 

--- Quote End ---  



Actually, this is very likely the source of your problem. Considering the fact that the compilation process is crashing in a different part every time, you are very likely running out of memory. Intel's recommendation for memory size to place and route designs for Cyclone V is 6-8 GB (and probably more if you are using OpenCL): 


You can easily verify whether you are running out of memory or not by checking your memory and swap usage during placement and routing. I recommend using a machine with at least 8 GB of memory (or preferably, 16).