Stats

  • Locked Locked
  • Replies 14
  • Subscribers 126
  • Views 16979
  • 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

Strange numbers in Virtuoso 6.1.5

JulianJ

 Hello,

I am seeing some strange number errors in Virtuoso 6.1.5.

In the ADE, I type  "1p" as the value for a variable and when set it appears as "1e122", "100f" becomes "1e155", "1f" becomes "1e155".

A similar error is also appearing on the drain diffusion area calculated on the FETs I am placing in my schematics, with the calculated area being displayed and netlisted as "480e155", when I think it should be "480f".

 I tried upgrading my instalation from  IC6.1.5-64b.500.1 to IC6.1.5-64b.500.9, but still have the same problem.

 Any help appreciated.

Julian

Parents

  • Julian,

    After writing some C code (replicating what's going on in the tools) and some experimentation, I now see the same problem when I'm running on my RHEL6.1 machine, and running virtuoso in 64 bit mode. It doesn't happen for me in 32 bit mode. Perhaps you can try running "virtuoso -32" to see if that helps? The same behaviour is true for my little C program; compiled in 32 bit mode, it works fine, but compiled in 64 bit mode I see the problem.

    I believe I understand the root cause in the code as to why this is happening (and I have an alternative implementation which seems to fix it), so I will file a CCR to get this fixed. I'll post the CCR number once I've done that.

    Regards,

    Andrew.

Reply

  • Julian,

    After writing some C code (replicating what's going on in the tools) and some experimentation, I now see the same problem when I'm running on my RHEL6.1 machine, and running virtuoso in 64 bit mode. It doesn't happen for me in 32 bit mode. Perhaps you can try running "virtuoso -32" to see if that helps? The same behaviour is true for my little C program; compiled in 32 bit mode, it works fine, but compiled in 64 bit mode I see the problem.

    I believe I understand the root cause in the code as to why this is happening (and I have an alternative implementation which seems to fix it), so I will file a CCR to get this fixed. I'll post the CCR number once I've done that.

    Regards,

    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.