包装错误2908是关于什么的？

消除过程的好抓！
看起来
IOSTANDARD = LVDS_25;
// *不好。
IOSTANDARD = LVDS25;
// 好
如果PlanAhead生成了错误的.UCF文件语法，则表示您应该报告的错误（请打开Webcase）。
目前尚不清楚该错误是出现在PlanAhead中是为了生成错误的语法，还是在ISE中的某个其他地方出现不一致的约束形式处理，或两者兼而有之。
如果您错误地手动指定了IOSTANDARD，那么问题就解决了。
在任何一种情况下，请将此主题标记为“已解决”，并接受我们的谢意，以便发现并记录它。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。
在原帖中查看解决方案



以下为原文

Good catch by process of elimination!
 
It seems that
IOSTANDARD = LVDS_25;  // *NOT* OK.
IOSTANDARD = LVDS25;   // OK
 
If PlanAhead generated the incorrect .UCF file syntax, this represents a bug that you should report (by opening a webcase, please).  It's not clear whether the bug is in PlanAhead for generating incorrect syntax, or somewhere else in ISE for inconsistent handling of a constraint form, or both.
 
If you manually specified the IOSTANDARD incorrectly, then your problem is solved.
 
In either case, please mark this thread as "SOLVED", and accept our thanks for uncovering and documenting it.
 
- Bob Elkind
SIGNATURE:
README for newbies is here: http://forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369

Summary:
1. Read the manual or user guide.  Have you read the manual? Can you find the manual?
2. Search the forums (and search the web) for similar topics.
3. Do not post the same question on multiple forums.
4. Do not post a new topic or question on someone else's thread, start a new thread!
5. Students: Copying code is not the same as learning to design.
6 "It does not work" is not a question which can be answered. Provide useful details (with webpage, datasheet links, please).
7. You are not charged extra fees for comments in your code.
8. I am not paid for forum posts.  If I write a good post, then I have been good for nothing.View solution in original post

是13.1 64位



以下为原文

ise 13.1 64 bit

错误是I / O组件“io_p”具有非法的IOSTANARD值LVDS_25。
我看vhd缓冲区的ibfudsgeneric地图（iostandard =>“LVDS_25”，IFD_DELAY_VALUE =>“0”，DIFF_TERM => TRUE）



以下为原文

the error is I/O component "io_p" has illegal IOSTANARD value LVDS_25.  i look the vhd buffer its  

ibfuds
generic map(
iostandard => "LVDS_25",
IFD_DELAY_VALUE => "0",
DIFF_TERM => TRUE)

错误是I / O组件“io_p”具有非法的IOSTANARD值LVDS_25
在同一个IO银行中使用了哪些其他IOSTANDARD？
该信号所在的IO bank的VCCO是什么？
这个信号是差分对的一半吗？
LVDS用于差分信号，而不是单端信号。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

the error is I/O component "io_p" has illegal IOSTANARD value LVDS_25
 
what other IOSTANDARDs are in use in the same IO bank?
What is VCCO for the IO bank in which this signal is located?
Is this signal half of a diff pair?  LVDS is for differential signals, not single-ended signals.
 
-- Bob Elkind
SIGNATURE:
README for newbies is here: http://forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369

Summary:
1. Read the manual or user guide.  Have you read the manual? Can you find the manual?
2. Search the forums (and search the web) for similar topics.
3. Do not post the same question on multiple forums.
4. Do not post a new topic or question on someone else's thread, start a new thread!
5. Students: Copying code is not the same as learning to design.
6 "It does not work" is not a question which can be answered. Provide useful details (with webpage, datasheet links, please).
7. You are not charged extra fees for comments in your code.
8. I am not paid for forum posts.  If I write a good post, then I have been good for nothing.

错误发生在virtex 5 sx240t部分的第11行。
LVDS对在vhdl中使用ibufds进行了实现，在UCF中我也为该对编写了约束
... iostandard = lvds_25 |
differ_term = true;
第11行中的所有其他对都是lvds_25，并且这对没有任何问题。
我不认为逻辑也是优化的。
它之前没有这个问题但是现在..



以下为原文

the error is at bank 11 in virtex 5 sx240t part. 
 
the LVDS pair was instiantiate with ibufds in vhdl, in the UCF i also wrote constraint for that pair
 
... iostandard = lvds_25 | differ_term = true;
 
all other pairs in bank 11 are lvds_25 and don't have any problems just this pair. 
i don't think the logic is optimize out either.
 
it doesn't has this issues before but now..
 

第11行中的所有其他对都是lvds_25，并且这对没有任何问题。
Bank 11 LVDS_25是对输入，输出还是两者兼而有之？
这对的.UCF条目是什么（两个引脚都是）？
... iostandard = lvds_25 |
differ_term = true;
上面的行中存在语法错误。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

all other pairs in bank 11 are lvds_25 and don't have any problems just this pair.
 
Are the Bank 11 LVDS_25 pairs inputs, outputs, or a mix of both?
What are the .UCF entries for this pair (both pins of the pair)?
 
