Stats

  • Locked Locked
  • Replies 12
  • Subscribers 91
  • Views 19945
  • 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

Difference between icecaps tech file and QRC Techgen tech file

hyeh

Hello there,

I encounter some problems on the tech file as I try to generate the ice (equivalent capacitance) in voltagestorm. Previously, I try to use QRC Techgen to generate the RC tech file. However, this QRC Techgen tech file is not acceptable when I utilize it to generate ice in voltagestorm. I have looked at the manuals and it says that the tech file should be icecaps tech file rather than Techgen tech file. 

Does someone have the idea how to generate the icecaps tech file from ict file and its detailed procedure? I missed the important chapter in the voltagestorm data prepare manual.

My voltagestorm is 6.2.2a version and its required icecaps tech file should be the same.

Thanks for any help in advance.

Ho-Hsin

 

  • Hello Kari,

    Thanks for your response and kind.

    After I carefully read the manuals, I observe that our recongnizations are different. The one you are talking about is Fire & Ice QX "Cell Level" and I am talking about Fire & Ice QX "Transistor" Level. It seems like the same but the whole flow for RC extraction, their RC generated output and the required tech file have lots of difference.

    Currently I am using the VoltageStorm "Transistor" Level software (not voltagestorm "Cell" Level software) to do the power analysis. The transistor level needs the Fire & Ice QX Transistor Level extracted RC and its required input tech file is Icecaps tech file not the Techgen or RCgen generated tech file. According to the QRC Techgen manuals, I have noticed the following sentance

    "The technology file created by Techgen -cell is not a unified techfile, and is only suitable for "cell-level" extraction."

    Therefore, this is the reason why the tech file I generate in Techgen(RCgen) is not compatible with Fire & Ice QX Transistor Level. One is for cell level and the other one is for transistor level.

    Right now, I think the solution is to use the Icecaps commands. However, there is one missing chapter, as my previously mentioned, in "VoltageStorm Data Preparation Manual"  6.2.2a. The missing chapter is called "Chapter 2 Interconnect Modeling" I think this Chapter should have the instruction of the Icecaps command that should be used to extract icecaps.tch file and this icecaps.tch file is fitting to Fire & Ice QX Transistor Level.

    So, they are the reasons why I need that missing chapter to use icecaps. Would you mind providing the older or newer version "VoltageStorm Data Preparation Manual" ? (Whatever older and newer, the only one I pay attention to is that missing bit very important chapter)

    Thanks for your patience and kind to read this long article. I appreciate your help.

    Best Regards

    Ho-Hsin   

     

  •  Hi Ho-Hsin,

    Yes, that must be the source of our disconnect - cell-level vs transistor-level. 

    There also seems to be a disconnect in the docs! I see where the Fire & Ice manual points you to Chapter 2 of the Data Prep manual, but chapter 2 of the data prep manual is not called "Interconnect Modelling". It's something else. Still, here's the link to the 6.2.2 data prep manual on sourcelink:

    http://sourcelink.cadence.com/docs/files/Release_Info/Docs/dataprep/dataprep6.2.2/dataprepTOC.html

    Just browsing through chapter 1 of the data prep manual, it looks like you may need to use Techgen -capgen for transistor-level, but please take a look at the manual and see if it helps you get the tech file you need.

    I never do transistor-level, so I'm sorry that I'm not much help here.

    - Kari

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.