Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 16273
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HAL lint check design_info file

zeoshin

Hi, I am trying to turn off some checking rules in the design_info file. I tried the example given by reference manual

INFNOT {pattern = "*unused_*"} off;

and it does not work. I also tried

INFNOT {pattern = *unused_*} off;

but it seems that it exempts the whole file from INFNOT rule instead of lines containing that pattern.

Anyone has an idea what's the correct way to exempt rule checking based on pattern?

Parents

  • Did you remember to pass the design_info file to irun?
    It works fine for me if I do "irun -hal hal_play.sv -design_info design_info", where design_info contains:

    lint_checking file = *
    {
      INFNOT {pattern="*unused_*"} off;
    }

    And where hal_play.sv contains:

    module hal_play(input clk, input d, output bit q);
    wire unused_ok = 1'b1;

    wire bad_bad = 1'b1;
    always @(posedge clk) q <= d;
    endmodule

    I see only one INFNOT message:

    grep INFNOT irun.log
    halstruct: *N,INFNOT (./hal_play.sv,16|0): Ignoring wire 'bad_bad' with no fanout to module/design-unit outputs or child instances.


Reply

  • Did you remember to pass the design_info file to irun?
    It works fine for me if I do "irun -hal hal_play.sv -design_info design_info", where design_info contains:

    lint_checking file = *
    {
      INFNOT {pattern="*unused_*"} off;
    }

    And where hal_play.sv contains:

    module hal_play(input clk, input d, output bit q);
    wire unused_ok = 1'b1;

    wire bad_bad = 1'b1;
    always @(posedge clk) q <= d;
    endmodule

    I see only one INFNOT message:

    grep INFNOT irun.log
    halstruct: *N,INFNOT (./hal_play.sv,16|0): Ignoring wire 'bad_bad' with no fanout to module/design-unit outputs or child instances.


Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.