- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When executing the "skew_report.tcl" script referenced in the FIFO Intel FPGA IP User Guide, we got this error message:
ERROR: Invalid name id for top level entity: 752582. Specify a valid top level entity id value. In Quartus Prime Pro, get_name_info query through integer value is only supported for "get_top_level_entity" TCL command. For other names query, please refer to "get_names" TCL command.
while executing
"get_name_info -info full_path $parent_id"
invoked from within
"set parent [get_name_info -info full_path $parent_id] "
invoked from within
"foreach_in_collection path [get_timing_paths -false_path -setup -detail summary -from $wrptr_regs -npaths $num_wrptrs] {
set src_reg_id [get_path_..."
(file "C:/Projects/pandora_iv_3d_fpga/skew_report.tcl" line 34)
invoked from within
"source "C:/Projects/pandora_iv_3d_fpga/skew_report.tcl""
("eval" body line 1)
invoked from within
"eval $tcl_command"
Is there a script for this compatible with Quartus Prime Pro? Or, does the DCFIFO now handle the false paths automatically with no need for user intervention?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Filip,
Looking into the skew_report.tcl
https://www.intel.com/content/dam/www/programmable/us/en/scripts/literature/ug/skew_report.tcl
Those command are written quite long ago which is 2010. On those days, we do not have pro edition of Quartus. Thus, a lot of tcl command had change when you use pro edition of Quartus.
For this document
https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/archives/ug-fifo-15.1.pdf
It is an old document for old Quartus usage:
You may need to refer to the below document:
https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug_fifo.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I understand that the script was written long time ago, when Quartus Pro did not exist yet. Is there however now a version of the script for Quartus Pro? What is the suggested solution to the DCFIFO constraining issue for Quartus Pro?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is an option when you open up the timing analyzer. Can you try to use the Report Skew under the custom reports?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That could work, but we would have to do this for every DCFIFO in our design separately. Is this assumption correct? We would obviously prefer to use some automated method and this is where the Quartus-Prime-Pro-compatible script would be handy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are correct. Unfortunately, we do not have the scripts developed yet for Quartus Pro. The reason that you are seeing the error is because some of the syntax had change for tcl when comparing with Pro vs Std.
I will request our internal engineer to look into this enhancement.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there any further question?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page