Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 14615
  • 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

convertion of oldtech sechmatics to newtech schematics

siva 234

Hi Sir,

I have one technolgy schematics,in that having mos's(p&n mos) and all the components like caps &resistors ,So i want to replace that mos's of old technology to new another technology mos's .

if it is possible to convert with SKILL scrips are not please let me know

Thanks in adavance

venkatasiva.j

Parents
  • Andrew Beckett

    First of all you'll have to distinguish between analog and digital schematics - I don't know what criteria you use to determine which is which.

    It's also not clear what you're actually trying to change - it doesn't make sense that a width would be the same as the old W/L (surely W/L will be dimensionless if you're dividing the width by the length).

    Maybe you're just saying that for digital schematics you keep the W and L the same as before, but for analog schematics the length becomes the L/sqrt(2) and leaves the width the same?

    If so, then it would be:

    procedure(MyFixLength(inst parName val)
      if(MyIsAnalog(inst~>cellView) then
        aelSuffixNotation(cdfParseFloatString(val)/sqrt(2))
      else
        val
      )
    )

    Note I'm using cdfParseFloatString and aelSuffixNotation to avoid using evalstring and sprintf (the aelSuffixNotation will make the expression prettier).

    You'd have to write MyIsAnalog() to take a cellView id to determine whether analog or digital.

    And then you'd specify MyFixLength as the function call as the third argument for mapping the length in the config file.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    First of all you'll have to distinguish between analog and digital schematics - I don't know what criteria you use to determine which is which.

    It's also not clear what you're actually trying to change - it doesn't make sense that a width would be the same as the old W/L (surely W/L will be dimensionless if you're dividing the width by the length).

    Maybe you're just saying that for digital schematics you keep the W and L the same as before, but for analog schematics the length becomes the L/sqrt(2) and leaves the width the same?

    If so, then it would be:

    procedure(MyFixLength(inst parName val)
      if(MyIsAnalog(inst~>cellView) then
        aelSuffixNotation(cdfParseFloatString(val)/sqrt(2))
      else
        val
      )
    )

    Note I'm using cdfParseFloatString and aelSuffixNotation to avoid using evalstring and sprintf (the aelSuffixNotation will make the expression prettier).

    You'd have to write MyIsAnalog() to take a cellView id to determine whether analog or digital.

    And then you'd specify MyFixLength as the function call as the third argument for mapping the length in the config file.

    Regards,

    Andrew.

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.