Assura Installation Problem

B

Burak Kelleci

Guest
Hi,

I installed assura 3.1.3. I am using cadence 5.0.33 and have tried to
invoke assura from cadence. During the opening of the layout window,
cadence give the following warning.

*WARNING* Assura not available.

Therefore I couldn't access assura from layout. I followed everything in
the instraction manual. But it didn't solve the problem. Should I upgrade
also cadence version? Or is there another solution?

Thanks

Burak
 
There is nothing in the Assura C or SKILL code that issues that message.
Nor is there anything in the code that loads the Assura shared object.
My guess is that something in the workbench is trying to reference
Assura without it having been properly loaded.

Perhaps more context for the message might be helpful. One line of
output is not as useful as several. Try starting the workbench, open a
layout view, and exit the workbench. Then post the entire log. It should
be rather short, but may have the missing clue.

You might also review the manual for environmental variable settings,
like ASSURAHOME, which is needed if Assura was not installed in the same
hierarchy as the DFII tools.

On Mon, 21 Feb 2005 13:25:47 -0600, Burak Kelleci <burak@ee.tamu.edu>
wrote:

Hi,

I installed assura 3.1.3. I am using cadence 5.0.33 and have tried to
invoke assura from cadence. During the opening of the layout window,
cadence give the following warning.

*WARNING* Assura not available.

Therefore I couldn't access assura from layout. I followed everything in
the instraction manual. But it didn't solve the problem. Should I upgrade
also cadence version? Or is there another solution?

Thanks

Burak
Click to expand...
 
There's a sourcelink solution for this, number 11108690.

It suggests:

"One of the cases when this warning message appears is if you run the 'layout'
executable instead of 'layoutPlus' or 'icfb'. Choose 'layoutPlus' or 'icfb'
to initiate the dfII session."

This is of course in addition to the previous suggestions - making sure that
ASSURAHOME is set, and that the UNIX path includes
$ASSURAHOME/tools/assura/bin

Regards,

Andrew.

On Mon, 21 Feb 2005 15:26:38 -0800, Diva Physical Verification
<diva@cadence.com> wrote:

There is nothing in the Assura C or SKILL code that issues that message.
Nor is there anything in the code that loads the Assura shared object.
My guess is that something in the workbench is trying to reference
Assura without it having been properly loaded.

Perhaps more context for the message might be helpful. One line of
output is not as useful as several. Try starting the workbench, open a
layout view, and exit the workbench. Then post the entire log. It should
be rather short, but may have the missing clue.

You might also review the manual for environmental variable settings,
like ASSURAHOME, which is needed if Assura was not installed in the same
hierarchy as the DFII tools.

On Mon, 21 Feb 2005 13:25:47 -0600, Burak Kelleci <burak@ee.tamu.edu
wrote:

Hi,

I installed assura 3.1.3. I am using cadence 5.0.33 and have tried to
invoke assura from cadence. During the opening of the layout window,
cadence give the following warning.

*WARNING* Assura not available.

Therefore I couldn't access assura from layout. I followed everything in
the instraction manual. But it didn't solve the problem. Should I upgrade
also cadence version? Or is there another solution?

Thanks

Burak
Click to expand...
 
I think this is caused by the PATH,you can use "echo PATH" to see if there
path is correct or not.

for cshr
setenv ASSURA30 /tools/cadence/ASSURA30
set path = ($ASSURA/tools/bin $ASSURA/tools/dfII/bin
$ASSURA/tools/assura/bin $path)

for bash
ASSURA30=/tools/cadence/ASSURA30
export ASSURA30;
PATH=$ASSURA/tools/bin:$ASSURA/tools/dfII/bin:$ASSURA/tools/assura/bin:$PATH
export PATH;

if the path is not in your our path,you should add all in your .cshrc(CSH)
or .bash_profile (BASH).

"Andrew Beckett" <andrewb@DcEaLdEeTnEcTe.HcIoSm>
??????:c4jl119pe799f7m1bbalmslaqriidi32g4@4ax.com...
There's a sourcelink solution for this, number 11108690.

It suggests:

