Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 6880
  • 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

Help: AMS Mixed-signal simulation error reported ERROR (VACOMP-2070)

feiyufox

cadence ic618 + INCISIVE152.+SPECTRE201

When I running AMS，Mixed signal simulation, Error reported as below:

Error found by spectre during circuit read-in.
    ERROR (VACOMP-2070):
        "/edatools/INCISIVE152/tools/spectre/etc/ahdl/disciplines.vams", line
        251: Detected unknown type for identifier: F. Check the validity of the
        type.
    ERROR (VACOMP-2070):
        "/edatools/INCISIVE152/tools/spectre/etc/ahdl/disciplines.vams", line
        251: Detected unknown type for identifier: F. Check the validity of the
        type.
    ERROR (SPECTRE-357): AMS Analog Elaboration has exited with error.
        Simulation will terminate.

spectre terminated prematurely due to fatal error.
ncsim: *F,RNAERR: The simulator terminated with an analog initialization error.
ncsim: Memory Usage - 35.7M program + 442.5M data = 478.2M total (478.2M Peak)
ncsim: CPU Usage - 0.3s system + 3.7s user = 4.0s total (4.1s, 97.0% cpu)
TOOL:    irun(64)    15.20-p001: Exiting on Apr 11, 2023 at 14:46:13 CST  (total: 00:00:22)

May I ask what the problem is? How to solve it?

Parents
  • Andrew Beckett

    First of all, it doesn't make sense to be using INCISIVE152. That's an obsolete 8-year old version of the digital simulator. You should use a recent XCELIUM version instead.

    The issue here is quite likely (I'm guessing a bit here) to be because you've used the identifier F elsewhere and that's clashing with the attempt to define F as an access function for Force in the disciplines.vams file. It's hard to know without seeing your models - but that's what I'd look for. Perhaps talking to customer support would be a good idea.

    Andrew

Reply
  • Andrew Beckett

    First of all, it doesn't make sense to be using INCISIVE152. That's an obsolete 8-year old version of the digital simulator. You should use a recent XCELIUM version instead.

    The issue here is quite likely (I'm guessing a bit here) to be because you've used the identifier F elsewhere and that's clashing with the attempt to define F as an access function for Force in the disciplines.vams file. It's hard to know without seeing your models - but that's what I'd look for. Perhaps talking to customer support would be a good idea.

    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.