Assura and deviceInfo.rul file

[S. Badel]

I use a deviceInfo.rul file to map schematic terminal names to
assura terminal names. it works perfectly with LVS, but it seems
that RCX is not using this file, and therefore i get terminal errors.
I don't know what to do. Any ideas?
Thanks,
Stéphane

 

[Sam Durbin]

My LVS passes. RCX operates normally until attempted on a design with
a device of 2 terminals with 3 auLVS terminals (the virtual substrate
terminal). With such a device, RCX fails giving a terminal error.
Cadence SR32675338.
Cadence has asked me for a test case, however, the need for the
customers complex legacy Skill set and more has resulted in failure of
Cadence ability to replicate the issue. I am hoping to replicate in
IC50 with cleaner structure. Perhaps we could compare notes.

Sam

"S. Badel" <stephane.badel@epfl.ch> wrote in message news:<3ffa94d5$1@epflnews.epfl.ch>...

I use a deviceInfo.rul file to map schematic terminal names to
assura terminal names. it works perfectly with LVS, but it seems
that RCX is not using this file, and therefore i get terminal errors.
I don't know what to do. Any ideas?
Thanks,
Stéphane

 

[S. Badel]

Sam,
I found this in the Assura Developer Guide :

Important
If you are going to create an extracted view, you must define the terminal
names as
they are defined in the symbol.

this is stated for all device extraction command.
this makes clear to me the fact it also won't work if the terminal count is
different.

for me, i changed the terminal names to be the same in the extraction
command
and in the auLvs symbol and auLvs views, and it worked. i needed to
resimulate
parasitics with capgen -S however.

I also needed to add a substrate terminal in the extraction command for my
resistors
because the symbol contained 3 pins. this also worked.

stephane

"Sam Durbin" <sam.durbin@guidant.com> wrote in message
news:13d412e6.0401071556.307cbeb4@posting.google.com...

My LVS passes. RCX operates normally until attempted on a design with
a device of 2 terminals with 3 auLVS terminals (the virtual substrate
terminal). With such a device, RCX fails giving a terminal error.
Cadence SR32675338.
Cadence has asked me for a test case, however, the need for the
customers complex legacy Skill set and more has resulted in failure of
Cadence ability to replicate the issue. I am hoping to replicate in
IC50 with cleaner structure. Perhaps we could compare notes.

Sam

"S. Badel" <stephane.badel@epfl.ch> wrote in message
news:<3ffa94d5$1@epflnews.epfl.ch>...
I use a deviceInfo.rul file to map schematic terminal names to
assura terminal names. it works perfectly with LVS, but it seems
that RCX is not using this file, and therefore i get terminal errors.
I don't know what to do. Any ideas?
Thanks,
Stéphane