Quantcast
Channel: Cadence Digital Implementation Forum
Viewing all articles
Browse latest Browse all 1454

Multimode timing with create_mode and read_sdc, docs conflicting

$
0
0

I want to do timing analysis on two functional modes I have in my design.

I'm using GENUS162.

Searching around I've been told to do it this way:

create_mode -name {MODEA MODEB}
set CURRENT_MODE MODEA
read_sdc -mode MODEA constraints.sdc
set CURRENT_MODE MODEB
read_sdc -mode MODEB constraints.sdc

and in my constraints.sdc I have a chunk which is included based on a switch:

switch -glob CURRENT_MODE {
  MODEA {
     set_case_analysis 0 [get_ports some_input_tied_low_when_in_modea]
      # modea-secific constraints
    } 
    MODEB {
     set_case_analysis 1 [get_ports some_input_tied_low_when_in_modea]
     # modeb-specific constraints
    }
}

Now, I try to do that but the first issue is that read_sdc doesn't accept a -mode flag but -view flag, to specify a constraints view, which is not the same as a mode. Setting up a constraints view seems far more complicated than setting up a simple mode.

So I guess the version of Genus I'm using is not in step with the example I've come across on the Cadence support site. There are no examples in the docs bundled with the tool that I can find. So if anyone can point me to or paste me an example of doing what I've outlined above but with the version of Genus I'm using (as obviously things appear to have changed) then that'd be appreciated.


Viewing all articles
Browse latest Browse all 1454

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>