• 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. Custom IC Design
  3. Compilation error of verilogAMS --> ncvlog: *F,DLCSYN Syntax...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 2517
  • 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

Compilation error of verilogAMS --> ncvlog: *F,DLCSYN Syntax error 'DEFINE NCSIMRC

RFStuff
RFStuff over 4 years ago

Dear All,

I wrote a verilogAMS code and then tried to compile it. But I see the following error in Parser Log:-

ncvlog(64): 15.20-s086: (c) Copyright 1995-2020 Cadence Design Systems, Inc.
DEFINE NCSIMRC ( ./ncsimrc, ~/.ncsimrc )
|
ncvlog: *F,DLCSYN (/P/cadence/installs/INCISIVE152/tools.lnx86/inca/files/hdl.var,4): cds.lib Syntax error 'DEFINE NCSIMRC ( ./ncsimrc, ~/.ncsimrc )'.

Could anybody please tell how to fix this issue ?

Kind Regards,

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    This looks as if you have something strange in your cds.lib. I can get exactly the same error by adding:

    SOFTINCLUDE $AMSHOME/tools/inca/files/hdl.var

    (could be INCLUDE) to my cds.lib - it makes no sense to include an hdl.var from a cds.lib file (the syntax is similar, but they serve different purposes). So please check your cds.lib for inclusion of the standard hdl.var - and remove it if needed.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    This looks as if you have something strange in your cds.lib. I can get exactly the same error by adding:

    SOFTINCLUDE $AMSHOME/tools/inca/files/hdl.var

    (could be INCLUDE) to my cds.lib - it makes no sense to include an hdl.var from a cds.lib file (the syntax is similar, but they serve different purposes). So please check your cds.lib for inclusion of the standard hdl.var - and remove it if needed.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • RFStuff
    RFStuff over 4 years ago in reply to Andrew Beckett

    Thanks a lot Andrew.

    That was indeed the case. But, I am seeing an interesting issue when I create the symbol after complilation.

    If there is an input or output net named with underscore (like t_plus), this net shows in the symbol as tplus (bar over plus) like shown below.  How to fix this.

    Kind Regards,

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to RFStuff

    If you open the symbol for edit, and select those labels, they will have the "overbar" on the form checked. If you uncheck it, normal service will be resumed.

    That's not the default behaviour, nor is it the default for the normal symbol generation "tsg" template. If you check which template is being used:

    envGetVal("schematic" "tsgTemplateType")

    and the location of each template by entering:

    tsgTemplateMasters

    Look to see if the template used (presumably not one in the installation unless it's been edited) has isOverbar(t) for any of the labels. If so, that's the reason why the label has been created with overbar turned on. Looking at my tsgTemplateMasters:

    (("digital" "/export/home/apps/IC618_isr/tools.lnx86/dfII/samples/symbolGen/default.tsg")
    ("analog" "/export/home/apps/IC618_isr/tools.lnx86/dfII/samples/symbolGen/artist.tsg")
    ("artist" "/export/home/apps/IC618_isr/tools.lnx86/dfII/samples/symbolGen/artist.tsg")
    ("PCB" "/export/home/apps/IC618_isr/tools.lnx86/dfII/samples/symbolGen/package.tsg")
    ("metric" "/export/home/apps/IC618_isr/tools.lnx86/dfII/samples/symbolGen/metric.tsg")
    )

    All of the files above have isOverbar(nil). There is also the envGetVal("schematic" "pinLabelOverbar") and envGetVal("schematic" "pinLabelSetOverbar") - but these don't have an effect if the isOverbar() is in the TSG file (as far as I know).

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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