Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 15016
  • 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

RE: path groups encounter timing analysis

kenambo

Hi All,

While doing timing analysis, I have a different path group as "reg2reg_temp.2234" instead of "reg2reg" path group. The path group is supposed to be reg2reg right?

Why this change? Is there anything else I can do to change this?

And in timing report, I have some paths in which launch clock is leading edge of a clock and capture clock is also the same clock with trailing edge. and the phase shift also 0.
Is this common for a timing path? or am I missing something?

Thanks.

Parents

  • Hi,

    Can you please check which are data to data checks ?

    if yes, In general we are seeing this issue because of

    1.missing case analysis statements for scan pins (if you are seeing paths between SI to SE)

    2. Arc definition in  library data.

Reply

  • Hi,

    Can you please check which are data to data checks ?

    if yes, In general we are seeing this issue because of

    1.missing case analysis statements for scan pins (if you are seeing paths between SI to SE)

    2. Arc definition in  library data.

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.