Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
has anyone have an issue with ipcBeginProcess? i have an exe program that need to be run from Allegro, running the exe outside Allegro does it job, but when calling it from allegro it does not work at all (not being called to be exact), is there an issue of ipcBeginProcess not working in Allegro win7 64 bit
i tried this ipcBeginProcess("notepad") and it is working and using ipcBeginProcess in an XP 32 bit machine is also working
*** shell is not an option since i need to run the exe without showing the cmd console window and I need to know when exe program finished its job
edit: using shell aside from the cmd console window was being shown the exe program was working
I have the same problem, after switching to windows 7 64-bit. The script was working on windows xp 32-bit.Did you find a solution to the problem?
when trying to start perl i get cid = ipcBeginProcess("perl.exe") ipcReadProcess(cid)"Cannot create child process 'perl.exe '; Error code: 50\n"
when running dir i get: cid = ipcBeginProcess("dir") ipcReadProcess(cid)"Cannot create child process 'dir '; Error code: 2\n"
Does anyone have a clue about those error codes?
In reply to Adamsen:
try giving a fully qualified path to perl.exe
dir is a builtin command to cmd.exe. I would suggest using the Skill function getDirFiles to get a directory listing.
In reply to fxffxf:
I gave it a go, but no luck. I also had made sure that perl was in the correct PATH before. But changing to full path did not do the trick (if I did it right)
pp = "c:\\Perl64\\bin\\perl.exe" pid = ipcBeginProcess(pp) ipcReadProcess(pid)"Cannot create child process 'c:\\Perl64\\bin\\perl.exe '; Error code: 50\n"
The example with dir, was only to try an other command, which resultet in an other error code. I have tried to find information about these error codes, but no luck so far. But I didnt actually think about dir was inside cmd.exe, I tried with date as well, as this is used as example in the manual, gave same error code. (Error code: 2)
I found a solution to my problem.
Trying to start a 64-bit program with ipcBeginProcess command is not good, and will result in Error code 50.
Reinstalling perl as 32-bit solved my issue. Thanks to support at nordcad.dk
Thanks for the nice words
Regards from Ole at Nordcad