"One of the cases when this warning message appears is if you run the
'layout'
executable instead of 'layoutPlus' or 'icfb'. Choose 'layoutPlus' or
'icfb'
to initiate the dfII session."

This is of course in addition to the previous suggestions - making sure
that
ASSURAHOME is set, and that the UNIX path includes
$ASSURAHOME/tools/assura/bin

Regards,

Andrew.

On Mon, 21 Feb 2005 15:26:38 -0800, Diva Physical Verification
diva@cadence.com> wrote:

There is nothing in the Assura C or SKILL code that issues that message.
Nor is there anything in the code that loads the Assura shared object.
My guess is that something in the workbench is trying to reference
Assura without it having been properly loaded.

Perhaps more context for the message might be helpful. One line of
output is not as useful as several. Try starting the workbench, open a
layout view, and exit the workbench. Then post the entire log. It should
be rather short, but may have the missing clue.

You might also review the manual for environmental variable settings,
like ASSURAHOME, which is needed if Assura was not installed in the same
hierarchy as the DFII tools.

On Mon, 21 Feb 2005 13:25:47 -0600, Burak Kelleci <burak@ee.tamu.edu
wrote:

Hi,

I installed assura 3.1.3. I am using cadence 5.0.33 and have tried to
invoke assura from cadence. During the opening of the layout window,
cadence give the following warning.

*WARNING* Assura not available.

Therefore I couldn't access assura from layout. I followed everything in
the instraction manual. But it didn't solve the problem. Should I upgrade
also cadence version? Or is there another solution?

Thanks

Burak
Click to expand...
 
You need also to add the lib path.

For Cshell it should be :
setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$ASSURAHOME/tools/lib

================
Kholdoun TORKI
http://cmp.imag.fr
================


Guanghui wrote:

I think this is caused by the PATH,you can use "echo PATH" to see if there
path is correct or not.

for cshr
setenv ASSURA30 /tools/cadence/ASSURA30
set path = ($ASSURA/tools/bin $ASSURA/tools/dfII/bin
$ASSURA/tools/assura/bin $path)

for bash
ASSURA30=/tools/cadence/ASSURA30
export ASSURA30;
PATH=$ASSURA/tools/bin:$ASSURA/tools/dfII/bin:$ASSURA/tools/assura/bin:$PATH
export PATH;

if the path is not in your our path,you should add all in your .cshrc(CSH)
or .bash_profile (BASH).

"Andrew Beckett" <andrewb@DcEaLdEeTnEcTe.HcIoSm
??????:c4jl119pe799f7m1bbalmslaqriidi32g4@4ax.com...

There's a sourcelink solution for this, number 11108690.

It suggests:

"One of the cases when this warning message appears is if you run the
'layout'
executable instead of 'layoutPlus' or 'icfb'. Choose 'layoutPlus' or
'icfb'
to initiate the dfII session."

This is of course in addition to the previous suggestions - making sure
that
ASSURAHOME is set, and that the UNIX path includes
$ASSURAHOME/tools/assura/bin

Regards,

Andrew.

On Mon, 21 Feb 2005 15:26:38 -0800, Diva Physical Verification
diva@cadence.com> wrote:


There is nothing in the Assura C or SKILL code that issues that message.
Nor is there anything in the code that loads the Assura shared object.
My guess is that something in the workbench is trying to reference
Assura without it having been properly loaded.

Perhaps more context for the message might be helpful. One line of
output is not as useful as several. Try starting the workbench, open a
layout view, and exit the workbench. Then post the entire log. It should
be rather short, but may have the missing clue.

You might also review the manual for environmental variable settings,
like ASSURAHOME, which is needed if Assura was not installed in the same
hierarchy as the DFII tools.

On Mon, 21 Feb 2005 13:25:47 -0600, Burak Kelleci <burak@ee.tamu.edu
wrote:


Hi,

I installed assura 3.1.3. I am using cadence 5.0.33 and have tried to
invoke assura from cadence. During the opening of the layout window,
cadence give the following warning.

*WARNING* Assura not available.

Therefore I couldn't access assura from layout. I followed everything in
the instraction manual. But it didn't solve the problem. Should I upgrade
also cadence version? Or is there another solution?

Thanks

Burak
Click to expand...
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top