Stats

  • Locked Locked
  • Replies 20
  • Subscribers 126
  • Views 23645
  • 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

detecting process corner from within verilogA model

SoniaMK

Hello,

I need to create a model of a current source in verilogA but the value of the current depends also on the process corner. Is there a way for the verilogA model to detect what corner the simulation runs with? In ADEL we specify the corners through an include statement like this:

include <model file> section=typical

Thanks

Parents

  • There's nothing to stop you defining your own wrapper around the foundry files which does something like this:

    library mylib
    section NN
    parameter corner=1
    include "foundry.scs" section=NN
    endsection NN

    section FF
    parameter corner=2
    include "foundry.scs" section=FF
    endsection FF

    endlibrary mylib

    Something like that... then you can include your wrapper around the foundry models and don't have to touch the foundry models in any way. 

    Andrew.

  • in reply to Andrew Beckett

    The correct Syntax would be "parameters"  - in Andrews example the "s" is missing.

    It took me quit a while to figure out why it was not working.

    Here is the correct Syntax (that is working in my modelfiles at least):

    library mylib
    section NN
    parameters corner=1
    include "foundry.scs" section=NN
    endsection NN

Reply
  • in reply to Andrew Beckett

    The correct Syntax would be "parameters"  - in Andrews example the "s" is missing.

    It took me quit a while to figure out why it was not working.

    Here is the correct Syntax (that is working in my modelfiles at least):

    library mylib
    section NN
    parameters corner=1
    include "foundry.scs" section=NN
    endsection NN

Children

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.