Stats

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

integrate ansys Electromagnetic Suite 16 problem

rockyicer

hello, guys

    I am trying to integrate ansys Electromagnetic Suite 16 into cadence. I have installed Ansys Electromagnetic Suite 16 and the ECAD (which is the interface to the virtuoso)  and do exactly what the configure says as follows:

1)Initial Setup
a) Environment variable settings
ANSYSEM_INSTALL_DIR=/eda/ansys/AnsysEM17.0/Linux64
bash: export PATH=${ANSYSEM_INSTALL_DIR}:$PATH
csh: setenv PATH ${ANSYSEM_INSTALL_DIR}:$PATH

SI_INTEGRATE4_DIR=/eda/ansys/ECADTranslators2016.0/Linux/LayoutIntegrations


(b)Add the code in the file ${SI_INTEGRATE4_DIR}/cdsinit_integ.txt to your .cdsinit file as follows:

let( (contextFile layoutIntegDir)
if( layoutIntegDir = getShellEnvVar("SI_INTEGRATE4_DIR") then
contextFile = strcat(layoutIntegDir "/VirtuosoTranslator.cxt")
when( isFile(contextFile)
loadContext(contextFile)
callInitProc("VirtuosoTranslator")
)
else
printf("SI_INTEGRATE4_DIR environent variable is not set.\n")
)
)

 

when I open the layout , there is no menu for ansys which there should be according to the guide. and I found that there are errors in the CIW, which I can't understand as follows:

*WARNING* context read failure: can't read 32-bit context on 64-bit platform

*** INTERNAL ASSERTION FAILURE *** (Mismatch between RESTORE/REBIND macros -) in file ilSys/context.c line 5832

Please copy down the error message and notify Cadence!

*Error* ilAssert: Assertion Failure

In the /eda/ansys/ECADTranslators2016.0/Linux/LayoutIntegrations  folder, there is a file VirtuosoTranslator.cxt and a folder name 64bit which contain the file VirtuosoTranslator.cxt as the same name in the folder /eda/ansys/ECADTranslators2016.0/Linux/LayoutIntegrations, I have changed the VirtuosoTranslator.cxt. but the error still occurs.

anyone knows what is going on here, please enlighten me. thanks in advance!

Parents

  • You missed out the fairly important piece of information - which version of the  IC tools (Virtuoso) are you using? Help->About will give the subversion.

    In general, if the directory structure of the context files is correct, attempting to load the path to the 32-bit context file should automatically switch across to use the path for the 64bit context. No need to change the path you're loading. If you directly give the path to the 64bit context, that would work too - if it's really a 64-bit context - but in general that shouldn't be necessary.

    The second message is a bit strange - it's come up a few times, but mostly with internal builds. So knowing the version of the IC tools is quite important here.

    Note that I know nothing about the ANSYS tools - and the support for those would have to come from ANSYS rather than Cadence... (they can report it to us if there's a problem they can't resolve).

    Regards,

    Andrew.

Reply

  • You missed out the fairly important piece of information - which version of the  IC tools (Virtuoso) are you using? Help->About will give the subversion.

    In general, if the directory structure of the context files is correct, attempting to load the path to the 32-bit context file should automatically switch across to use the path for the 64bit context. No need to change the path you're loading. If you directly give the path to the 64bit context, that would work too - if it's really a 64-bit context - but in general that shouldn't be necessary.

    The second message is a bit strange - it's come up a few times, but mostly with internal builds. So knowing the version of the IC tools is quite important here.

    Note that I know nothing about the ANSYS tools - and the support for those would have to come from ANSYS rather than Cadence... (they can report it to us if there's a problem they can't resolve).

    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.