Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
16612 Discussions

Qsys-script FAILED

Altera_Forum
Honored Contributor II
‎08-19-2013 10:14 AM
2,602 Views

Hi all, 

Finally moved to sdk ver 13 but bumped into another issue. 

aoc fails with the following message: 

... 

Error: Qsys-script FAILED 

See all.log for details. 

 

all.log shows the following (single) error message: 

... 

...... Error: add_connection acl_iface.kernel_irq all_system.kernel_irq: No interface named acl_iface.kernel_irq. 

... 

 

Any suggestions? 

Thanks.
0 Kudos

Link Copied

7 Replies
Altera_Forum
Honored Contributor II
‎08-19-2013 04:46 PM
1,113 Views

At 13.0 the tools changed quite a bit so I recommend going through the getting started guide again. The first thing to check is that the environment variables point at the 13.0 tools and that you have Stratix V device support installed. 

 

Also in 13.0 you use 'aoc.exe' to compile the kernels now, acl is depricated.
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎08-22-2013 08:06 AM
1,113 Views

 

--- Quote Start ---  

At 13.0 the tools changed quite a bit so I recommend going through the getting started guide again. The first thing to check is that the environment variables point at the 13.0 tools and that you have Stratix V device support installed. 

 

Also in 13.0 you use 'aoc.exe' to compile the kernels now, acl is depricated. 

--- Quote End ---  

 

 

I can get the .aoco file without any problems using -c flag. 

error occurs during the second phase of the compilation. 

I do not get any errors/warnings about path variables or device files.
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎08-23-2013 07:15 PM
1,113 Views

Sounds like integrating the kernel hardware into the rest of the system is failing. Is your compilation machine set to the Turkish language? It could be a localization problem. 

 

If you are compiling for the Nallatech A7 board try running "aocl install". Also when you run into that error try opening system.qsys, that file should be located in the directory named after your kernel. Assuming Qsys isn't in your path you should be able to open the system like this: <path of your Quartus installation>\sopc_builder\bin\qsys-edit system.qsys If you take a screen shot of that system and attach it here then I can take a look to see if I spot anything out of the ordinary. It should be comprised of three cores, a little clock/reset block, the kernel block, and a big blob of logic that represents the PCIe, SDRAMs, etc...
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎09-03-2013 08:15 AM
1,112 Views

Hi BadOmen, 

First off my apologies. You were right. This was caused by machine locality/language settings. 

I switched everything to English as a last attempt. Should have tried this first. 

Error is gone and I am monitoring the compilation to see if all goes well. 

Thanks for your suggestion.
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎09-04-2013 06:55 PM
1,113 Views

We are currently trying to track these language issues. Are you using Windows or Linux to compile on?

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎09-11-2013 06:13 AM
1,113 Views

 

--- Quote Start ---  

We are currently trying to track does these language issues. Are you using Windows or Linux to compile on? 

--- Quote End ---  

 

Windows 7 / 64
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎06-02-2015 08:29 AM
1,112 Views

