Stats

  • Locked Locked
  • Replies 9
  • Subscribers 165
  • Views 24291
  • Members are here 0
More Content
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

[SOLVED] Problem with two versions of CADENCE

bluecat

Hi Everyone,

 I recently upgrade my Hard drive into a bigger one from 80 GB to 320G, everything was fine, basically I backup and clone the OS(windows XP) and the installed programs which include CADENCE 16.2 as well. Everything is working perfecrt, But recently we decide to upgrade to CADENCE 16.6 due to many designers are using CADENCE 16.3 and higher. The problem is that I installed CADENCE 16.6 and everything look normal, but there is a problem and it is giving me a error messages on windows. Maybe is because I update the hard drive and it mess up with the register or something. I used the "Cadence SPB switch release" and then, When I try to open DESING ENTRYCIS (ORCAD) the following message apperas "Capture.exe - Entry Point Not Found,  X  The procedure entry point ?find@SBString@@QEHPBDH_N@Z cold not be located in the dynamic link library SBaseMD_sh.dll". And when I try to open allegro this message show up "allegro.exe - Entry Point Not Found, X The procedure entry point obSearch could not be located in the dynamic link library _cadencehelp.dll.". I tried to re-install all the application again and again, and I am still getting the same error. Please could anybody help me to fix this issue. I really wnat to try the CADENCE 16.6, because I read the new features that it has, and they look awsome.

Thanks in advance for the help.

 

Regards.

 

 

 

  • chads108

    Yes, try what Steve said.  It could be something to do with your permissions on your PC.

    If that doesn't work, it still sounds like your environment variable path has the path to the Cadence install is hard coded.  I can't see it from your picture and really the only way you can see it is to go to My Computer, right click Properties and in the Advanced tab select Environment Variables.  Highlight the PATH variable and select edit.  The Cadence install path should look something like the the attached picture of my path.

     

  • bluecat

     nothing yet, I just notice something else. when I try to change from one release to another release on the  "Cadence SPB Switch Release"the outcomming text below looks identical for the 16.2 version and 16.6. Maybe those have to be changes. thi is the text:

     

    CDSROOT = C:\Cadence\SPB_16.6

    PATH = C:\Program Files\STMicroelectronics\st_toolset\asm;C:\Program Files\Microchip\mplabc18\v3.46\mpasm;C:\Program Files\Microchip\mplabc18\v3.46\bin;C:\Program Files\Microchip\xc16\v1.11\bin;C:\Program Files\Microchip\xc8\v1.20\bin;C:\Program Files\Atmel\AVR Tools\AVR Toolchain\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Cadence\SPB_16.2\tools\bin;C:\Cadence\SPB_16.2\tools\libutil\bin;C:\Cadence\SPB_16.2\tools\fet\bin;C:\Cadence\SPB_16.2\tools\pcb\bin;C:\Cadence\SPB_16.2\tools\PSpice;C:\Cadence\SPB_16.2\tools\PSpice\Library;C:\Cadence\SPB_16.2\tools\Capture;C:\Cadence\SPB_16.2\tools\specctra\bin;C:\Program Files\Microchip\MPLAB C32 Suite\bin;C:\PROGRA~1\PICC;C:\Program Files\Prime Sense\Sensor\bin;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\OpenNI\bin;C:\Program Files\PrimeSense\NITE\bin;C:\Program Files\P-CAD 2006 Viewer\;C:\Program Files\Raisonance\Ride\bin%CDSROOT%\openaccess\bin\win32\opt;%CDSROOT%\tools\bin;%CDSROOT%\tools\capture;%CDSROOT%\tools\pspice;%CDSROOT%\tools\fet\bin;%CDSROOT%\tools\specctra\bin;%CDSROOT%\tools\pcb\bin;%CDSROOT%\tools\libutil\bin;C:\Program Files\Microchip\mplabc18\v3.46\mpasm;C:\Program Files\Microchip\mplabc18\v3.46\bin;C:\Program Files\COSMIC\CXVLE_16K;C:\Program Files\COSMIC\CXSTM8_EVAL;C:\Program Files\COSMIC\CXSTM8_32K


    CDSROOT = C:\Cadence\SPB_16.2

    PATH = C:\Program Files\STMicroelectronics\st_toolset\asm;C:\Program Files\Microchip\mplabc18\v3.46\mpasm;C:\Program Files\Microchip\mplabc18\v3.46\bin;C:\Program Files\Microchip\xc16\v1.11\bin;C:\Program Files\Microchip\xc8\v1.20\bin;C:\Program Files\Atmel\AVR Tools\AVR Toolchain\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Cadence\SPB_16.2\tools\bin;C:\Cadence\SPB_16.2\tools\libutil\bin;C:\Cadence\SPB_16.2\tools\fet\bin;C:\Cadence\SPB_16.2\tools\pcb\bin;C:\Cadence\SPB_16.2\tools\PSpice;C:\Cadence\SPB_16.2\tools\PSpice\Library;C:\Cadence\SPB_16.2\tools\Capture;C:\Cadence\SPB_16.2\tools\specctra\bin;C:\Program Files\Microchip\MPLAB C32 Suite\bin;C:\PROGRA~1\PICC;C:\Program Files\Prime Sense\Sensor\bin;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\OpenNI\bin;C:\Program Files\PrimeSense\NITE\bin;C:\Program Files\P-CAD 2006 Viewer\;C:\Program Files\Raisonance\Ride\bin%CDSROOT%\openaccess\bin\win32\opt;%CDSROOT%\tools\bin;%CDSROOT%\tools\capture;%CDSROOT%\tools\pspice;%CDSROOT%\tools\fet\bin;%CDSROOT%\tools\specctra\bin;%CDSROOT%\tools\pcb\bin;%CDSROOT%\tools\libutil\bin;C:\Program Files\Microchip\mplabc18\v3.46\mpasm;C:\Program Files\Microchip\mplabc18\v3.46\bin;C:\Program Files\COSMIC\CXVLE_16K;C:\Program Files\COSMIC\CXSTM8_EVAL;C:\Program Files\COSMIC\CXSTM8_32K

     

    For both version it is calling the  "C:\Cadence\SPB_16.2".

     

    Any ideas?

  • chads108

     You need to edit your path.  Based on what you posted, the Cadence tools paths are defined twice.  Remove the hard coded paths, i.e. C:\Cadence\SPB_16.2... and leave the %CDSROOT% paths.

    Chad

  • bluecat

     Thanks all for your help,

    I was able to to make it work, as Chad said I edit the VARIABLE systems instead of the USER variables(see picture) and everything is working now I am able to swithc from 16.2and 16.6 without a problem.  I  just did: start > my computer (right click) > Properties > Advance > Environment Variables > System variables >(high light) PATH > Edit. and change all "C:\Cadence\SPB_16.2" to %CDSROOT%, then ok to everything and that's it everything is working now.

Cadence Guidelines

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.