• 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. Importing a VHDL file into Virtuoso for mixed signal si...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 128
  • Views 19542
  • 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

Importing a VHDL file into Virtuoso for mixed signal sim

FernandoLeite
FernandoLeite over 13 years ago

Hello, I am experiencing quite a few problems when trying to include a VHDL file into a mixed signal testbench to verify its functionalities. The testbench is created (config + schematic), the vhdl file was imported with  "VHDL Import" (following Cadence Help Docs...). The tool creates 3 cell views: entity, rtl and symbol. After that I set the binding view in Hierarchy Editor to "entity" and try to run the simulation (note that "entity" view has only the entity part of VHDL code, and "rtl" view has the actual behavioural code).

 I get an error message stating: "ncelab: *F,CUIVEN: Illegal view named entity specified for binding in sil180_adc_spi.el_spi_static:entity."

 Ok, trying to solve this I create a "vhdl" cellview for the same block, containing the whole VDHL code (entity + rtl). This time, when I modify this new "vhdl" view, the tool automatically updates the other two views ("entity" and "rtl"). Going back to Hierarchy Editor I set the current view of the block to "vhdl" and try to run the sim again. 

This time I get the following errors: 

ncelab: *W,CUNOUN: Cannot find any unit under sil180_adc_spi.el_spi_static:vhdl in the design libraries.
ncelab: *E,DLCSMD: Dependent checksum entity SIL180_ADC_SPI.EL_SPI_STATIC (AST) doesn't match with the checksum that's in the header of: architecture SIL180_ADC_SPI.EL_SPI_STATIC:RTL (AST).

I really tried to find out WHAT this error means. Can anyone give a hand here?

 Thanks in advance.

=)

  • Cancel
  • Yigit
    Yigit over 12 years ago

    Hello,

     I am facing the identical problem. I wonder if you could somehow figure it out.

    I'd really appreciate it if you could help.

    Thank you

    Yigit

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jsaenznoval
    jsaenznoval over 10 years ago

    Did you use git as version control program?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • HoWei
    HoWei over 4 years ago

    Hi all,

    the same error message I get in year 2020 with IC6.1.8 AMS simulations plus external VHDL code.

    I only get the error if I run "2 or more jobs in parallel" - if I run only "1 job" then the error does not appear.

    Loading snapshot ATIC543_tb.NOX_ADC14B_tb:config ..................
    xmsim: *E,DLCSMD: Dependent checksum module worklib.cds_globals:vams (VST) doesn't match with the checksum that's in the header of: snapshot ATIC543_tb.NOX_ADC14B_tb:config (SSS).
    xmsim: *F,NOSIMU: Errors initializing simulation 'ATIC543_tb.NOX_ADC14B_tb:config'.

    I use precompiled "External HDL" in the hierarchy editor.

    Interestingly, the "xrun.log" error message link of the run "Interactive.9" points to the previous version "Interactive.8" worklib.cds_globals:vams (see screenshot):

    There are multiple "cds_globals.vams" files:

    - in simulation folder "psf/<testname>/netlist"  (e.g. ../Interactive.9/psf/Output_test/netlist/cds_globals.vams)

    - and in each subfolder for each run "<simulation_run>/<testname>/netlist" (e.g. ../Interactive.9/1/Output_test/netlist/cds_globals.vams)

    Has anyone an idea what bad setting is causing this ? 

    Why/what is creating the checksum ?

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

    I found some old reports of this (very old - over 15 years) with cds_globals which were resolved by removing old *.pak files in the library (which shouldn't be needed and it's not obvious in this case which should be removed). The article Cause and cure for the DLCSMD error doesn't help enormously... (there are quite a few cases related to DLCSMD but not sure why it would show up here).

    It's probably best to contact customer support - we may need to do some digging around.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • HoWei
    HoWei over 4 years ago in reply to HoWei

    The below setting seem to be required to avoid dependencies on previous runs.

    It seems that now multiple runs are started, but for some runs the following error exists:

    xmsim: *W,DLWNEW: Intermediate file connect worklib.ddiscrete_dynsup_full_fast_ie2_cr:vams (VST)
     is newer than expected by snapshot ATIC543_tb.NOX_ADC14B_tb:config (SSS)
      actual:   Mon Nov  9 12:49:43 2020
      expected: Mon Nov  9 12:49:41 2020.
    xmsim: *W,DLWNEW: Intermediate file module worklib.cds_globals:vams (VST)
     is newer than expected by snapshot ATIC543_tb.NOX_ADC14B_tb:config (SSS)
      actual:   Mon Nov  9 12:50:07 2020
      expected: Mon Nov  9 12:49:40 2020.
    xmsim: *E,DLNORD: Intermediate file for module worklib.cds_globals:vams (SIG) <0x13aeccd1> could not be read (no such object).

    xmsim: *F,NOSIMU: Errors initializing simulation 'ATIC543_tb.NOX_ADC14B_tb:config'.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • HoWei
    HoWei over 4 years ago in reply to HoWei

    Hi,

    thanks Andrew - after deleting the existing *.pak files (basically deleting the ./xcelium.d folder) the simulation is running with multiple jobs !

    • 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