Date: Thu, 28 Mar 2024 20:01:55 +0000 (GMT) Message-ID: <1946575690.25.1711656115495@[172.30.0.157]> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_24_1567275323.1711656115495" ------=_Part_24_1567275323.1711656115495 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
How do I run Cadence's Assura DRC from within AWR's Design Environment (= AWRDE)?
AWR 2007 (Version 7.5) and later.
MWO and AO
Assura DRC is supported in AWRDE v7.5 or higher. Some of the important f= eatures are support for secure shell (ssh), simple user setup, area DRC,and= ability to mark errors as Checked or False.
The Assura integration requires an optional ASR-100 feature in the License File
. To determine whether or not you have this feature,=
perform the following steps from within the AWRDE:
Select File > License > Feature Setup
You must have ASR-100 in Optional Features for the As= sura integration to work properly. If you do not have this feature, contact= your local AWR Sales representative for assistance.
The purpose of this article is to show users the how to run Assura DRC f= rom within the AWRDE. It is expected that Assura DRC is installed and runni= ng on a UNIX or Linux computer prior to integrating with the AWRDE. How to = set up Assura DRC is beyond the scope of this article. Contact your local C= adence representative for help in getting Assura DRC running.
Assura DRC runs on a either UNIX or Linux computer. In this article, "Li= nux" will be used generically to refer to either Unix or Linux. We support = both remote shell (rsh) and secure shell (ssh) as communication protocols b= etween the PC running AWRDE and the Linux machine running Assura DRC.
For using rsh, AWRDE uses the Windows built-in rsh functionality. To use=
ssh, you will need a ssh, telnet, and rlogin client called PuTTY =
code> .
The AWRDE setup for using rsh or ssh is done by selecting Help > Show=
Files/Directories and adding the following statements to the user.i=
ni
file.
For rsh:
[ASSURA_DRC]=20 Machine=3Dname_of_Linux_machine_where_Assur= a_DRC_runs=20
For ssh:
[ASSURA_DRC]=20 Machine=3Dname_of_Linux_machine_where_Assur= a_DRC_runs=20 NetClient=3DPuTTY Password=3D-i point_to_PuTTY_generated_priv= ate_key_file=20
OR
Password=3D-pw type_user's_Linux_password=20
Note: If using the "-pw" option, the user's password will be plainly vis=
ible to anyone viewing user.ini
. Because of this, users mig=
ht prefer the "-i" key approach, where a private/public key pair (both of w=
hich are encrypted) is generated using PuTTYgen
, which is <=
code> PuTTY key generator. For more information on creating and usi=
ng keys, the user is referred to Chapter 8 of PuTTY's User Manual =
code> which covers using public keys for SSH authentication.
After performing these steps, save and close your user.ini
and text editor, and then close the Directories window.
In addition, if using ssh, the path to putty.exe
needs to=
be specified in the Windows Path environment variable by right-clicking on=
My Computer, going to Properties > Advanced > Environment Variables,=
and adding the path to putty.exe
. The default location is =
C:\Program Files\PuTTY
.
For version 9.0 and later, the following directions apply:
Open the layout you would like to DRC and select Verify > Design = Rule Check .
Click Configure .
Browse to Rule Deck.
Select Assura as Engines and click OK
Click Run DRC
At this point, AWRDE will create a GDS of the layout, copy the GDS file = and rule file to the Linux computer, do the Assura DRC run, and bring back = the results of the DRC run. The results of the DRC run will display as eith= er "No DRC errors" or the errors will be highlighted. The user can highligh= t errors in groups or 1-by-1 and fix them, mark them as Checked, or mark th= em as False.
In addition, errors can be saved for later review. With your layout open= , select Verify > Save DRC Errors. The saved errors can be loaded by sel= ecting Verify > Load DRC Errors.
Area DRC is also available to the user. This can be enabled by selecting= Verify > DRC Check Area, drawing a window around the area to be checked= , clicking DRC check area in the DRC window, followed by Run DRC.
Troubleshooting:
If DRC did not complete properly, an error transcript log will appear. B= efore looking in detail into the log, check that the PC and Linux computer = are connected using the following steps:
For rsh: Open a DOS window by selecting Start > Ru=
n and type cmd
in the box that appear. At=
the DOS prompt, type
rsh name_of_Linux_machine_where_Assura_DRC_run= s ls=20
This should return a listing of the files the user has in his Linux
For ssh: Test PC/Linux connectivity using PuTTY:
If using the "-i" keys approach: In PuTTY
, in Sessio=
n category, enter Host Name
(which is the=
name_of_Linux_machine_where_Assura_DRC_runs
in this example=
) and select SSH as Protocol. In Connection > SSH > Auth category, po=
int to the private key specified in the "-i" option click Open. If connecti=
on is unsuccessful, the error messages should give an idea of what the prob=
lem is. Depending on the problem, your IT department might need to help res=
olve the issue.
If using the "-pw" password approach: In PuTTY
, in S=
ession category, enter Host Name
(which i=
s the name_of_Linux_machine_where_Assura_DRC_runs
in this ex=
ample) and SSH as Protocol. Click Open. If this doesn't connect, your IT de=
partment might need to help resolve the issue.
If proper connection is made, a window asking your username and password= should appear. If proper connection is made in either of the above cases, = this means ssh is properly connecting the PC and Linux computer, so you can= view the DRC error transcript log.