Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 13453
  • 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

ui_timingcon_file

ErezBS

Hi,

What is te difference between rda_Input(ui_timingcon_file) and rda_Input(ui_timingcon_file,full) in encounter config file?

thanks! 

  • This has tripped me up in the past as well. When you set these variables in the GUI it's more clear which is which.

    The ",full" option is for ILMs. The rda_Input(ui_timingcon_file) is what you'd use if you're not using ILMs.

    These notions are present when we go to using MMMC to configure the timing information as well. 

    Hope this helps,
    Bob 

  • Hi thanks a lot!

    yes - it helped.

    one more thing - i should define the ",full" with pointers to top level sdc file  and ILM's sdc files?

     

    Thanks,

    Erez. 

  • If you want to include SDCs that target entities within the ILMs, but written from a top-level context, include them in the ,full.

    If you want to write them in the context of the block-level, include them as part of the ILM definition itself.

    Hope this makes sense.

    -Bob 

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.