Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 14760
  • 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

Analog-Env Sim Error

tempVar

Hi. Here is my situation:

I worked on a schematic for a 2to4 decoder, saved and checked with no problem. Opened Analog Environment and hit run and simulate. Everything works with no errors.

I made a symbol for this 2to4 decoder. 

I then opened a new schematic, inserted a decoder. Opened Analog Environment, tried to run simulation... icfb told me to go to out output log (hspice.out) to check for the error, here is what I got:

 

Any help will be appreciated, thank you. 

 

 

  •  Hi tempVar,

     

    please don't start your circuits name with a number Hspice  can't handle it.

    Instead of "2to4..." rename the cell to "two2four..."  and it should be ok.

     

    Regards,

    Marc

  • Hello again. Thank you for your reply, your solution worked! 

    I do however have another problem now, When I update my symbols' names, the instances used in the main schematic do not update : ( Do I need to manually update them (or redo the schematic)? Or is there away to automatically update all instance cell names from their symbol cell names?

     

  • If you rename the cell in the library manager, you should make sure  you have the "update instances" check box checked.

    BTW, if an initial number is not legal in HSPICE, we really should fix the hspiceD netlister so that it maps leading numbers in subckt names. This is doable within the netlisting infrastructure; the netlister just needs to be told that it is illegal so that it will automatically map during netlisting. So you should report this to customer support so that we can get it implemented in the netlister.

    However, if it were me, I would avoid using names that begin with numbers or use any kind of special characters in the names, as these invariably need mapping for some tools. That mapping should work fine, but I tend to go for the "avoid any possible problem" approach and give them more conservative names.

    Regards,

    Andrew.

  • Hey. Thank you Andrew for your help and input. So I tried simply renaming them (and checking the "Update instances" button) but that did not work : (

    I did however manage to rename all of them using another technique:

     

    • I clicked on one instance of a component (say, my previously named "2to4decoder")
    • Hit 'q' 
    • Where it says "Apply To," i set it to "all" and "instance."
    • Finally I renamed it to "twTOfrDecoder." and hit "OK"

     

     I now have a schematic that I am able to simulate. Thank you guys for your help : )

  • Actually your method works. Sorry, it was an error on my part (edited the wrong library).

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.