Hi all,First of all, sorry for my poor english.I am working on c5soc but I would like to compile hello_world kernel. I am on windows 7 64.When I invoke : aoc --board c5soc device/hello_world.cl -o bin/hello_world.aocxI get an error which is : Error qsys-script failed. Before this, I have :aoc: Environment checks are completed successfully.You are now compiling the full flow!!aoc: Selected target board c5socaoc: Running OpenCL parser....aoc: OpenCL parser completed successfully.aoc: Compiling....aoc: Linking with IP library ...aoc: First stage compilation completed successfully.aoc: Setting up project for QXP preservation flow....The errors are reported in hello_world.log :System name: hello_worldPlacing kernel hello_world at address 0x02015.06.02.09:51:12 Info: Doing: qsys-script --script=system.tcl --xmx512m --xx:+useserialgc --system-file=system.qsysInternal Error: Sub-system: DYGR, File: /quartus/ddb/dygr/dygr_fitter_delay_info_drl_interface.cpp, Line: 299Cannot load library ddb_dygr_fdi.dll: La procédure spécifiée est introuvable.Stack Trace: 0x39dd2: DYGR_ROUTE_TIMING_INFO::get_timing_node + 0x94a2 (DDB_DYGR) 0x20ad8: dygr_fdi_drl_call_mem_new + 0x8 (DDB_DYGR) 0x209ef: DYGR_DIE_INFO_BODY::DYGR_DIE_INFO_BODY + 0x1bf (DDB_DYGR) 0x207b5: dygr_create_die_info + 0x55 (DDB_DYGR) 0xe6a3: dmgr_create_device_for_pintable_update + 0xcc53 (DDB_DMGR) 0x10240: dmgr_create_device_for_pintable_update + 0xe7f0 (DDB_DMGR) 0x1171f: dmgr_create_device_for_pintable_update + 0xfccf (DDB_DMGR) 0x11bf3: dmgr_create_device_for_pintable_update + 0x101a3 (DDB_DMGR) 0x189e: DMGR_UTILITY::create_device + 0x6e (DDB_DMGR) 0xd202: pll_get_reference_clock_frequency_range + 0xaa2 (qcl_pll) 0xd5f7: generic_pll_parse_tcl_data + 0xd7 (qcl_pll) 0x112a8: Tcl_ListMathFuncs + 0x5a8 (tcl85) 0x56917: Tcl_ExprObj + 0x1837 (tcl85) 0xa2376: TclObjInterpProcCore + 0x76 (tcl85) 0x112a8: Tcl_ListMathFuncs + 0x5a8 (tcl85) 0x56917: Tcl_ExprObj + 0x1837 (tcl85) 0xa2376: TclObjInterpProcCore + 0x76 (tcl85) 0x112a8: Tcl_ListMathFuncs + 0x5a8 (tcl85) 0x121b5: Tcl_EvalEx + 0x8f5 (tcl85) 0x129b9: Tcl_Eval + 0x29 (tcl85) 0x1a47: Java_com_altera_tcl_interpreter_NativeTclWrapper_eval0 + 0x67 (tcl_jni_bridge)End-traceInternal Error: Sub-system: DMGR, File: /quartus/ddb/dmgr/dmgr_utility_body.cpp, Line: 2932ref_count >= 0Stack Trace: 0x113b5: dmgr_create_device_for_pintable_update + 0xf965 (DDB_DMGR) 0x114b3: dmgr_create_device_for_pintable_update + 0xfa63 (DDB_DMGR) 0x128bf: dmgr_create_device_for_pintable_update + 0x10e6f (DDB_DMGR) 0x13fde: dmgr_create_device_for_pintable_update + 0x1258e (DDB_DMGR) 0x14228: dmgr_create_device_for_pintable_update + 0x127d8 (DDB_DMGR) 0x23ab0: LdrShutdownProcess + 0x1d0 (ntdll) 0x238bf: RtlExitUserProcess + 0x8f (ntdll) 0x20ccc: _get_pgmptr + 0x248 (MSVCR100) 0x1dac: err_ie_abort_or_exit + 0x1c (CCL_ERR) 0x33407: MSG_INTERNAL_ERROR::update_comment_and_send_crash_report + 0x2f57 (CCL_MSG) 0x334e2: MSG_INTERNAL_ERROR::report + 0xd2 (CCL_MSG) 0x39dd2: DYGR_ROUTE_TIMING_INFO::get_timing_node + 0x94a2 (DDB_DYGR) 0x20ad8: dygr_fdi_drl_call_mem_new + 0x8 (DDB_DYGR) 0x209ef: DYGR_DIE_INFO_BODY::DYGR_DIE_INFO_BODY + 0x1bf (DDB_DYGR) 0x207b5: dygr_create_die_info + 0x55 (DDB_DYGR) 0xe6a3: dmgr_create_device_for_pintable_update + 0xcc53 (DDB_DMGR) 0x10240: dmgr_create_device_for_pintable_update + 0xe7f0 (DDB_DMGR) 0x1171f: dmgr_create_device_for_pintable_update + 0xfccf (DDB_DMGR) 0x11bf3: dmgr_create_device_for_pintable_update + 0x101a3 (DDB_DMGR) 0x189e: DMGR_UTILITY::create_device + 0x6e (DDB_DMGR) 0xd202: pll_get_reference_clock_frequency_range + 0xaa2 (qcl_pll) 0xd5f7: generic_pll_parse_tcl_data + 0xd7 (qcl_pll) 0x112a8: Tcl_ListMathFuncs + 0x5a8 (tcl85) 0x56917: Tcl_ExprObj + 0x1837 (tcl85) 0xa2376: TclObjInterpProcCore + 0x76 (tcl85) 0x112a8: Tcl_ListMathFuncs + 0x5a8 (tcl85) 0x56917: Tcl_ExprObj + 0x1837 (tcl85) 0xa2376: TclObjInterpProcCore + 0x76 (tcl85) 0x112a8: Tcl_ListMathFuncs + 0x5a8 (tcl85) 0x121b5: Tcl_EvalEx + 0x8f5 (tcl85) 0x129b9: Tcl_Eval + 0x29 (tcl85) 0x1a47: Java_com_altera_tcl_interpreter_NativeTclWrapper_eval0 + 0x67 (tcl_jni_bridge)End-traceThanks for your help

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.