• 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. RF Design
  3. HBAC analysis issue, while simulating a mixer from Cadence...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 64
  • Views 17341
  • 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

HBAC analysis issue, while simulating a mixer from Cadence examples

apaj
apaj over 11 years ago

Hello, 

I am having two errors in setting up the HBAC analysis. I am trying to run simulations described in Cadence examples/RFworkshop/docs for a mixer.

HB analysis runs smoothly, but when I try to run the HBAC - I get the following messages:

ERROR (SFE-874): "input.scs" 76: Unexpected identifier "annotate". Expected equals.

ERROR (SFE-678): "input.scs" 76: Statement is not in Spectre format. Use `simulator lang = spice' to introduce spice language sections.

I tried changing the default setting of the Annotate Parameter in ADE->HBAC->Options form, but with no success - the same thing happens. I have set up all the other stuff as shown in Cadence example.

Could you please try to help me out and let me know how to solve these errors?

Thank you for your time.

  • Cancel
Parents
  • apaj
    apaj over 11 years ago

     Hello.

    Thank you for a through explanation and sorry for a late answer - some paperwork needed to be taken care of.

    I ventured into the rfLib folder and there I found both balun and balun_ideal. Each of these has two folders (symbol and veriloga) and prop.xx. The symbol folders for each look the same: they both contain a master.tag file which are identical. Nevertheless, the difference appears in balun_ideal/veriloga folder - it's empty! On the other hand balun/verliga contains master.tag, pc.db, veriloga.cd%, veriloga.cdb and veriloga.va. So - this is where the error was coming from.

    Is there a way for me to obtain the missing files? 

    Or, can I just keep using balun instead of balun_ideal? As far as I can see, the only difference is that balun_ideal has an offset input port - so if I give a DC voltage offset to the input signal of balun - should it make at least they look the same?

    As far as the sofware version is considered, here it is:

    icfb -W
    sub-version 5.10.41.500.6.151

    Regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • apaj
    apaj over 11 years ago

     Hello.

    Thank you for a through explanation and sorry for a late answer - some paperwork needed to be taken care of.

    I ventured into the rfLib folder and there I found both balun and balun_ideal. Each of these has two folders (symbol and veriloga) and prop.xx. The symbol folders for each look the same: they both contain a master.tag file which are identical. Nevertheless, the difference appears in balun_ideal/veriloga folder - it's empty! On the other hand balun/verliga contains master.tag, pc.db, veriloga.cd%, veriloga.cdb and veriloga.va. So - this is where the error was coming from.

    Is there a way for me to obtain the missing files? 

    Or, can I just keep using balun instead of balun_ideal? As far as I can see, the only difference is that balun_ideal has an offset input port - so if I give a DC voltage offset to the input signal of balun - should it make at least they look the same?

    As far as the sofware version is considered, here it is:

    icfb -W
    sub-version 5.10.41.500.6.151

    Regards.

    • 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