Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
Intel Support hours are Monday-Fridays, 8am-5pm PST, except Holidays. Thanks to our community members who provide support during our down time or before we get to your questions. We appreciate you!

Need Forum Guidance? Click here
Search our FPGA Knowledge Articles here.
15462 Discussions

qsys-script: invalid command name

fogl
Novice
1,079 Views

Hello everybody,

 

I would like to run the .tcl script i exported from GUI wizard to generate the design without the GUI.

 

I wrote a .tcl script which includes the line:

qsys-script --script=internal_osc.tcl --package-version=16.0

 

When i run my script, i gen an error:

invalid command name "qsys-script"

   while executing

"unknown_original qsys-script --script=internal_osc.tcl --..."

   ("eval" body line 1)

   invoked from within

"eval unknown_original $cmd $args"

   (procedure "::unknown" line 7)

   invoked from within

"qsys-script --script=internal_osc.tcl --package-version=16.0"

   (file "synthProject.tcl" line 12)

 

I noticed a thread with a similar problem (https://forums.intel.com/s/question/0D50P00003yyOXWSA2/qsysscript-problems ), but additional package-version parameter doesn't solve my problem. Does anybody have an idea what is the problem with my script.

 

Regards

Klemen

0 Kudos
10 Replies
sstrell
Honored Contributor III
882 Views

Do you have a package require line at the top of internal_osc.tcl as mentioned in the user guide:

 

https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug-qpp-platform-designer...

 

#iwork4intel

fogl
Novice
882 Views

Yes i have. This file was generated by quartus.

Regards

 

 

internal_osc.tcl

--------------------

 

# qsys scripting (.tcl) file for internal_osc

package require -exact qsys 16.0

 

create_system {internal_osc}

 

set_project_property DEVICE_FAMILY {MAX 10}

set_project_property DEVICE {10M02SCU169C8G}

set_project_property HIDE_FROM_IP_CATALOG {true}

 

# Instances and instance parameters

# (disabled instances are intentionally culled)

add_instance int_osc_0 altera_int_osc 19.1

set_instance_parameter_value int_osc_0 {CBX_AUTO_BLACKBOX} {ALL}

set_instance_parameter_value int_osc_0 {CLOCK_FREQUENCY_1} {116}

set_instance_parameter_value int_osc_0 {CLOCK_FREQUENCY_2} {77}

 

# exported interfaces

set_instance_property int_osc_0 AUTO_EXPORT {true}

 

# interconnect requirements

set_interconnect_requirement {$system} {qsys_mm.clockCrossingAdapter} {HANDSHAKE}

set_interconnect_requirement {$system} {qsys_mm.enableEccProtection} {FALSE}

set_interconnect_requirement {$system} {qsys_mm.insertDefaultSlave} {FALSE}

set_interconnect_requirement {$system} {qsys_mm.maxAdditionalLatency} {1}

 

save_system {internal_osc.qsys}

 

fogl
Novice
882 Views

And the .tcl script i run:

 

package require ::quartus::project

qsys-script --script=internal_osc.tcl --package-version=16.0

RichardTanSY_Intel
882 Views

Do you execute the script in the command shell?

I am able to run your script though and get warning messages instead of an error.

fogl
Novice
882 Views

Yes, i run the script in shell.

I am using linux - Ubuntu 18.04.1 LTS.

RichardTanSY_Intel
882 Views

Have you tried to execute the command in the Nios II command shell?

fogl
Novice
882 Views

I was not aware this is possible. What is the command to run the .tcl script in nios II?

 

I found the intelFPGA_lite/19.1/nios2eds/nios2_command_shell.sh, if i run it it returns this:

------------------------------------------------

Altera Nios2 Command Shell

 

Version 19.1, Build 670

------------------------------------------------

 

I was experimenting with options acording to exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...] but no luck.

Regards

 

 

 

RichardTanSY_Intel
882 Views

You can run again your tcl script:

qsys-script --script=internal_osc.tcl --package-version=16.0

fogl
Novice
882 Views

I was able to execute this command and it seems this solved the problem, Thank you for your help :)

Regards

RichardTanSY_Intel
881 Views

I am glad that the issue solved. ;)

Reply