Schematic pin to pin tracer

  • Thread starter tattvamasi@gmail.com
  • Start date
T

tattvamasi@gmail.com

Guest
Problem statement:
Given a starting pin, starting cell name & ending cellname(All in the
same hierarchy), to find the mapping between the starting pin and the
actual pin it is connected to in the ending cell name(stop level).

Looks to me like a big graph theory problem, open to ideas about
implementation.
But since Cadence already has leHiProbe, am tempted to check and see if
they have any canned skill function?

What I can think off:

Start out "waves" from the starting pin:cellName and stop when you hit
on the endingcell name, and grab the pinname of that instance

Not very clear how I would do so in skill though.

Any insights appreciated!
Partha
 
tattvamasi@gmail.com wrote:
But since Cadence already has leHiProbe, am tempted to check and see if
they have any canned skill function?
Hmmmmmm ...

Just for the record, I can find no official Cadence SKILL function:
leHiProbe()

Of course, you may be referring to SKILL code written by Cadence
personnel or by your site which defines that function. However, any
Customer or non-production Cadence AE function SKILL written should
begin with a capital-letter prefix, e.g., MyLeHiProbe() and this one
doesn't.

I even checked the database of SKILL functions called & written by
Customers who cared enough about their SKILL code to register the
functions in use with Cadence; and even that lookup came up blank.
IMHO, nobody who cares enough about their SKILL to register with
Cadence which functions they care about has ever called or defined a
SKILL function named leHiProbe().

My only point is I see no indication that this function exists. In
Cadence code; or in anyone else's code. It may, of course, exist, so
I'm not doubting the veracity of your statements. I'm just saying I
don't see any evidence leHiProbe() exists. Did you mean some other
SKILL probing function?

For example, there is a Cadence public documented Virtuoso XL function
"adleHiProbe(); and there is a public lxHiProbe() function called in
samples/local/lxBindKeys.il; but no Cadence SKILL function (as of IC434
anyway which is as far back as I checked) named leHiProbe() as far as I
can see.

If you think your company has defined this SKILL function, I suggest:
you run a quick 5-minute, yet complete CIW:Tools->SKILL->Survey on your
SKILL code. The first half of the SKILL Survey will be a tabulation
which provides you a complete inventory of all the SKILL functions you
called and where exactly you called them; plus another inventory of all
SKILL functions you defined and where you defined them.

This extensive personal SKILL code inventory is completely for your
use.

In addition, if you decide to complete the second half of the SKILL
Survey, by sending the non-proprietary summary file to Cadence (just
click on the CIW: Tools->SKILL->Survey email button when it asks), you
automatically obtain a listing of which functions you called in your
code exist and which ones don't exist (among other key data such as
which functions were improved or deleted yesterday in any recent or
future release).

You can even find your own typos this way. How? Well, you called it but
didn't define it; yet Cadence didn't define it either. It's either a
dependency or a typo, but, either way, the function doesn't exist in
the code you surveyed. Kewl huh? (Psssst ... John ... get off the
soapbox ... oh ... ok ... sorry ... I just think this is a great, if
underused, feature of product 900 SKILL Development Environment. I'll
shut up now.).

As always, good luck in all that you do,
John Gianni
"Please do not email to this spam-trap address; use my official email."
 
John,
That was an error on my part.
I should have meant,
geAddNetProbe()

This highlights all the nets connected to the selected net, through the
hierarchy. Would like to know the best way to implement this sort of a
function for my problem mentioned above.

Thanks,
Partha
P.S Will use skill Suvey.

J. J. G. wrote:
tattvamasi@gmail.com wrote:
But since Cadence already has leHiProbe, am tempted to check and see if
they have any canned skill function?

Hmmmmmm ...

Just for the record, I can find no official Cadence SKILL function:
leHiProbe()

Of course, you may be referring to SKILL code written by Cadence
personnel or by your site which defines that function. However, any
Customer or non-production Cadence AE function SKILL written should
begin with a capital-letter prefix, e.g., MyLeHiProbe() and this one
doesn't.

I even checked the database of SKILL functions called & written by
Customers who cared enough about their SKILL code to register the
functions in use with Cadence; and even that lookup came up blank.
IMHO, nobody who cares enough about their SKILL to register with
Cadence which functions they care about has ever called or defined a
SKILL function named leHiProbe().

My only point is I see no indication that this function exists. In
Cadence code; or in anyone else's code. It may, of course, exist, so
I'm not doubting the veracity of your statements. I'm just saying I
don't see any evidence leHiProbe() exists. Did you mean some other
SKILL probing function?

For example, there is a Cadence public documented Virtuoso XL function
"adleHiProbe(); and there is a public lxHiProbe() function called in
samples/local/lxBindKeys.il; but no Cadence SKILL function (as of IC434
anyway which is as far back as I checked) named leHiProbe() as far as I
can see.

