• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. SoC Encounter: Troubles with encrypted Cap_Table

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 13380
  • 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

SoC Encounter: Troubles with encrypted Cap_Table

marten
marten over 12 years ago

Hi there,

currently I am having issues with adding cap_tables to my configuration. I use a TCL script for configuration, loading of LEF, LIBs etc.

So I add captables to my workspace using the command:

set rda_Input(ui_captbl_file) "-best $CAPTABLE_BEST -worst $CAPTABLE_WORST -typical $CAPTABLE_TYP"

the variables contain the paths to the *.captabl Files of my designkit. After configuration setup, I call 

commitConfig

which exits with the following error:

**ERROR: (ENCEXT-6109): Key word TempSiliconWidths at line 25 is not recognized inside WidthDependentTempCoeff
**DIAG[peReadCapTbl.c:1282:dbiParseCapValLine]: Assert "layer_id != -1"
**ERROR: (ENCEXT-2715): Syntax Error in line 26

I am using Encounter 10.12-s181_1 (64bit), the captables were created using Encounter 10.13-e079_1, maybe this is the Problem ?

I would be glad if someone could give me a kick in the right direction.

 

Krind regards,

Marten

 

  • Cancel
  • wally1
    wally1 over 12 years ago

    Hi Marten,

    You need to use a version of Encounter which is equal to or later than the version used to generate the cap table. Some enhancements were added to the cap table in 10.13 which 10.12 does not understand.

    Brian

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • marten
    marten over 12 years ago

     Hey wally1,

     thanks for your reply! When we installed the new SoC Version, I will check if everything works fine afterwards.

    cheers,

    Marten 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information