• 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. Logic Design
  3. No binary/Encrypted TCL(tcl compiler) support in all cadence...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 62
  • Views 3876
  • 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

No binary/Encrypted TCL(tcl compiler) support in all cadence tools, but Yes in Synopsys!

iceda
iceda over 16 years ago

 Currently everybody is talking out IP protection, including all TCL commands, but it seems that Cadence didn't do good job for this kind of IP proctection unlike synopsys. Now all byte-code TCL is supported very well in all synopsys tools, but not a tiny support in all cadence tools!

  • Cancel
  • grasshopper
    grasshopper over 16 years ago

    Hi iceda,

    not sure what you are talking about. All Cadence tools support the encryption outlined in IEEE1800, System Verilog LRM. In SV you can also use `pragma protect compiler directive which is supported by Cadence tools as well. Needless to say the same encryption scheme can apply to VHDL and other languages supported by Cadence tools. Not only that but tools also support partial encryption of files, different protection levels, and in many cases, encryption of TCL as well. Furthermore, in my experience, the Synopsys encryption scheme does not interoperate with any other vendors as described in IEEE1800. Maybe I missunderstood you message and can clarify.

    gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • iceda
    iceda over 16 years ago

     I'm not taking about the theverilog/VHDL code. I'm saying the standard TCL commands used in synthesis/formal verification/P&R/static timing analysis EDA tools. For example, the following industry standard TCL syntax:

     set TTT 1

    if {$TT} {

    echo "it's good!!!"

    }

    If you source above tcl commands in any EDA tools, that's fine, but if you compile them to binay/byteCode using any Tcl Compiler(such as TclPro or ActiveTCL), Cadence EDA tools won't support those compiled tcl command, but Synopsys's support them very well.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • grasshopper
    grasshopper over 16 years ago

     Hi iceda,

     while it is my understanding that the byte-code compiled code from TCLPro can be provided with the decryption utility embedded as well, it is still a proprietary solution specific to TCLPro and not consistent amongst all TCLCompilers. I am curious what is your driving motivation to use this solution as opposed to the industry standard encryption provided by IEEE1800 and available in all Cadence tools as well as many other vendors. I am sure you are well aware that byte-compilation and encryption are not necessarily the same things and while TCLPro byte-compiled code provides some encryption, it may not be as robust of an encryption solution.

     gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • iceda
    iceda over 16 years ago
    Hi grasshopper:

     Thanks for your reply, but could you please tell me where can I find free encryption utility to follow industry standard encryption provided by IEEE180, so we can use it to encrypt our tcl commands,which can be supported in all Cadence EDA tools as well as Synopsys EDA tools.

    Thanks,

     iceda

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • grasshopper
    grasshopper over 16 years ago

     Hi iceda,

     I can only speak for the products I am familiar with and I am not aware of any Cadence provided encryption utility that is free and  stand-alone. You may be able to gain access to encryption utility through "Connections" program. Another issue you may keep in mind is that not every tool uses TCL natively so in some cases I am not even sure that TCLPro byte-compiled code could be made to work. Another suggestion I will make is to file a service request through support@cadence.com if you feel TCLPro byte-compiled support is needed for whatever tools you are using. I do not believe supporting it is an issue of whether or not it is possible since I believe it is possible indeed but the issue is more likely one of customer demand for such capability and if so, should it be TCLPro byte-compiled code or one of the other TCL Compiler out there and whatever licensing nonesense is involved.

    gh-

    • 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