精华内容
下载资源
问答
  • waring和warning
    千次阅读
    2021-05-21 14:33:31

    1."WARNING:Route:455 - CLK Net:trn_clk_OBUF may have excessive skew&nBSP;

    because 0 CLK pins and 1 NON_CLK pins failed to route using a CLK

    template."

    Solution

    This message informs the user that some loads on the clock net are not

    clock pins. Therefore, the clock template that is normally uSED to connect

    clock pins will not be used to connect the loads. A different routing that

    involves local routing will be used, potentially inducing some skew on the

    clock net.

    Opening your design in FPGA Editor will allow you to see what loads are

    connected to the clock net, and the cause of the warnings.

    The amount of skew on the net will be reported in the Place and Route

    report.

    If the loads on the net shown in FPGA Editor are in accord with your

    design, the skew reported in the PAR report is not critical for the

    design, and the timing constraint requirement on that net is met, then

    this warning can be safely ignored.

    实例原因:在代码中用到这样的语句时(aa’event and

    aa=’1’),aa不是时钟信号,最多只是时钟信号产生的一类周期信号,aa被作为了另一个

    进程或模块的类似周期信号的作用。(我是在行场信号发生器中 出现的这样的问题,用产

    生的行同步信号(行同步信号是由全局时钟信号驱动产生的)再去驱动产生场同步信号,产

    生的场同步信号相对与输入的全局时钟,有一定 的倾斜)

    2. "WARNING:Xst:647 - Input is never used."

    or

    "WARNING:Xst:648 - Output is never used."

    Solution

    This particular port has been declared in your HDL description, but does

    not drive or is not driven by any internal logic.

    Unused input ports will remain in the design, but they will be completely

    unconnected. If the port is not intended to be used, this message can be

    safely ignored. To avoid this message, reMOVe any loadless or sourceless

    elements from your HDL description.

    Output ports will remain in the final netlist and will be driven by a

    logic 0. To avoid the message and to save the port resource, remove the

    unused output port from your HDL description.

    实例原因:一般输入端口不要预留,即使不使用,在代码中定义的输入端口就一定要有

    输入的; 而输出端口不用到的可以用OPEN封上, 最常见的是在利用DLL和DCM时, CLK90,

    CLK180,

    CLK270等一般不用,在端口连接的时候都用 OPEN封上。       3. ERROR:HDLParsers:3562 - pepExtractor.prj line 1 Expecting 'vhd ' or

    'verilog' keyword, found 'work'。SolutionThis occurs when there are spaces

    embedded in the project location.

    A bad example for project location would be:

    C:/Documents and settings/User/example.ise.

    A good example fpr project location would be:

    C:/ISE_tests/example.ise.

    实例原因:在 ISE9.1的版本里,在行为仿真和使用约束编辑器的时候会遇到,主要原

    因是工程的路径名里有空格一类的不被要求的非英文字符。

    4. "ERROR:Xst:2587 Port of instance has different

    type in definition " .

    Solution

    Compare the component declaration and instantiation to the submodule that

    is instantiated. When this error occurs, the declaration matches the

    instantiation, but does not match the port declarations of the submodule.

    Change either the port declarations in the declaration/instantiation pair

    or the submodule port declarations so that they match. This error is

    SPECific to the types of ports in the submodule.

    实例原因:一般是子模块宣称和子模块的实体定义中端口的宽度和类型(in, out, inout,

    buffer)不匹配造成的。

    5. XST can generate very large log files for certain designs. In some

    cases, the generation of these log files can even cause an increase in

    runtime. How can I eliminate or hide certain frequently generated

    messages?

    Solution

    For users of XST via Project Navigator

    starting in ISE 7.1i, Project Navigator has the capability to do message

    fiLTEring for all Xilinx tools. Please refer to the Project Navigator help

    on how to use this method.

    For users of XST via command line

    You can hide specific messages generated by XST at the HDL or Low-Level

    Synthesis steps in specific situations by using the XIL_XST_HIDEMESSAGES

    environment variable. This environment variable can have one of the

    following values:

    -- none: maximum verbosity. All messages are printed out. This is the

    default.

    -- hdl_level: reduce verbosity during VHDL/Verilog Analysis and HDL BASIC

    and Advanced Synthesis.

    -- low_level: reduce verbosity during Low-level Synthesis

    -- hdl_and_low_levels: reduce verbosity at all stages

    The following messages are hidden when hdl_level or hdl_and_low_levels

    values are specified for the XIL_XST_HIDEMESSAGES environment variable:

    WARNING:HDLCompilers:38 - design.v line xx Macro 'my_macro' redefined

    NOTE: This message is issued by the Verilog compiler only.       WARNING:Xst:916 - design.vhd line xx: Delay is ignored for synthesis.

    WARNING:Xst:766 - design.vhd line xx: Generating a Black Box for component

    comp.

    Instantiating component comp from Library lib.

    Set user-defined property "LOC = X1Y1" for instance inst in unit block.

    Set user-defined property "RLOC = X1Y1" for instance inst in unit block.

    Set user-defined property "INIT = 1" for instance inst in unit block.

    Register reg1 equivalent to reg2 has been removed.

    The following messages are hidden when low_level or hdl_and_low_levels

    values are specified for the XIL_XST_HIDEMESSAGES environment variable:

    WARNING:Xst:382 - Register reg1 is equivalent to reg2.

    Register reg1 equivalent to reg2 has been removed.

    WARNING:Xst:1710 - FF/Latch reg (without init value) is constant in block

    block.

    WARNING:Xst 1293 - FF/Latch reg is constant in block block.

    WARNING:Xst:1291 - FF/Latch reg is unconnected in block block.

    WARNING:Xst:1426 - The value init of the FF/Latch reg hinders the constant

    cleaning in the block block. You could achieve better results by setting

    this init to value.

    实例原因:在综合时,有很多的综合警告是可以忽略的,以上大致的罗列几项。

    6. "WARNING:Xst:737 - Found n-bit latch for signal ."

    The listing for "n" is the width of the latch.

    If latch inference is intended, you can safely ignore this message.

    However, some iNEFficient coding styles can lead to accidental latch

    inference. You should analyze your code to see if this result is intended.

    The examples below illustrate how you can avoid latch inference.

    实例原因:一般出现这样的问题都是代码出现了锁存器,因避免这样的代码写法,电路

    会不稳定,因利用触发器去寄存数据在时钟沿。

    Solution 1

    include all possible cases in the case statement

    Verilog

    always @ (SEL or DIN1 or DIN2)

    begin

    case (SEL)

    2'b00 : DOUT <= DIN1 + DIN2;

    2'b01 : DOUT <= DIN1 - DIN2;

    2'b10 : DOUT <= DIN1;

    endcase

    end

    VHDL

    process (SEL, DIN1, DIN2)

    begin

    case SEL is

    when "00" => DOUT <= DIN1 + DIN2;  when "01" => DOUT <= DIN1 - DIN2;

    when "10" => DOUT <= DIN1;

    end case;

    end process;

    These two examples create latches because there is no provision for the

    case when SEL = "11." To eliminate the latches, add another entry to deal

    with this possibility.

    Verilog

    2'b11 : DOUT <= DIN2;

    VHDL

    when "11" => DOUT <= DIN2;

    Using the "DEFAULT" (Verilog) or "WHEN OTHERS" (VHDL) clause always works,

    but this can create extraneous logic. This is always the safest

    methodology, but might produce a larger and slower design since any

    unknown state has logic that is needed to bring it to a known state.

    Solution 2

    Assign to all the same outputs in each case.

    Verilog

    always @ (SEL or DIN1 or DIN2)

    begin

    case (SEL)

    2'b00 : DOUT <= DIN1 + DIN2;

    2'b01 : DOUT <= DIN1 - DIN2;

    2'b10 : DOUT <= DIN1;

    2'b11 :

    begin

    DOUT <= DIN2;

    TEMP <= DIN1;

    end

    endcase

    end

    VHDL

    process (SEL, DIN1, DIN2)

    begin

    case SEL is

    when "00" => DOUT <= DIN1 + DIN2;

    when "01" => DOUT <= DIN1 - DIN2;

    when "10" => DOUT <= DIN1;

    when "11" =>

    DOUT <= DIN2;

    TEMP <= DIN1;

    end case;

    end process;       These examples infer latches because the "11" case assigns two outputs,

    while the others assign only one. Looking at this case from TEMP's point

    of view, only one of four possible cases are specified, so it is

    incomplete. You can avoid this situation by assigning values to the exact

    same list of outputs for each case.

    Solution 3

    MAKE sure any "if / else if" statements have a concluding "else" clause:

    VHDL:

    process (ge, din)

    begin

    if (ge = '1') then

    dout_a <= din;

    else

    dout_a <= '0';                               -- This is a concluding

    "else" statement.

    end if;

    end process;

    Verilog:

    always @(ge or din)

    if (ge) dout_a <= din;

    else dout_a <= 1'b0;                        // This is a concluding "else"

    statement.

    在不影响电路功能的情况下,要写完整的 if--else语句。(对于时钟沿触发时,是不要 else

    的)

    更多相关内容
  • 微信小程序开发warning

    2021-03-29 17:42:59
    如果列表中项目的位置会动态改变或者有新的项目添加到列表中,并且希望列表中的项目保持自己的特征状态(如 中的输入内容, 的选中状态),需要使用 wx:key 来指定列表中项目的唯一的标识符。 wx:key 的值以两种...
  • See the caveats in the documentation: http://pandas.pydata.org/pandas-docs/stable/user_guide/indexing.html#returning-a-view-versus-a-copy df_1_level['level1_name'] = df_1_level['department_name'] ...
  • 今天小编就为大家分享一篇Python 忽略warning的输出方法,具有很好的参考价值,希望对大家有所帮助。一起跟随小编过来看看吧
  • jlink v9 warning clone解决

    2022-03-27 01:29:07
    试试吧
  • #erro#warning使用分析

    2022-04-20 20:44:22
    #error编译指示字用于自定义程序员特有的编译错误消息,类似的#warning用于生成编译警告。 #error是一种预编译器指示字。 #error可用于提示编译条件是否满足。 代码: #ifnedf __cplusplus #error This file should...

    1 #error的用法

    error用于生成一个编译错误消息。
    用法:#error message(message不需要用双引号包围)。
    #error编译指示字用于自定义程序员特有的编译错误消息,类似的#warning用于生成编译警告。
    #error是一种预编译器指示字。
    #error可用于提示编译条件是否满足。

    代码:

    #ifnedf __cplusplus
        #error This file should be processed with C++ compiler.
    #endif
    

    编译过程中的任意错误信息意味着无法生成最终的可执行程序。

    #error预处理初探

    #include <stdio.h>
    
    #ifndef __cplusplus
        #error This file should be processed with C++ compiler.
    #endif
    
    class CppClass
    {
    private:
        int m_value;
    public:
        CppClass()
        {
    
        }
    
        ~CppClass()
        {
        }
    };
    
    int main()
    {
        return 0;
    }
    
    

    #error在条件编译中的应用

    #include <stdio.h>
    
    void f()
    {
    #if ( PRODUCT == 1 )
        printf("This is a low level product!\n");
    #elif ( PRODUCT == 2 )
        printf("This is a middle level product!\n");
    #elif ( PRODUCT == 3 )
        printf("This is a high level product!\n");
    #else
        #error the PRODUCT NOT defined!
    #endif
    }
    
    int main()
    {
        f();
    
        printf("1. Query Information.\n");
        printf("2. Record Information.\n");
        printf("3. Delete Information.\n");
    
    #if ( PRODUCT == 1 )
        printf("4. Exit.\n");
    #elif ( PRODUCT == 2 )
        printf("4. High Level Query.\n");
        printf("5. Exit.\n");
    #elif ( PRODUCT == 3 )
        printf("4. High Level Query.\n");
        printf("5. Mannul Service.\n");
        printf("6. Exit.\n");
    #else
        #error the PRODUCT NOT defined!
    #endif
    
        return 0;
    }
    
    

    2 小结

    #error用于自定义一条编译错误信息。
    #warning用于自定义一条编译警告信息。
    #error和#warning常应用于条件编译的情形。
    参考:https://blog.csdn.net/qq_20233867/article/details/78619565

    展开全文
  • 参考博客 - Python日志...通过supervisor管理项目时,会有stdoutstderr两种日志路径的设置方式,通过给一个logger设置2个StreamHandler后,分别对handler设置日志级别的过滤,实现日志的分级输出。 # -*- coding: ...

    参考博客 - Python日志分级别输出到不同文件

    参考思路:为logger设置2个handler,再对2个handler设置不同的filter进行日志过滤。
    通过supervisor管理项目时,会有stdout和stderr两种日志路径的设置方式,通过给一个logger设置2个StreamHandler后,分别对handler设置日志级别的过滤,实现日志的分级输出。

    # -*- coding: utf-8 -*-
    import logging
    import logging.handlers
    import os
    
    
    def setup_logger(logger_name):
        # root_path = os.path.abspath(os.path.join(os.path.dirname(__file__), os.pardir))
        root_path = os.path.abspath(os.path.join(os.getcwd(), "../.."))  # 与项目根目录平级
        log_path = root_path + '/logs/' + logger_name + '.log'
        myapp = logging.getLogger(logger_name)
        myapp.setLevel(logging.INFO)  # 先将INFO及以上的日志都添加到logger,再按照是否WARNING过滤是否输出到文件
    
        formatter = logging.Formatter("%(asctime)s - %(filename)s - %(funcName)s[line:%(lineno)d] - %(levelname)s: %(message)s")
    
        rotatingHandler = logging.handlers.RotatingFileHandler(log_path, maxBytes=20 * 1024 * 1024, backupCount=10)
        rotatingHandler.setFormatter(formatter)
        myapp.addHandler(rotatingHandler)
    
        streamHandler = logging.StreamHandler()
        streamHandler.setFormatter(formatter)
        myapp.addHandler(streamHandler)
    
        # 过滤级别:控制台输出INFO和WARNING级别,文件只记录WARNING级别
        info_filter = logging.Filter()
        info_filter.filter = lambda record: record.levelno < logging.WARNING  # 设置过滤等级
        err_filter = logging.Filter()
        err_filter.filter = lambda record: record.levelno >= logging.WARNING
    
        # streamHandler.addFilter(info_filter)
        rotatingHandler.addFilter(err_filter)
    
    
    # 示例
    def main():
        # setup_logger('log1', r'log1.log')
        # setup_logger('log2', r'log2.log')
        # log1 = logging.getLogger('log1')
        setup_logger('myapp')
        myapp = logging.getLogger('myapp')
    
        myapp.info("file test")
        myapp.warning("file warning")
    
    
    if __name__ == '__main__':
        main()
        # print(os.path.abspath(os.path.join(os.getcwd(), "../..")))
    

    效果

    控制台输出INFO和WARNING级别,文件只记录WARNING级别
    在这里插入图片描述
    在这里插入图片描述

    展开全文
  • 解决报错libpng waring:iccp:known incorrect srgb profile,递归查找修改png图片为Qt适配使用的图片
  • php怎么关闭warning提示

    2021-04-08 09:46:46
    php怎么关闭warning提示2020-07-14 14:07:46php关闭warning提示的方法是:可以通过error_reporting()函数来实现。error_reporting()函数可以设置当前脚本的错误报告级别。具体代码为:【error_reporting(0);】。要...

    php怎么关闭warning提示2020-07-14 14:07:46

    99e5055e8714a7624b0539e8f44d624c.png

    php关闭warning提示的方法是:可以通过error_reporting()函数来实现。error_reporting()函数可以设置当前脚本的错误报告级别。具体代码为:【error_reporting(0);】。

    要关闭warning提示可以通过error_reporting()函数来实现。

    (推荐教程:php教程)

    相关函数介绍:

    error_reporting() 函数规定报告哪个错误。该函数设置当前脚本的错误报告级别。该函数返回旧的错误报告级别。

    函数语法:

    error_reporting(report_level)

    参数介绍:

    report_level    可选。规定当前脚本的错误报告级别。值数字和常量名都能接受,但是,考虑未来的 PHP 版本的兼容性,推荐使用常量名。

    代码实现:<?php

    error_reporting(0);

    ?>

    展开全文
  • php程序(warning)警告

    2021-04-21 07:44:14
    php.ini里配置error_reporting = E_ALL就意味着输出记录所有错误信息,包括Fatal error、Warning、Notice等各种信息,php.ini配置里有详细的说明: ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Error handling and logging...
  • :warning: 显示js错误 在浏览器中发生js错误时显示一条消息。 对于在手机,平板电脑台式机上开发测试您的网站很有用。 不久: 细节:浏览器任何。安装npm install show-js-error --save-dev使用< link rel =...
  • php warning 关闭的方法

    2021-03-23 12:50:11
    php warning关闭的方法:首先指定error_log文件;然后在php.ini中设置“display_errors = Off”即可。php关闭warningerror_reporting 设定错误讯息回报的等级2047我记得应该是E_ALL。php.ini 文件中有许多配置设置。...
  • 关于vue的warning(一)

    千次阅读 2019-03-13 14:10:46
    今天做项目的时候突然发现用vue-cli启动项目以后发生了几个警告。 There are multiple modules with names that only differ in casing. This can lead to unexpected behavior when compiling on a filesystem with...
  • php怎样去掉warning提示

    2021-04-08 09:47:39
    【摘要】PHP即“超文本预处理器”,是一种通用...下面是php怎样去掉warning提示,让我们一起来看看php怎样去掉warning提示的具体内容吧!php怎样去掉warning提示php去掉warning提示的方法:1、打开php.ini配置文件...
  • Makefile控制函数error和warning Makefile 中提供了两个控制 make 运行方式的函数。其作用是当 make 执行过程中检测到某些错误时为用户提供消息,并且可以控制 make 执行过程是否继续。这两个函数是 "error" ...
  • Python如何忽略warning的输出
  • 怎么在php中关闭warning提示发布时间:2020-07-15 11:50:17来源:亿速云阅读:91作者:Leah本篇文章给大家分享的是有关怎么在php中关闭warning提示,小编觉得挺实用的,因此分享给大家学习,希望大家阅读完这篇文章...
  • C 语言:#warning 指令

    2022-05-27 09:13:51
    本教程解释了如何在 C 语言中使用 #warning 预处理器指令。更多C教程请访问码农之家 描述 在 C 编程语言中,#warning 指令类似于#error 指令,但不会导致取消预处理。#warning 指令之后的信息在预处理继续之前...
  • 1. WARNING: Application does not specify an API level requirement![2011-03-03 19:03:03 - rss_reader]WARNING: Application does not specify an API level requirement![2011-03-03 19:03:03 - rss_reader]Dev...
  • notice waring 等问题 ini_set("display_errors", 0); error_reporting(E_ALL ^ E_NOTICE); error_reporting(E_ALL ^ E_WARNING); 2,打开php.ini文件,找到相关设置(如下图),将 on 改成 off,就可以屏蔽出错(不...
  • Python忽略warning警告错误

    千次阅读 2022-02-24 08:49:56
    python开发中经常遇到报错的情况,但是warning通常并不影响程序的运行,而且有时特别讨厌,下面我们来说下如何忽略warning错误。 在说忽略warning之前,我们先来说下如何主动产生warning错误,这里用到warnings模块...
  • 查看MySQL的warning

    千次阅读 2021-01-19 00:50:57
    在执行sql语句,或者导入...命令很简明,一查看发现一般的警告是这样的Warning | 1265 | Data truncated for column '刊名' at row 1265//警告是字段长度不够,导入的是被系统自动裁剪后的数据====================...
  • 此文章讲述了QuartusII里出现的大部分警告的处理方法!
  • keil编译出现如下警告: WARNING L1: UNRESOLVED EXTERNAL SYMBOL SYMBOL: UART0 MODULE: .\obj\app_uart0.obj (APP_UART0) WARNING L2: REFERENCE MADE TO UNRESOLVED EXTERNAL ...解决办法:L1L2是同...
  • 常见warning及error

    2014-05-10 09:13:00
    warning: 1.waring:Assigning to 'id<UITableViewDataSource>' from incompatable type 'ContactListEnterpriseVC *const_strong* 解决:这种情况一般是设置了tableView的代理,但是并没有采用相关的协议,...
  • PHP 关闭 Waring警告

    千次阅读 2018-04-08 16:48:18
    找到初始文件在php文件开头写入:/...//显示所有提示error_reporting(0);//不显示所有提示error_reporting(7);//只显示严重错误提示下列常见错误1、 E_ERROR 致命的运行时错误2、 E_WARNING 运行时警告(非致命性错误...
  • fake_warning-main.zip,fake_warning-main,index.html,voice.aiff,warning.mp3,icon.png,README.md,voice.mp3
  • 这里是说密钥文件权限不能为0777,0777权限太开放了...这里“/home/zhurong/.ssh/id_ed25519”就是warning里给出的密钥文件名,所以你需要换成你的warning信息里给出的秘钥文件名。格式如下:chmod 权限码 密钥文件名...
  • 类似的警告: warning: type mismatch with previous implicit declaration warning: type mismatch with previous implicit declaration warning: previous implicit declaration of 'Example()' 类型2: 显示:...
  • 今天在看源码的时候,遇到以下内容: #pragmawarning(push)是保存当前的编译器警告状态; #pragmawarning(pop)是恢复原先的警告状态。...#pragma warning(disable : 4100) // unused parameter #endif // _MSC_VE...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 3,785
精华内容 1,514
热门标签
关键字:

waring和warning