Stats

  • Locked Locked
  • Replies 5
  • Subscribers 92
  • Views 18084
  • 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. 
Parents

  • 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.

     

Reply

  • 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.

     

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.