ansLvsCompPrim netlisting procedure for auLvs

[anandganesan@gmail.com]

Hi
Can someone tell me how ansLvsCompPrim works and what is the logic
behind it?

Is it possible to create a similar functionality if I want to create a
custom device (with variable number of pins)?

Thanks.

Anand.

 

[Bernd Fischer]

ansLvsCompPrim takes the name and number of pins form the CDF
simInfo for auLvs.
Have you tried to modify it according to what you want?


Bernd

cdfId->simInfo->auLvs = '( nil
propMapping nil
netlistProcedure ansLvsCompPrim
instParameters (m l w)
componentName nmos
termOrder (D G S B)
deviceTerminals "D G S B"
permuteRule "(p D S)"
namePrefix "M"
)



anandganesan@gmail.com wrote:

Hi
Can someone tell me how ansLvsCompPrim works and what is the logic
behind it?

Is it possible to create a similar functionality if I want to create a
custom device (with variable number of pins)?

Thanks.

Anand.

 

[Andrew Beckett]

On 21 Feb 2006 10:21:20 -0800, "anandganesan@gmail.com" <anandganesan@gmail.com>
wrote:

Thanks Andrew. That does clarify a lot, but doesn't completely solve my
problem.

Yes, I am looking at symbol Pcell (inductor with flexible number of
taps). That is why I am not able to store pin information in the
auLvs->simInfo section. I do have access to the number of pins on the
CDF and can create the pin list using logic. I can also perform
extraction of the device as a blackbox using recognition shapes, but it
still needs to netlist suitably for LVS. I am using Assura.

Please give me an idea of how to implement a custom netlisting
procedure? A template would be helpful.

Thanks.

Anand.

OK, if you're using Assura, then it's not using ansLvsCompPrim - that's for
Diva. Assura directly goes from DFII to a vldb representation, but uses the
auLvs information to know how to do that.

Perhaps missing out the auLvs simInfo altogether might work with a symbol
pcell?

(wild guess, don't have time to try it right now).

Regards,

Andrew.

 

[Andrew Beckett]

Perhaps you're asking about netlisting something that has a pcell symbol, with
a variable number of pins?

Well, ansLvsCompPrim does not support this, and there's no public API for
writing your own netlisting procedure for Diva. Normally there's no need to...

If you have a variable number of pins, you'd have to extract these as different
devices in the Diva extract rules - and Diva extraction cannot have a variable
number of logical pins (it can have a variable number of physical pins though).
So you'd have to have a discrete number of different extraction statements in
the Diva extract rules for each different number of pins - and you'd have to
have some way of recognising them.

Assuming that you then have a discrete number of them, you could have a
symbol pcell (with a variable number of pins), and then a schematic pcell
which instantiated one of the discrete number of fixed-pin devices, depending
on the passed-in parameters.

That's the only way I can see this working. It could be done with a clever
custom netlisting procedure, but there's no support for that - so the best thing
is to use the additional level of hierarchy approach that I suggested.

This is of course assuming you've got a symbol pcell. If not, you can forget the
above!

Regards,

Andrew.

On Thu, 16 Feb 2006 09:40:02 +0100, Bernd Fischer <bernd.fischer@xignal.com>
wrote:

ansLvsCompPrim takes the name and number of pins form the CDF
simInfo for auLvs.
Have you tried to modify it according to what you want?


Bernd

cdfId->simInfo->auLvs = '( nil
propMapping nil
netlistProcedure ansLvsCompPrim
instParameters (m l w)
componentName nmos
termOrder (D G S B)
deviceTerminals "D G S B"
permuteRule "(p D S)"
namePrefix "M"
)



anandganesan@gmail.com wrote:
Hi
Can someone tell me how ansLvsCompPrim works and what is the logic
behind it?

Is it possible to create a similar functionality if I want to create a
custom device (with variable number of pins)?

Thanks.

Anand.

 

[Bernd Fischer]

Sorry I missed the word 'varibale' in you post.

Bernd

Bernd Fischer wrote:

ansLvsCompPrim takes the name and number of pins form the CDF
simInfo for auLvs.
Have you tried to modify it according to what you want?


Bernd

cdfId->simInfo->auLvs = '( nil
propMapping nil
netlistProcedure ansLvsCompPrim
instParameters (m l w)
componentName nmos
termOrder (D G S B)
deviceTerminals "D G S B"
permuteRule "(p D S)"
namePrefix "M"
)



anandganesan@gmail.com wrote:

Hi
Can someone tell me how ansLvsCompPrim works and what is the logic
behind it?

Is it possible to create a similar functionality if I want to create a
custom device (with variable number of pins)?

Thanks.

Anand.

 

[anandganesan@gmail.com]

Thanks Andrew. That does clarify a lot, but doesn't completely solve my
problem.

Yes, I am looking at symbol Pcell (inductor with flexible number of
taps). That is why I am not able to store pin information in the
auLvs->simInfo section. I do have access to the number of pins on the
CDF and can create the pin list using logic. I can also perform
extraction of the device as a blackbox using recognition shapes, but it
still needs to netlist suitably for LVS. I am using Assura.

Please give me an idea of how to implement a custom netlisting
procedure? A template would be helpful.

Thanks.

Anand.