请问怎么才能设置bank I / O电压值？

嗨，
在用户指南（UG454）中，您可以找到以下图片：
当我记得丢失的文件附件时，我讨厌它......按下按钮后。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

Hi,
in the user guide (UG454) you find this picture:
 

 
I hate it when I remember the missing file attachment ... after I hit the button.
 
-- 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.

嗨鲍勃，
谢谢你添加图片。
不知怎的，我的帖子中没有显示base64编码的html。
（没有使用文件附件，但复制/粘贴）
似乎有些东西被打破了。
我在预览中看到了它，但现在不再使用编辑功能了。
奇怪...
亲切的问候 
Eilert



以下为原文

Hi Bob,
thanks for adding the picture.
Somehow the base64 encoded html isn't shown in my post. (Didn't use file attachment, but copy/paste)
Something seems to be broken. I saw it in the preview, but not now anymore when using the edit function. Strange...
 
Kind regards
  Eilert

（没有使用文件附件，但复制/粘贴）
我还使用了复制/粘贴（通过Windows屏幕剪切工具）。
不知道问题是什么，但最近论坛网站问题似乎越来越有选择性。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

(Didn't use file attachment, but copy/paste)
 
I also used copy/paste (via the Windows screen snipping tool).  Don't know what the problem is, but the forum website problems seem increasingly selective, lately.
 
-- 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.

eteam00写道：
（没有使用文件附件，但复制/粘贴）
我还使用了复制/粘贴（通过Windows屏幕剪切工具）。
不知道问题是什么，但最近论坛网站问题似乎越来越有选择性。
Eilert的形象被亵渎过滤器打破了：
M0U + ** **听到哔哔JJV / 88
显然这个bug尚未修复。



以下为原文

eteam00 wrote:
(Didn't use file attachment, but copy/paste)
 
I also used copy/paste (via the Windows screen snipping tool).  Don't know what the problem is, but the forum website problems seem increasingly selective, lately.

Eilert's image was broken by the profanity filter: 
 
M0U+**bleep**jJv/88Obviously this bug hasn't been fixed yet.

joelby，
请为更广泛的受众（包括我）详细说明这个问题，
漏洞什么时候侵入（例如粘贴HTML代码，粘贴ascii编码的二进制数据或位图）
解决方法（例如，避免某些图像格式，使用图像插入工具，用作附件）
非常感谢你带领这个bug。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

joelby,
 
Please elaborate on this problem for the broader audience (including me),
 

• When does the bug intrude (e.g. pasting HTML code, pasting ascii-encoded binary data or bitmaps)
  
• Workarounds (e.g. avoid certain image formats, use image insertion tool, use as attached file)
  

Thanks much for leading the charge on this bug.
 
-- 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.

嗨鲍勃，
在这个主题中我的帖子中有更多信息。
放置在回复文本框中的任何内容都受亵渎内容过滤器的约束，该过滤器会自动用** bleep **替换“淫秽”文本字符串。
虽然论坛一般不受滥用的困扰，但还算公平。
主要问题是从剪贴板粘贴到编辑框中的图像（而不是使用插入/编辑图像附加）使用base64编码包含在文本正文中，例如，
这样可以正常工作，但是对于大图像来说它有点愚蠢，因为这意味着页面将比在服务器的文件系统上保存图像并使用HTTP单独访问（如普通附件）时要大得多。
该机制实际上仅用于小图像，其中下载扩展的base64编码版本所花费的时间少于获取另一资源的额外网络延迟。
问题是base64编码数据本质上是随机的，偶尔会偶尔包含亵渎过滤器识别为淫秽的文本字符串。
因为论坛软件将消息体视为纯文本，它只是将它们替换为** bleep **，这会导致base64编码因使用无效字符而中断（但即使它没有，也会破坏图像）
只需通过更改和插入中间的其他字符）。
以下是建议的解决方案列表：
禁用亵渎过滤器并通过审核报告处理滥用行为。
对于这个论坛可能没问题，但Xilinx可能无法接受。
请求Lithium修改论坛的消息发布例程以检测内联图像，将它们提取到文件并重写img标记以通过HTTP访问该文件。
甚至可以在此时将BMP转换为PNG。
最佳，但相对复杂的变化。
请求Lithium修改淫秽过滤器以忽略base64编码的字符串。
如果当前过滤器使用正则表达式，这将很容易 - 你可以忽略/src="data:image(.*?)"/中出现的任何淫秽。
如果没有，请改进现有的朴素文本替换方案以使用大多数主要Web编程语言支持的正则表达式。
额外：
唯一可靠的解决方法是始终使用“插入/编辑图像”而不是粘贴图像。



以下为原文

Hi Bob,
 
There's a little more information in my post in this thread.
 
Any content placed in a reply's text box is subject to the profanity content filter, which automatically replaces 'obscene' text strings with **bleep** . Fair enough, though the forum isn't generally plagued by abuse.
 
The main issue is that images that are pasted in to the edit box from the clipboard (rather than attached using insert/edit image) are included within the body of the text using base64 encoding, e.g.
 
This works fine, but for large images it is a bit stupid because it means that pages will be much larger than they would be if images were saved on the server's file system and accessed separately using HTTP, like a normal attachment. The mechanism is really only intended for use with small images where the time taken to download the expanded base64 encoded version is less than the additional network latencies in fetching another resource.
 
The problem is that the base64 encoded data, which is essentially random, will by chance occasionally contain strings of text that the profanity filter recognises as obscene. Because the forum software treats the message body as plain text, it just substitutes these for **bleep** and this causes the base64 encoding to break due to use of invalid characters (but even if it didn't, it would break the image merely by changing and inserting additional characters into the middle).
 
Here are a list of suggested solutions:
 

• Disable the profanity filter and deal with abuse through moderation reports. Probably okay for this forum, but may not be acceptable for Xilinx.
  
• Ask Lithium to modify the forum's message posting routine to detect inline images, extract them to a file and rewrite the img tag to access the file over HTTP. Could even convert BMP to PNG at this point. Optimal, but a relatively complex change.
  
• Ask Lithium to modify the obscenity filter to ignore base64-encoded strings. This would be easy if the current filter is using regular expressions - you can just ignore any obscenity occurring within /src="data:image(.*?)"/ . If not, retrofit the existing naive text substitution scheme to use regular expressions, which are supported in most major Web programming languages.
  

 Additional:
 
The only reliable workaround is to always use "Insert/edit image" rather than pasting images.