Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

Assura LVS quits due to unbound device error

Status
Not open for further replies.
S

Souljah44

Junior Member level 1
Joined
Feb 17, 2009
Messages
17
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,445
Hi guys,

I'm using Assura for the first time and am encountering issues that I don't know how to tackle.

I just ran LVS on a rather large block and am getting this error:

Preprocessing schematic network phase 2
Preprocessing layout network phase 2
*ERROR* Device 'probe1(Generic)' on Layout is unbound to any Schematic device.
*ERROR* Device 'probe2(Generic)' on Layout is unbound to any Schematic device.
*ERROR* UnBound devices found.
Info: All devices must be bound or filtered for comparision to be run.
Exiting nvn.


I have no idea what the error is trying to tell me...I guess I'm too used to Caliber but I did a hierarchichal search of "probe" and "probe1" in my layout but the search returned nothing. I'm stumped.

If anyone has seen this before and can point me in the right direction, I'd really appreciate it.

Thanks!
 

You probably have placed these "probe" devices in the
layout that don't have an appropriate schematic
counterpart, or a proper LVS rep (they probably are
not meant to be in the layout anyway, do you expect
to print a "probe" in fab?).

I'd begin with doing schematic and layout tree reports,
and grep them both for 'probe'. This should get you to
"where".

If you find them then you either want them gone, or
set / add property lvsIgnore="t".

Now you might also want to look carefully at your
"layout" master as presented to Assura and make sure
it's really the right block, because feeding a schematic
to the layout extract process will result in some kooky
stuff. Make sure it's not just a matter of misdirection.
 

Thanks for the reply,

I have done a tree of both the layout and the schematic and neither file contains "probe" in it. The layout is a port so who knows what it contains but in all my years of doing layout, I've never used a layout probe and don't know what it is or its use.

I don't think this is referring to the probe that you add to a net so it gets highlighted. That type of probe would not be streamed out.

Thanks

dick_freebird said:
You probably have placed these "probe" devices in the
layout that don't have an appropriate schematic
counterpart, or a proper LVS rep (they probably are
not meant to be in the layout anyway, do you expect
to print a "probe" in fab?).

I'd begin with doing schematic and layout tree reports,
and grep them both for 'probe'. This should get you to
"where".

If you find them then you either want them gone, or
set / add property lvsIgnore="t".

Now you might also want to look carefully at your
"layout" master as presented to Assura and make sure
it's really the right block, because feeding a schematic
to the layout extract process will result in some kooky
stuff. Make sure it's not just a matter of misdirection.
Click to expand...
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top