Stats

  • Locked Locked
  • Replies 5
  • Subscribers 92
  • Views 18080
  • 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

Encounter cannot find a valid clock net / Timing library is not loaded

rexnyu
In SoC encounter 11.0, after I execute the following command:
 
createClockTreeSpec -output ../CTS/${DESIGN_NAME}_spec.cts \
   -bufferList BUFX2 BUFX4 INVX1 INVX2 INVX4 INVX8
 
 
It gives me the following message: 
 
CTS treats D-pins and I/O pins as non-synchronous pins by default.
If you want to change the behavior, you need to use the SetDPinAsSync
or SetIoPinAsSync statement in the clock tree specification file,
or use the setCTSMode -traceDPinAsLeaf {true|false} command,
or use the setCTSMode -traceIoPinAsLeaf {true|false} command
before specifyClockTree command.

*** End specifyClockTree (cpu=0:00:00.0, real=0:00:00.0, mem=345.0M) ***
<clockDesign CMD> ckSynthesis -report ../RPT/SboxWrapper/clock.report -forceReconvergent -breakLoop
Checking spec file integrity...
**WARN: (ENCCK-178):    CTS cannot find a valid clock net.
**WARN: (ENCCK-313):    You have not specified a clock tree. Use the specifyClockTree command to do so.
*** End ckSynthesis (cpu=0:00:00.0, real=0:00:00.0, mem=345.0M) ***
**clockDesign ... cpu = 0:00:00, real = 0:00:00, mem = 345.0M **
<CMD> optDesign -postCTS -hold -outDir ../RPT/SboxWrapper
**DIAG[opUtil.c:10662:update]: Assert "powerView != tocDefaultView"
**DIAG[opUtil.c:10667:update]: Assert "powerViewTlc"
**DIAG[opUtil.c:10662:update]: Assert "powerView != tocDefaultView"
**DIAG[opUtil.c:10667:update]: Assert "powerViewTlc"
**optDesign ... cpu = 0:00:00, real = 0:00:00, mem = 345.2M, totSessionCpu=0:00:05 **
**ERROR: (ENCOPT-6029): Timing Library is not loaded yet**ERROR: (ENCSYT-6692): [SoC_Encounter.tcl]: Invalid return code while executing "SoC_Encounter.tcl"
 
 
What could be the reason for this? My design does have a clock. 

  • Did you specify the spec file when invoking clockDesign "clockDesign -specFile ../CTS/${DESIGN_NAME}_spec.cts"?

    Brian

  • Yes. I have the following:

    createClockTreeSpec -output ../CTS/${DESIGN_NAME}_spec.cts \

       -bufferList BUFX2 BUFX4 INVX1 INVX2 INVX4 INVX8

    clockDesign -noDeleteClockTree -specFile ../CTS/${DESIGN_NAME}_spec.cts -outDir ../RPT/${DESIGN_NAME}

     

    But I realize one more thing. I see the timing library problem even earlier when I execute:

    placeDesign -noPrePlaceOpt

    setDrawView place

    After these two commands, the log file says:

    **Info: (ENCSP-307): Design contains fractional 20 cells.

    Average module density = 0.702.

    Density for the design = 0.702.

           = stdcell_area 1580 (1483 um^2) / alloc_area 2250 (2112 um^2).

    Pin Density = 1.013.

                = total # of pins 1600 / total Instance area 1580.

    **ERROR: (ENCDC-634):   Timing library is not loaded yet.....

    **ERROR: (ENCTS-136):   buffer footprint is not defined.

     

    I think I have point the .lib file to encounter to the correct directory by using the following lines in the config file

    set rda_Input(ui_timelib,min) "${NANGATE45_DIR}/gscl45nm.lib"

    set rda_Input(ui_timelib,max) "${NANGATE45_DIR}/gscl45nm.lib"

     

     

  • I wonder if my problem is related to this info from this doecument : Cadence Encounter Digital Implementation System Known Problems and Solutions. My script was originally written for 10.1.


    CCR 940227: MMMC design that loads into 10.x displays errors about missing library

    sets when loading into 11.1

    Description: The EDI 11.1 system no longer creates default MMMC objects, such as library

    sets, from information in the configuration file. If any part of your MMMC configuration references

    these legacy default objects, the software may issue error messages.

    Solution: To migrate the design manually, you need to create new library sets in the

    viewDefinition file to match the timing library specification in the configuration file. You should

    rename the library sets and all the references to them so that they do not refer to the old,

    reserved MMMC object names.

     

  • You should modify your flow to use a .globals file in place of the config file and define timing with MMMC. This solution and its related solutions will help with this:

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

    Brian

  • Did you solve this problem? I am facing the same issue

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.