为什么NGDbuild的选项不能工作？（ISE 11.4）

我最初的想法是TNM约束是O.K.
但在其他地方你
在另一个约束中使用该组，例如“FROM：TO”或“PERIOD”。
现在看到了
它看起来像错误消息-aut不适用于TNM，也许它只适用于
TNM_NET。
坦率地说，我从未理解为什么约束文件中的不匹配项应该创建
错误而不是警告。
在Lattice工具链中有一个“忽略错误”的毯子
允许您根据可能的约束构建设计的选项
识别并仅为那些不能识别的人创建警告。
在旧版本的ISE中，-aul（允许不匹配的LOC）不会创建
如果与LOC约束在同一行上存在其他约束，则会出错：
NET“foo”LOC =“AC4”|
IOSTANDARD = LVCMOS25 |
拉起 ;
在新的ISE版本中，-aul仅防止LOC的LOC部分出错
然后，行给出IOSTANDARD约束的错误。
有的东西
在较新版本的ISE中添加的是能够包含多个.ucf文件
在设计中。
不幸的是，在他们移除这种能力的某个地方
选择.ucf附加到哪个模块。
所以你仍然需要使用顶部
级别项目管理，以包含您希望用于特定构建的.ucf文件。
也许Xilinx的某个人会听这个......
问候，
的Gabor
-  Gabor
在原帖中查看解决方案



以下为原文

My original thought was that the TNM constraint was O.K. but somewhere else you
used the group in another constraint like "FROM : TO" or "PERIOD".  Now seeing
the error messages it looks like -aut does not work for TNM, perhaps it only works for
TNM_NET.
 
Quite frankly, I never understood why unmatched items in the constraint file should create
errors rather than warnings.  In the Lattice tool chain there is a blanket "ignore errors"
option that allows you to build the design based on the constraints that can be
identified and only create warnings for those that can't.
 
In the older versions of ISE the -aul (allow unmatched LOC) would not create an
error if there were other constraints on the same line as the LOC constraint like:
 
NET "foo"  LOC = "AC4" | IOSTANDARD = LVCMOS25 | PULLUP ;
 
In the new ISE versions, -aul only prevents an error on the LOC portion of the
line then gives an error on the IOSTANDARD constraint.  Something that has
been added in newer versions of ISE is the ability to include multiple .ucf files
in a design.  Unfortunately somewhere along the way they removed the ability
to select which module the .ucf attaches to.  So you still need to use the top
level project management to include the .ucf files you want for a particular build.
 
Maybe someone at Xilinx will listen to this...
 
Regards,
Gabor
-- GaborView solution in original post

你能发布你得到的错误信息吗？
它是指您帖子中的TNM约束吗？
或者在那里
使用获取错误的组的时间约束？
一世
认为-aut只能防止产生错误
计时组仍然留有一些元素。
问候，
的Gabor
-  Gabor



以下为原文

Can you post the error message you get?
 
Is it referring to the TNM constraint in your post?  Or is there
a timing constraint using the group that gets the error?  I
think that -aut only prevents errors when the resulting
timing group still has some elements left in it.
 
regards,
Gabor
-- Gabor

你是说“-aut”选项不支持“TNM”组约束？
-------------------------------这是来自错误信息-------------
-----------------
错误：约束系统：58-约束[sec_subl.ucf（4）]：INST“ccm_en_u / data_cnt_ *”TNM =“cnt_grp”;
与任何设计对象都不匹配。



以下为原文

Do you mean that the " -aut"  option  not  support the  "TNM" group constraint ?
 
-------------------------------
This is from the Error Message
------------------------------
ERROR:constraint system:58-constraint [sec_subl.ucf(4)]: INST "ccm_en_u/data_cnt_*" TNM = "cnt_grp"; does not match any design objects.

我最初的想法是TNM约束是O.K.
但在其他地方你
在另一个约束中使用该组，例如“FROM：TO”或“PERIOD”。
现在看到了
它看起来像错误消息-aut不适用于TNM，也许它只适用于
TNM_NET。
坦率地说，我从未理解为什么约束文件中的不匹配项应该创建
错误而不是警告。
在Lattice工具链中有一个“忽略错误”的毯子
允许您根据可能的约束构建设计的选项
识别并仅为那些不能识别的人创建警告。
在旧版本的ISE中，-aul（允许不匹配的LOC）不会创建
如果与LOC约束在同一行上存在其他约束，则会出错：
NET“foo”LOC =“AC4”|
IOSTANDARD = LVCMOS25 |
拉起 ;
在新的ISE版本中，-aul仅防止LOC的LOC部分出错
然后，行给出IOSTANDARD约束的错误。
有的东西
在较新版本的ISE中添加的是能够包含多个.ucf文件
在设计中。
不幸的是，在他们移除这种能力的某个地方
选择.ucf附加到哪个模块。
所以你仍然需要使用顶部
级别项目管理，以包含您希望用于特定构建的.ucf文件。
也许Xilinx的某个人会听这个......
问候，
的Gabor
-  Gabor



以下为原文

My original thought was that the TNM constraint was O.K. but somewhere else you
used the group in another constraint like "FROM : TO" or "PERIOD".  Now seeing
the error messages it looks like -aut does not work for TNM, perhaps it only works for
TNM_NET.
 
Quite frankly, I never understood why unmatched items in the constraint file should create
errors rather than warnings.  In the Lattice tool chain there is a blanket "ignore errors"
option that allows you to build the design based on the constraints that can be
identified and only create warnings for those that can't.
 
In the older versions of ISE the -aul (allow unmatched LOC) would not create an
error if there were other constraints on the same line as the LOC constraint like:
 
NET "foo"  LOC = "AC4" | IOSTANDARD = LVCMOS25 | PULLUP ;
 
In the new ISE versions, -aul only prevents an error on the LOC portion of the
line then gives an error on the IOSTANDARD constraint.  Something that has
been added in newer versions of ISE is the ability to include multiple .ucf files
in a design.  Unfortunately somewhere along the way they removed the ability
to select which module the .ucf attaches to.  So you still need to use the top
level project management to include the .ucf files you want for a particular build.
 
Maybe someone at Xilinx will listen to this...
 
Regards,
Gabor
-- Gabor

谢谢
我在另一个约束中使用了该组，例如“FROM：TO”。



以下为原文

thanks
 I used the group in another constraint like "FROM : TO" .