AR# 24489

9.1i ISE - Associating a UCF file with a lower-level module error: "ERROR:ProjectMgmt - TOE: ITclInterp::ExecuteCmd gave Tcl result 'invalid command name "0""


Keywords: association, constraints, top

If the lower-level module has never been set as top, creating and associating a new User Constraints File (UCF) to it causes the following error message:

"ERROR:ProjectMgmt - TOE: ITclInterp::ExecuteCmd gave Tcl result 'invalid command name "0"'.
Tcl_ErrnoId: ENOENT
Tcl_ErrnoMsg: no such file or directory
_cmd: ::xilinx::Dpm::dpm_chCreateNewSource $piThisInterface
errorInfo: invalid command name "0"
while executing "$_obj GetInterface $id"
(procedure "_GetInterface" line 13) invoked from within "_GetInterface $_IView IPropertyInstanceSet"
(procedure "_GetViewProperty" line 8)
invoked from within "_GetViewProperty $_iView "PROP_TopDesignUnit" _TopDUName" (procedure "::xilinx::Dpm::dpm_chCreateNewSource" line 79)
invoked from within "::xilinx::Dpm::dpm_chCreateNewSource $piThisInterface""

The constraints file is not created or added to the project.


In ISE 9.1i, UCF files can only be associated with the top module. Project Navigator should not allow user to associate a UCF file to any module but the Top Level module.

This problem has been fixed in the latest 9.1i Service Pack available at:
The first service pack containing the fix is 9.1i Service Pack 1.
AR# 24489
日期 04/17/2009
状态 Archive
Type 综合文章