If you think your company has defined this SKILL function, I suggest:
you run a quick 5-minute, yet complete CIW:Tools->SKILL->Survey on your
SKILL code. The first half of the SKILL Survey will be a tabulation
which provides you a complete inventory of all the SKILL functions you
called and where exactly you called them; plus another inventory of all
SKILL functions you defined and where you defined them.

This extensive personal SKILL code inventory is completely for your
use.

In addition, if you decide to complete the second half of the SKILL
Survey, by sending the non-proprietary summary file to Cadence (just
click on the CIW: Tools->SKILL->Survey email button when it asks), you
automatically obtain a listing of which functions you called in your
code exist and which ones don't exist (among other key data such as
which functions were improved or deleted yesterday in any recent or
future release).

You can even find your own typos this way. How? Well, you called it but
didn't define it; yet Cadence didn't define it either. It's either a
dependency or a typo, but, either way, the function doesn't exist in
the code you surveyed. Kewl huh? (Psssst ... John ... get off the
soapbox ... oh ... ok ... sorry ... I just think this is a great, if
underused, feature of product 900 SKILL Development Environment. I'll
shut up now.).

As always, good luck in all that you do,
John Gianni
"Please do not email to this spam-trap address; use my official email."
 
John,
That was an error on my part.
I should have meant,
geAddNetProbe()

This highlights all the nets connected to the selected net, through the
hierarchy. Would like to know the best way to implement this sort of a
function for my problem mentioned above.

Thanks,
Partha
P.S Will use skill Suvey.

J. J. G. wrote:
tattvamasi@gmail.com wrote:
But since Cadence already has leHiProbe, am tempted to check and see if
they have any canned skill function?

Hmmmmmm ...

Just for the record, I can find no official Cadence SKILL function:
leHiProbe()

Of course, you may be referring to SKILL code written by Cadence
personnel or by your site which defines that function. However, any
Customer or non-production Cadence AE function SKILL written should
begin with a capital-letter prefix, e.g., MyLeHiProbe() and this one
doesn't.

I even checked the database of SKILL functions called & written by
Customers who cared enough about their SKILL code to register the
functions in use with Cadence; and even that lookup came up blank.
IMHO, nobody who cares enough about their SKILL to register with
Cadence which functions they care about has ever called or defined a
SKILL function named leHiProbe().

My only point is I see no indication that this function exists. In
Cadence code; or in anyone else's code. It may, of course, exist, so
I'm not doubting the veracity of your statements. I'm just saying I
don't see any evidence leHiProbe() exists. Did you mean some other
SKILL probing function?

For example, there is a Cadence public documented Virtuoso XL function
"adleHiProbe(); and there is a public lxHiProbe() function called in
samples/local/lxBindKeys.il; but no Cadence SKILL function (as of IC434
anyway which is as far back as I checked) named leHiProbe() as far as I
can see.

If you think your company has defined this SKILL function, I suggest:
you run a quick 5-minute, yet complete CIW:Tools->SKILL->Survey on your
SKILL code. The first half of the SKILL Survey will be a tabulation
which provides you a complete inventory of all the SKILL functions you
called and where exactly you called them; plus another inventory of all
SKILL functions you defined and where you defined them.

This extensive personal SKILL code inventory is completely for your
use.

In addition, if you decide to complete the second half of the SKILL
Survey, by sending the non-proprietary summary file to Cadence (just
click on the CIW: Tools->SKILL->Survey email button when it asks), you
automatically obtain a listing of which functions you called in your
code exist and which ones don't exist (among other key data such as
which functions were improved or deleted yesterday in any recent or
future release).

You can even find your own typos this way. How? Well, you called it but
didn't define it; yet Cadence didn't define it either. It's either a
dependency or a typo, but, either way, the function doesn't exist in
the code you surveyed. Kewl huh? (Psssst ... John ... get off the
soapbox ... oh ... ok ... sorry ... I just think this is a great, if
underused, feature of product 900 SKILL Development Environment. I'll
shut up now.).

As always, good luck in all that you do,
John Gianni
"Please do not email to this spam-trap address; use my official email."
 
Did you ever try this website: http://www.nandigits.com/
It is a graphical netlist trace and modification tool. It allows users
draw and isolate gates in schematics by just clicking on gate pins.
Starting from one cell user has interest in, after several mouse
clicking and moving, one circuit appears. Users can move, replace,
delete or add gates in the schematics, and can also drag and drop gates
from codeview window. After changes are made with the tool, an ECO file
in tcl format or a new netlist file an be generated and printed. I have
used it for a while, it works great for me! Save me a lots time to
debug. The best ECO tool, highly recommended.

Heidi
 
Hi,
This looks interesting to me. Is it possible to highlight (or
seperate) a logic path that is sensitized by an input test pattern.
Lets say I have to test vectors and applying these vectors bacl-to-back
causes a logic transition to propagate along certain path in the
design; is it possible to highlight such logic paths and then isolate
them from the netlist?

Thanks
saby.
 

Welcome to EDABoard.com

Sponsor

Back
Top