... iostandard = lvds_25 | differ_term = true;
 
There is a syntax error in the above line.
 
-- Bob Elkind
SIGNATURE:
README for newbies is here: http://forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369

Summary:
1. Read the manual or user guide.  Have you read the manual? Can you find the manual?
2. Search the forums (and search the web) for similar topics.
3. Do not post the same question on multiple forums.
4. Do not post a new topic or question on someone else's thread, start a new thread!
5. Students: Copying code is not the same as learning to design.
6 "It does not work" is not a question which can be answered. Provide useful details (with webpage, datasheet links, please).
7. You are not charged extra fees for comments in your code.
8. I am not paid for forum posts.  If I write a good post, then I have been good for nothing.

您也引用了哪种语法错误？
bank 11是输入和输出lvds的混合，仅有1个输出对。
是的，忘记了它的diff_term，是的，在ucf中它的语法正确。
关于那个



以下为原文

which syntax error are you refer too?
 
bank 11 is mix of input and output lvds, althouth only 1 output pair. 
 
yea forgot its diff_term, yeah in the ucf its in correct syntax.  sry about that

这是在银行11上的post-syn引脚。红色的一个亮点是错误。



以下为原文

this is pins post-syn on bank 11.  the one highlight in red is the error.

建议：
从.UCF（和PlanAhead）中删除对此输入差异对的所有引用和赋值。
让ISE弄清楚如何处理这两个引脚。
检查后PAR总结以查看ISE是否做了正确的事情（例如，没有修剪，被视为差异对）。
使用此输入对使ISE“满意”后，将所需的约束添加回来...一次一个。
查看哪些约束（或约束组合）会引发错误消息。
使用反复试验，消除过程追逐这一点。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

Suggestion:
 
Remove all references and assignments to this input diff pair from the .UCF (and PlanAhead).  Let ISE figure out what to do with these two pins.  Check the post PAR summary to see if ISE 'did the right thing" (e.g. no trimming, treated as diff pair).
 
After you make ISE 'happy' with this input pair, add the desired constraints back in... one at a time.  See which constraints (or combination of constraints) provokes error messages.  Use trial-and-error, process of elimination to chase this down.
 
-- Bob Elkind
SIGNATURE:
README for newbies is here: http://forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369

Summary:
1. Read the manual or user guide.  Have you read the manual? Can you find the manual?
2. Search the forums (and search the web) for similar topics.
3. Do not post the same question on multiple forums.
4. Do not post a new topic or question on someone else's thread, start a new thread!
5. Students: Copying code is not the same as learning to design.
6 "It does not work" is not a question which can be answered. Provide useful details (with webpage, datasheet links, please).
7. You are not charged extra fees for comments in your code.
8. I am not paid for forum posts.  If I write a good post, then I have been good for nothing.

好吧看起来像IOSTANDARD = LVDS_25;
在.ucf导致此错误，一旦它注释掉，它运行正常并自动设置为lvds25。
不确定为什么因为所有其他对具有相同的约束语法。



以下为原文

ok look like
IOSTANDARD = LVDS_25;  in .ucf is causing this error, once its comment it out, it runs fine and sets to lvds25 automatically.  not sure why since all the other pairs has same constraint syntax.

消除过程的好抓！
看起来
IOSTANDARD = LVDS_25;
// *不好。
IOSTANDARD = LVDS25;
// 好
如果PlanAhead生成了错误的.UCF文件语法，则表示您应该报告的错误（请打开Webcase）。
目前尚不清楚该错误是出现在PlanAhead中是为了生成错误的语法，还是在ISE中的某个其他地方出现不一致的约束形式处理，或两者兼而有之。
如果您错误地手动指定了IOSTANDARD，那么问题就解决了。
在任何一种情况下，请将此主题标记为“已解决”，并接受我们的谢意，以便发现并记录它。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

Good catch by process of elimination!
 
It seems that
IOSTANDARD = LVDS_25;  // *NOT* OK.
IOSTANDARD = LVDS25;   // OK
 
If PlanAhead generated the incorrect .UCF file syntax, this represents a bug that you should report (by opening a webcase, please).  It's not clear whether the bug is in PlanAhead for generating incorrect syntax, or somewhere else in ISE for inconsistent handling of a constraint form, or both.
 
If you manually specified the IOSTANDARD incorrectly, then your problem is solved.
 
In either case, please mark this thread as "SOLVED", and accept our thanks for uncovering and documenting it.
 
- Bob Elkind
SIGNATURE:
README for newbies is here: http://forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369

Summary:
1. Read the manual or user guide.  Have you read the manual? Can you find the manual?
2. Search the forums (and search the web) for similar topics.
3. Do not post the same question on multiple forums.
4. Do not post a new topic or question on someone else's thread, start a new thread!
5. Students: Copying code is not the same as learning to design.
6 "It does not work" is not a question which can be answered. Provide useful details (with webpage, datasheet links, please).
7. You are not charged extra fees for comments in your code.
8. I am not paid for forum posts.  If I write a good post, then I have been good for nothing.