Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 14707
  • 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

delay vs buffer cells

SINGI

 I have one question

How does encounter recognisez whether a cell is of delay type or buff. In my case BuffD1 is buffer where as BufD8 is delay.
######encounter.log
List of usable buffers: BUFD1
List of identified usable delay cells: BUFD9
###################################
I checked Lef files and the lib files but no where it is mentioned as any particular type. I am confused on how encounter deffentiates them. In all the inputs I have given to encounter command of type buffer/delay is not mentioned any where 

Please give some exp.

BR

Sing

Parents
  • wally1

    Hi Sing,

    Encounter uses an internal algorithm which looks at the characteristics of the cells from the timing library to sort buffers from delay cells. The following solution explains how you can use the footprint file to modify this:

     http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11125148

    The algorithm works well but if you think it can be improved please open a Service Request through http://support.cadence.com and we look at your specific case.

    Thanks,

    Brian

Reply
  • wally1

    Hi Sing,

    Encounter uses an internal algorithm which looks at the characteristics of the cells from the timing library to sort buffers from delay cells. The following solution explains how you can use the footprint file to modify this:

     http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11125148

    The algorithm works well but if you think it can be improved please open a Service Request through http://support.cadence.com and we look at your specific case.

    Thanks,

    Brian

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.