• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Logic Design
  3. Need some more information about Trimmed index [CDFG-420...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 61
  • Views 13296
  • 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

Need some more information about Trimmed index [CDFG-420]

archive
archive over 18 years ago

While using RTL compiler I get the following warning message. [CDFG-420]

Trimmed index 'portIn' of signal 'startT0' from 2 bits to 1 bits in file

The code for above is :

parameter PORTS = 4;
input wire [1:0]    portIn;
input wire [3:0]    cntIn;
reg [PORTS -1:0]        pauseDa;

case (cntIn)
            0: pauseDa[portIn]

I noticed that in other instances, when I used an integer instead of a binary number, it gave the same warning.
As soon as I converted 0 to 1'b0 and 1 to 1'b1, this warning was not issued any more.

In the above case, whenever, a bus was used as the index, it issues the above warning.  From the code above, we
know pauseDa can have 4 values and portIn can address 4 locations.  But the warning says trimming index to 1 bit.

There was no such problem when integers were used for indexing.  (in a for loop).  So, I modified the code as follows,

int portIn_int;
                                                                                           
assign portIn_int = portIn;

        case (cntIn)
            0: pauseDa[portIn_int]

But I continue to get the same warning. 

Trimmed index 'portIn_int' of signal 'pauseDa' from 32 bits to 2 bits

The problem is even though the RTL and netlist can be verified each time using verplex, I have to still go through the
logs to make sure that all these warnings are ok.

Alternatively, I could set:

set_attr hdl_trim_target_index false

but it mentions that the design is not optimized.  I did verify, that there is a slight increase in area with the above
setting to false.  Default is true. 

Any suggestions or similar experiances are appreciated.

Thanks,
Amar.


 


Originally posted in cdnusers.org by adudyala
  • Cancel
Parents
  • archive
    archive over 18 years ago

    Sorry,

    I put the wrong Warning number. The correct one is : [CDFG2G-617]

    Thanks,
    Amar


    Originally posted in cdnusers.org by adudyala
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    Sorry,

    I put the wrong Warning number. The correct one is : [CDFG2G-617]

    Thanks,
    Amar


    Originally posted in cdnusers.org by adudyala
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information