AMS simulation error reporting

There's normally additional messages before that error in the log file which would provide more colour. Can you provide the entire log file from the simulator (that would also show which simulator version you're using which will be more important than the IC version, most likely).

Regards,

Andrew.

Hi,Andrew, I'm sorry to answer you too late. The log files are as follows. I can't get too much information from this log file.

ncelab(64): 14.10-s014: (c) Copyright 1995-2014 Cadence Design Systems, Inc.
TOOL: ncelab(64) 14.10-s014: Started on Jun 10, 2019 at 19:35:47 CST
ncelab
-snapshot DAC8bit_AMS.dac_8bit_test:config
-timescale 1ns/1ns
-discipline logic
-nowarn DLNOHV
-delay_mode None
-novitalaccl
-access +r
-errorMax 50
-messages
-status
-v93
-cdslib /home/IC/workspace/cds.lib
-noparamerr
-use5x4vhdl
-update
-amspartinfo /home/IC/simulation/dac_8bit_test/ams/hierarchy/psf/partition.info
-rnm_partinfo
-work DAC8bit_AMS
DAC8bit_AMS.dac_8bit_test:config
DAC8bit_AMS.cds_globals:dac_8bit_test_config
-logfile /home/IC/simulation/dac_8bit_test/ams/hierarchy/psf/ncelab.log

Elaborating the design hierarchy:
ERROR: terminated with error code 127
ncelab: *F,SPRSER: Spice/Spectre file parsing failed.
ncelab: Memory Usage - 46.6M program + 30.1M data = 76.8M total (Peak 76.8M)
ncelab: CPU Usage - 0.1s system + 0.1s user = 0.1s total (0.1s, 100.0% cpu)
TOOL: ncelab(64) 14.10-s014: Exiting on Jun 10, 2019 at 19:35:47 CST (total: 00:00:00)

OK, it suggests that you're running with an old version of INCISIVE (and probably an old IC version). You're using the unsupported 3-step rather than "UNL" (Unified Netlister) flow too.

Is there a reason why you're using such an old supported version? At the very least I would switch to using IC617 or IC618 and ideally XCELIUM1903 (at the very least INCISIVE152 latest hotfix) rather than trying to debug a problem which may have been resolved 5 years ago...

Andrew.

Hi，Andrew，Thank you very much for your reply.

But，I only have this version of the software , can not be updated, this version can not solve this problem?

I have no idea whether the problem can be resolved, since I can't see enough information to know what the problem actually is.

Having just looked back through  your post, I see you're using IC617, so there really is no good reason to be using such an old INCISIVE version.

However, I would suggest you try going to Simulation->Netlist and Run Options and picking "Unified Netlister" (I think that should be possible even with INCISIVE141 - I can't quite remember the minimum requirements). See if that fixes it.

Regards,

Andrew.

After setting up as you say, the simulator still reports errors. The error reports are as follows：

NING (OSSHNL-143): Incremental netlisting is not possible since the global
map file
'/home/IC/simulation/dac_8bit_test/ams/hierarchy/.tempProjectDir/dac_8bit_test/ams/config/netlist/digital/ihnl/globalmap', could
not be opened in the read mode
for IHNL version number comparison. Therefore
re-netlisting the entire design.

INFO (VLOGNET-60): The stimulus name mapped table will not be printed in the

"/home/IC/simulation/dac_8bit_test/ams/hierarchy/.tempProjectDir/dac_8bit_test/ams/config/netlist/digital/testfixture.verilog" file. To print the stimulus name
mapped table, set
simVerilogPrintStimulusNameMappingTable = t either in CIW or
the .simrc file
before invoking Verilog netlister.

INFO (VLOGNET-62): Database internal net names will be printed for floating
instance ports. To prevent
them from being printed, set
simVerilogProcessNullPorts = t either in CIW or
the .simrc file.

INFO (VLOGNET-64): All cellviews in the design will be printed in the Netlist
Configuration list.
If you want to print only those cellviews that need to be
re-netlisted in the
list, set simVerilogIncrementalNetlistConfigList = t either
in CIW or the
.simrc file.

INFO (VLOGNET-68): The initial state of stimulus of all inout pins is set to
"z". To get inout
pins with initial state of "0", set
hnlVerilogIOInitStimulusStr = "0"
either in CIW or the .simrc file.

*ERROR*: Error encountered while registering text designs in the configuration.
Refer to the following messages and correct the errors.
irun: *E,SPCERR: The program encountered one or more errors while processing the input SPICE file(s) in the AMSD flow. For details, see the following messages.

So where there any "following messages" that might give a clue? 

I still think  you would be better off getting a newer version of the simulator - there really isn't a good reason to stick with something this old. At the very least, the error reporting might be better. 

Or contact customer support - so at least we can see  your data. This is like trying to diagnose a problem with your car without being able to even see the engine.

Andrew.

Okay, thank you very much for your reply.