• 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. ADE error when I try to load *.VCD file

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 16105
  • 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

ADE error when I try to load *.VCD file

Nhumai
Nhumai over 6 years ago

Hi , 

i simvision to dump out a *.vcd file and try to use that *.vcd file as an input  to my ADE/spectre simulation. 

I have 2 files 

rowdecode.vcd which dumped about by simvision

rowdecode.vcd_infor I create it  

both file are attached. 

I don't know why when I try to load them in ADE and run I got the error like 

ERROR (OSSGLD-18): The command character after '[' in the NLP expression '[10:0] $end ' is not a valid character. The command character is the first character after '[' in the NLP expression. It must be '?', '!', '#', '$', 'n', '@', '.', '~' or '+'. Enter a valid character as the command character.

               si: simin did not complete successfully.

ERROR (ADE-3016): Could not map schematic names in the stimulus file /import/proj4/ca18/OA/projects/sbf303/work_libs/e373035/cds/simulation/stimulus/rowdecode/rowdecode.vcd

        to the target simulator.

      ...unsuccessful.

Anyone know how to fix it please let me know 

thanks 

Nhumai 

rowdecode.vcd.txt

Fullscreen rowdecode.vcd_infor.txt Download
From:	Nhumai T Le <e373035@sbfsr072367.orl.lmco.com>
Sent:	Wednesday, June 26, 2019 3:44 PM
To:	Le, Nhumai T (US)

*This command is used to match the input and output vector syntax between VCD file and spice netlist.
*syntax: .alias VCD_bus_syntax signal_bus_syntax

.alias ra[*] ra<*>


*scope to take care of signals present in lower level hierarchy.In this testcase i have just placed 
buffertest as it contains top-level signals.

.scope tb_digleft_asic 

* .in, .out and .bi are used to define specified bus as input,output and bi-directional signals as is netlist.

.in clr prstsh ra[10:0] row_valid vrefl_m

*These parameters define used when you to converting digital vector to analog signal.
*These specify the rise time, fall time, logical input high, logical input low,logic output high, logic output 
low.
.trise  100
.tfall  100
.vih    3.3 
.vil    0.0
.voh    3.3 
.vol    0.0

*This sets the reference to time t=0 (where you grabbed the VCD signals from) .tdelay 0



*in addition to this if you have specified output vectors in VCD file then you need to "chkwindow" 
parameter to check output signal in the specified window range.

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

    My guess is that you used the wrong field to specify the files - I think you've used the Setup->Simulation Files and then used the Stimulus Files field on the first tab (Paths/Files) whereas you should have used these fields on the Vector Files tab:

    I got exactly the same error you did if I put these files in the Stimulus File field - that's incorrect usage, as that expects a spectre syntax file, not a VCD file.

    Regards,

    Andrew.

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

    My guess is that you used the wrong field to specify the files - I think you've used the Setup->Simulation Files and then used the Stimulus Files field on the first tab (Paths/Files) whereas you should have used these fields on the Vector Files tab:

    I got exactly the same error you did if I put these files in the Stimulus File field - that's incorrect usage, as that expects a spectre syntax file, not a VCD file.

    Regards,

    Andrew.

    • 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