芯路恒电子技术论坛

 找回密码
 立即注册

扫一扫,访问微社区

热搜: 活动
查看: 304|回复: 0

【Vivado常见问题】【DRC NSTD-1 DRC UCIO-1】无法生成bitstream

[复制链接]
  • TA的每日心情
    可爱
    2019-5-10 10:58
  • 251

    主题

    451

    帖子

    1万

    积分

    管理员

    Rank: 9Rank: 9Rank: 9

    积分
    11350
    发表于 2020-10-24 13:14:55 | 显示全部楼层 |阅读模式
    生成bit失败.jpg
    报错截图.jpg

    [DRC NSTD-1] Unspecified I/O Standard: 4 out of 4 logical ports use I/O standard (IOSTANDARD) value 'DEFAULT', instead of a user assigned specific value. This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all I/O standards. This design will fail to generate a bitstream unless all logical ports have a user specified I/O standard value defined. To
    allow bitstream creation with unspecified I/O standard values (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks NSTD-1].  NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run. Problem ports: a, b, out, and sel.


    [DRC UCIO-1] Unconstrained Logical Port: 4 out of 4 logical ports have no user assigned specific location constraint (LOC). This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all pin locations. This design will fail to generate a bitstream unless all logical ports have a user specified site LOC constraint defined.  To allow bitstream creation with unspecified pin locations (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks UCIO-1].  NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run.  Problem ports: a, b, out, and sel.



    此种情况发生在对一个工程进行全编译后生成bitstream时,如果没有给工程添加IO约束,那么整个工程生成的bitstream就没有任何意义,所以生成bitstream的时候就会报该错误并生成失败。正确的做法应该是给工程加入合理的IO约束之后,再编译生成bitstream。但是如果我们此刻就是一定要生成bitstream呢?可以使用一句脚本语言来暂时忽略该限制。只需要创建一个tcl脚本,在脚本中输入下述内容即可
    set_property SEVERITY {Warning} [get_drc_checks NSTD-1]
    set_property SEVERITY {Warning} [get_drc_checks RTSTAT-1]
    set_property SEVERITY {Warning} [get_drc_checks UCIO-1]

    ,然后在工程设置中的Bitstream选项中,添加该tcl文件到tcl.pre项中,如下图所示:
    设置添加tcl.jpg

    添加tcl.jpg


    以下为编写好的tcl文件。
    pre_hook.tcl (171 Bytes, 下载次数: 27)
    回复

    使用道具 举报

    您需要登录后才可以回帖 登录 | 立即注册

    本版积分规则

    QQ|小黑屋|手机版|Archiver|芯路恒电子技术论坛  |鲁ICP备16033493号

    GMT+8, 2020-12-4 01:23 , Processed in 0.178991 second(s), 13 queries , File On.

    Powered by Discuz! X3.3

    © 2001-2017 Comsenz Inc. Template By 【未来科技】【 www.wekei.cn 】

    快速回复 返回顶部 返回列表