For Assura, all you should need to do is to:
That's it. For Calibre, you should read the Mentor documentation - but it's a matter of setting appropriate UNIX env vars, setting up your path, and loading some code from your .cdsinit (if my memory is correct).
Neither of these things is something that the PDK would take care of, I believe - it's more of a software installation/setup problem.
In reply to Andrew Beckett:
Thank you very much Indeed Andrew.
In reply to wgtkan:
This didn't work for me. Do you need to have anything else in the .cdsinit etc?
In reply to NKU10k:
Assura doesn't require anything in .cdsinit . Calibre probably does, but that's a question for Mentor.
Make sure you're using an OA version of Assura with an OA version of Virtuoso or a CDB version with a CDB version of icfb (i..e pick the appropriate version of Assura when you install it).
In reply to Khalil JRADI:
I already explained further back what you need to do for Assura and that this doesn't need anything in .cdsinit/.cdsenv. All that needs is the UNIX env var $ASSURAHOME setting and the UNIX path setting so that assura can be found in the UNIX search path.
For Calibre I can't answer as this is a Mentor Graphics tool not a Cadence tool - you'd have to read their documentation or ask Mentor Graphics.
Thank you for your quick reply.
I checked the ASSURA package and it's installed. I actually added the "UNIX path setting" in the bashrc file. My question is : Should I add also the "UNIX env var $ASSURAHOME setting" to the same file (bashrc) ? if not where should I add this command ?
Thank you for quick reply
Dracula is part of the IC stream so that's nothing to do with this - you get Dracula anyway. It's a completely different physical verification tool.
There's no such thing as "ASSURA 631" so I don't know what you mean. You'd need an ASSURA41 release built for IC614 (that is a very old Virtuoso version - that's the "base" version of IC614, which was released in November 2009 - and doesn't have any hotfixes at all). I would strongly recommend against you using an almost 6-year old base release - when there have been two major releases since then too.
Anyway, there are on downloads.cadence.com a couple of ASSURA41 releases intended for use with IC614:
16 Dec 2010 ASSURA04.12.001, Version: ASSURA41USR2OA_614
14 Jun 2012 ASSURA04.12.017, Version: ASSURA41USR2HF17OA_614
The second of these is a hotfix release - so I'd go for that.
I've no idea what you've installed, so can't really tell whether it would work or not.
I updated my cadence virtuoso for the IC6.1.6. & since i have ASSURA41 so everything is perfect now.
I would like to return to the above subject, in fact, I updated cadence (IC6.1.6) and with Assura41, I could start the DRC and LVS, (with these versions). The problem that i got, RCX wasn't working ! Well, it was available but i could not do an Extracted view (but only lvs-extracted).
Later, I made an update (towards hotfix release: IC18.104.22.1680.11) and an update for Assura too. The problem now is, all layouts are open with the same color (yellow) and I have no longer RCX in the Assura menu. Moreover, I can not launch an electrical simulation of my circuits! Do you have an explanation for this? Any suggestions (other compatible versions maybe for the update of cadence or Assura)?
The colour information is almost certainly nothing to do with this - it's an environment issue. If the colours are all yellow, it probably means that your display.drf file is not being found - either it was supposed to be in the working directory and you're running from the wrong place, or the PDK is not loading it. The explanation could be many things, but I'm sure it's nothing to do with the Cadence tools themselves.
As for extraction "wasn't working" is not very specific. It almost certainly would have given errors in the log file when you ran RCX. If you're running Assura RCX, that's not advisable because it hasn't been updated for many years; the RC extraction tool became a separate product, QRC, now Quantus QRC, many years ago and should be installed from the "EXT" release stream (EXT142 is the latest version). Maybe that's your problem?
I would suggest contacting customer support (as I have advised before). Figuring this out from so little information is really hard.