In the Assembler corner UI: Can we make one corner variable dependent on another variable?

Stephan,

This is not that straightforward because you can't make it a function - e.g. using axlGetCornerNameForCurrentPointInRun() in a global variable expression because that doesn't work (I have CCR 2298397 asking for this). This function can only reused in output expressions and output ocean script measurements.

The alternative might have been if we had support for "paramset" type links between parameters in complex corners (i.e.corners with sweeps) so that you could link two variables/sections with the same number of sweeps. Right now that can only be done by expanding the corners (you can expand as param set).

One possibility would be to include a different model file with sections rather than the real resistor model files, which looked like this:

library myresistors {
  section fast 
    include "realmodelfile.scs" section=fast
    parameters rtrim=40
  endsection fast
  section slow 
    include "realmodelfile.scs" section=slow
    parameters rtrim=0
  endsection fast
  section typ 
    include "realmodelfile.scs" section=typ
    parameters rtrim=0
  endsection typ
endlibrary myresistors

I didn't try this, but I think it should work in principle.

Andrew

Many thanks, Andrew. My current workaround is indeed to have groups of corners like all the ones with slow+trim=xxx, etc. Also the idea of paramesets came to my mind, but was not working. The file idea is good too, but our model file setup is complex. Maybe this is the way to go.

Dear StephanWeber,

StephanWeber said:

How can I set trim in corner UI according to the resistor corner?? If need something like a function taking R corner section  value string as input and using a case structure to deliver the right integer value for trim.

As perhaps you are aware Stephan, one means of providing this functionality is to pass a variable from one simulation to another using calcVal(). In fact, there are several means to provide a calibration simulation prior to a "main" simulation using the calibrated value from the calibration simulation at URL:

https://support.cadence.com/apex/articleattachmentportal?id=a1O0V000006AicEUAS&pageName=ArticleContent&attachId=0690V000003i7fqQAA&sq=null&caseSessionKey=null

It seems this is a more robust solution than parsing a model corner as your ability to parse the process case for resistor type may vary from process node to process node or PDK. Including a calibration run prior to the  main simulation guarantees the appropriate calibration word will be chosen for any process and environment. This method also more closely emulates the actual circuit as, in reality, some type of calibration will be performed using your sense resistor.

Just a thought...

Shawn

Dear StephanWeber,

StephanWeber said:

How can I set trim in corner UI according to the resistor corner?? If need something like a function taking R corner section  value string as input and using a case structure to deliver the right integer value for trim.

As perhaps you are aware Stephan, one means of providing this functionality is to pass a variable from one simulation to another using calcVal(). In fact, there are several means to provide a calibration simulation prior to a "main" simulation using the calibrated value from the calibration simulation at URL:

https://support.cadence.com/apex/articleattachmentportal?id=a1O0V000006AicEUAS&pageName=ArticleContent&attachId=0690V000003i7fqQAA&sq=null&caseSessionKey=null

It seems this is a more robust solution than parsing a model corner as your ability to parse the process case for resistor type may vary from process node to process node or PDK. Including a calibration run prior to the  main simulation guarantees the appropriate calibration word will be chosen for any process and environment. This method also more closely emulates the actual circuit as, in reality, some type of calibration will be performed using your sense resistor.

Just a thought...

Shawn