Stats

  • Locked Locked
  • Replies 11
  • Subscribers 127
  • Views 22162
  • 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

model card vith a verilogA model through spectre

Fabb

Hello,

I would like to run my own verilogA model with spetcre through a model card approach.

Nevertheless my model paramaters are not recognized, so not took into account in the simulation

#------------------------mymodel.va
module mymodel(T1,T2);
    
    inout T1, T2;
    electrical T1, T2;

    // instance parameters
    parameter real    ip1=1;
    //Technology Parameters
    parameter real tp1=1;
        analog begin
        @(initial_step)
        begin
            $strobe("----> mymodel");
            $display("Instance parameters: ip1=%r, ip1);
            $display("Technology parameters: tp1=%r , tp1);
        end
    endmodule

#------------------------model card
simulator lang=spectre

library test

section means
    parameters efftp1 = 777
        include "model_cards.scs" section=core
endsection means


section core
    ahdl_include "mymodel.va"        
    model device1 mymodel
        +tp1 = efftp1
endsection core
endlibrary

#------------------------cdf parameters
((nil name "ip1" paramType "string" defValue "1" prompt "ip1" choices nil parseAsNumber t units "lengthMetric" use nil display nil editable nil dontSave nil callback nil storeDefault t parseAsCEL t) (nil name "model" paramType "string" defValue "" prompt "model name" choices nil parseAsNumber nil units nil use nil display nil editable nil dontSave nil callback nil storeDefault nil parseAsCEL t))
(nil spectre (nil modelParamExprList "" optParamExprList "" opParamExprList "" stringParameters "" propMapping "" termMapping "nil T1 \\:1 T2 \\:2" termOrder "T1 T2" componentName "" instParameters "radius" otherParameters "model" netlistProcedure "") hspiceD (nil opParamExprList "" optParamExprList "" propMapping "" termMapping "" termOrder "" namePrefix "" componentName "" instParameters "" otherParameters "" netlistProcedure "") auLvs (nil namePrefix "" permuteRule "" propMapping "" deviceTerminals "" termOrder "" componentName "" instParameters "" otherParameters "" netlistProcedure "") auCdl (nil dollarEqualParams "" dollarParams "" modelName "" namePrefix "" propMapping "" termOrder "" componentName "" instParameters "" otherParameters "" netlistProcedure "") ams (nil isPrimitive "" extraTerminals "" propMapping "" termMapping "" termOrder "" componentName "" excludeParameters "" arrayParameters "" stringParameters "" referenceParameters "" enumParameters "" instParameters "" otherParameters "" netlistProcedure ""))
(nil paramLabelSet nil opPointLabelSet nil modelLabelSet nil paramDisplayMode nil paramEvaluate "nil nil nil nil nil" paramSimType nil termDisplayMode nil termSimType nil netNameType nil instDisplayMode nil instNameType nil)
(nil doneProc "" formInitProc "" promptWidth 175 fieldWidth 350 buttonFieldWidth 340 fieldHeight 35)

#------------------------error message

tp1 not recognized in mymodel.va


How should I proceed to allow parameters to be modified in a modelCard.

Regards,

Fabrice

Parents

  • I was searching for where I'd answered this (the attributes needed) before, and realised that you've appended to the same thread where I'd answered it already!

    With the attributes in the post, it tells spectre which parameters are instance parameters (and the rest are model parameters) - and having done that you can then specify a model card. You would have to include the veriloga model via a model file too (you can't really have it as a view, because you want the module to be generic and not just for that view). So you'd have your transistor symbol with the CDF set up with all the instance parameters you want to be able to pass to the model, and the spectre simulation information set up to netlist those parameters, and with the model parameter set to "nmos1" or whatever you've called it. You'd have a spectre view (copy of the symbol) to tell it to stop at that point. You could (say) copy from nmos4 in analogLib and then change the CDF parameters to suit your needs (Tools->CDF->Edit and set the CDF type to "Base").

    Then you'd have a file which you'd add to your model files - say "myBsimcmg.scs" which contains:

    ahdl_include "/path/to/bsimcmg.va"

    As well as referencing your model file.

    Regards,

    Andrew.

Reply

  • I was searching for where I'd answered this (the attributes needed) before, and realised that you've appended to the same thread where I'd answered it already!

    With the attributes in the post, it tells spectre which parameters are instance parameters (and the rest are model parameters) - and having done that you can then specify a model card. You would have to include the veriloga model via a model file too (you can't really have it as a view, because you want the module to be generic and not just for that view). So you'd have your transistor symbol with the CDF set up with all the instance parameters you want to be able to pass to the model, and the spectre simulation information set up to netlist those parameters, and with the model parameter set to "nmos1" or whatever you've called it. You'd have a spectre view (copy of the symbol) to tell it to stop at that point. You could (say) copy from nmos4 in analogLib and then change the CDF parameters to suit your needs (Tools->CDF->Edit and set the CDF type to "Base").

    Then you'd have a file which you'd add to your model files - say "myBsimcmg.scs" which contains:

    ahdl_include "/path/to/bsimcmg.va"

    As well as referencing your model 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.