• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Hardware/Software Co-Development, Verification…
  3. Problem with XFRM_LINEAR Subcircuit

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 49
  • Views 14754
  • 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

Problem with XFRM_LINEAR Subcircuit

G Balaji
G Balaji over 16 years ago
I created a subcircuit using XFRM_LINEAR (subcircuit within subcircuit) and passed a parameter to this using SUBPARAM. But when I generate the netlist, It doesn't included the parameter on PARAM list and generated the following netlist.

This is resolved when I use 2 inductors with K instead of XFRM_Linear.

 Why?

.subckt X_TXl 1 2 3 4

K_TXl         L1_TXl L2_TXl 0.998

L1_TXl         1 2 {L1_X}

L2_TXl         3 4 250u

.ends X_TXl
  • Cancel
Parents
  • G Balaji
    G Balaji over 16 years ago

     To explain clearly what I did, please find attached snap shot of two models, where model – 1 uses two inductors and K. whereas in model – 2 XFRM_Linear is used instead.
    Given below are the netlists generated by model-1 and model-2 respectively and these netlists are created using “Create Netlist” command in capture project manager.


    Model - 1

    * source LIBRARY_TR
    .SUBCKT TR P1 P2 S1 S2 PARAMS: LVAL=10U
    C_C1         P1 N2433146  1n  TC=0,0
    L_L1_40         S1 S2  {Lval}  
    Kn_K2         L_L1_40 L_L2_40     0.998
    L_L2_40         N2433146 P2  250u  
    .ENDS

    Model – 2
    * source LIBRARY_XTR
    .SUBCKT XTR P1 P2 S1 S2 PARAMS: LVAL=10U
    X_TX1    N00597 P2 S1 S2 XTR_TX1
    C_C1         N00597 P1  10u  TC=0,0
    .ENDS

    .subckt XTR_TX1 1 2 3 4  
    K_TX1         L1_TX1 L2_TX1 1
    L1_TX1         1 2 {LVal}
    L2_TX1         3 4 10uH
    .ends XTR_TX1

    Absolutely Model-1 doesn’t have any problem. But, in Model-2, as you said, It suppose to include +PARAM: L1_X=10u in XTR_TX1 subcircuit and when X_TX1 is called the value LVAL need to passed to this subcircuit.
    I’m expecting this to happen automatically as I’m generating netlist from capture project manager.

    • Models.JPG
    • View
    • Hide
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • G Balaji
    G Balaji over 16 years ago

     To explain clearly what I did, please find attached snap shot of two models, where model – 1 uses two inductors and K. whereas in model – 2 XFRM_Linear is used instead.
    Given below are the netlists generated by model-1 and model-2 respectively and these netlists are created using “Create Netlist” command in capture project manager.


    Model - 1

    * source LIBRARY_TR
    .SUBCKT TR P1 P2 S1 S2 PARAMS: LVAL=10U
    C_C1         P1 N2433146  1n  TC=0,0
    L_L1_40         S1 S2  {Lval}  
    Kn_K2         L_L1_40 L_L2_40     0.998
    L_L2_40         N2433146 P2  250u  
    .ENDS

    Model – 2
    * source LIBRARY_XTR
    .SUBCKT XTR P1 P2 S1 S2 PARAMS: LVAL=10U
    X_TX1    N00597 P2 S1 S2 XTR_TX1
    C_C1         N00597 P1  10u  TC=0,0
    .ENDS

    .subckt XTR_TX1 1 2 3 4  
    K_TX1         L1_TX1 L2_TX1 1
    L1_TX1         1 2 {LVal}
    L2_TX1         3 4 10uH
    .ends XTR_TX1

    Absolutely Model-1 doesn’t have any problem. But, in Model-2, as you said, It suppose to include +PARAM: L1_X=10u in XTR_TX1 subcircuit and when X_TX1 is called the value LVAL need to passed to this subcircuit.
    I’m expecting this to happen automatically as I’m generating netlist from capture project manager.

    • Models.JPG
    • View
    • Hide
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information