Stats

  • Locked Locked
  • Replies 7
  • Subscribers 90
  • Views 14509
  • 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

2 questions, 1for cdump file and 1for CeltIC

archive

Hi ALL:

I have 2 questions:

1. I try to use readgds command to read GDSII file as cdump file, and then using cdump2lef covert cdump to LEF, I got stucked and found that the cdump file is correct, but the generated LEF is wrong.......is cdump2lef having bugs? I am using SOCE52USR3.

2. When I am running CeltIC, I find the 'set_parm gtol' parameter, this gtol means the filter criteria for aggressors, means glitch tolerance. But I also find 'set_thresh -glitch_peak' can also set such criteria, gtol default is 5% of VDD and glitch_peak is 20% of VDD, what is the difference? Can anybody tell me?

thank!


Originally posted in cdnusers.org by eminemshow
Parents

  • Posted By BobD on 1/30/2008 7:56 AM
    Hi eminemshow,

    Regarding question #1, readgds and cdump2lef are no longer supported. The recommended way of creating a LEF MACRO from gds is to use the abstract generator which is part of the Virtuoso platform.

    For question #2, I don't know right off personally but hopefully a CeltIC expert can chime in.

    Thanks,
    Bob
    Thanks! bob, I will try to use abstract gen. Maybe later I will have questions about it.


    Originally posted in cdnusers.org by eminemshow
Reply

  • Posted By BobD on 1/30/2008 7:56 AM
    Hi eminemshow,

    Regarding question #1, readgds and cdump2lef are no longer supported. The recommended way of creating a LEF MACRO from gds is to use the abstract generator which is part of the Virtuoso platform.

    For question #2, I don't know right off personally but hopefully a CeltIC expert can chime in.

    Thanks,
    Bob
    Thanks! bob, I will try to use abstract gen. Maybe later I will have questions about it.


    Originally posted in cdnusers.org by eminemshow
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.