Greyed menu: "Run Assura Quantus QRC..." and "Run Assura Quantus QRC..."

Have you run LVS? If yes, which tool did you use? If you ran LVS using Assura, can you tell me the IC and Assura versions you are using.

Regards,

Saloni

Yes, LVS passed without any problem.

I am using IC617, ASSURA41 and EXT172.

Thanks. You didn't say what _vuiGetQRCVersion() returns - can you show that (you'll have had to have opened a layout window first)?

Also, can you provide what these output (both in the CIW)?

_vuiGetQRCContext()

system.??

In the terminal window, can  you  run "cds_plat" and post what is returned?

Thanks,

Andrew.

Sorry Andrew, I forgot. Here are the results:

_vuiGetQRCVersion()
*Error* eval: undefined function - _vuiGetQRCVersion

system.??
(name "Linux" plat "lnx86" dirBrkChrs
    "/" dirSepChr "/" pathSep ":"
    shLibExt ".so" LP64 t P64
    t
)

[bit@cds TSMC-CR018]$ cds_plat
lnx86

You need to do it after opening a layout window (so that Assura has initialised - I said that before). So I need that and both the _vui function output including _vuiGetQRCContext()

Andrew

OK, sorry again. I have to pay more attention.

_vuiGetQRCVersion()
0
_vuiGetQRCContext()
"/opt/cadence/EXT181/tools.lnx86/extraction/bin/64bit/etc/context/6.1.0/64bit/qrc.cxt"

OK, we’re getting close. The first returning 0 is why the menus get messed up. Now just need to figure out why it returns 0.

I’m on a plane now so this will need to wait until a bit later to debug further. 

To be honest, doing this via the forums is not the most efficient way of solving this - thanks for your patience. 

Andrew

OK Andrew. It's I who thank you.

I know it is a bit frustrating to have to wait for the return of a simple command.

Thanks again,

wighou

wighou,

I thought I'd found a possible explanation, but I'm not convinced this can be it because if I mess with this the QRC menu doesn't appear at all and I get some different warnings in the CIW. Anyway, just in case, can you open the layout window as before and then do:

rexMagic()

I'm interested if this returns nil. If it does, try:

rexMagic(t)
_vuiGetQRCVersion()

and see if that returns something other than zero. Otherwise, try doing this:

trace(_vuiGetQRCVersion _vuiEvalQRCVersion)
tracev(qrcVer version qrcOk)
_vuiGetQRCVersion()

and paste here what you get.

Thanks,

Andrew.

I had a problem of moderation I think. I will begin with this first part:

rexMagic()
t

trace(_vuiGetQRCVersion _vuiEvalQRCVersion)
_vuiEvalQRCVersion(_vuiGetQRCVersion)

tracev(qrcVer version qrcOk)
|[1]qrcVer set to unbound, was unbound
|[1]version set to unbound, was unbound
|[1]qrcOk set to unbound, was unbound
(qrcOk version qrcVer)

and the second part (_vuiGetQRCVersion() response), you can find here: https://file.io/NGbhKi

I just get a "file.io 404 Page not found" error if I try to follow that link. Can you not attach it as a text file here if it won't let you paste it? If it goes into moderation, I can approve it - although I've not seen anything that needs approval. Use the Insert->Image/video/file below...

Regards,

Andrew.

I just get a "file.io 404 Page not found" error if I try to follow that link. Can you not attach it as a text file here if it won't let you paste it? If it goes into moderation, I can approve it - although I've not seen anything that needs approval. Use the Insert->Image/video/file below...

Regards,

Andrew.

Thanks for the additional data.

OK, it is in fact because you're running on an unsupported OS.

What's happening is that the message about this being an unsupported machine is being output before the qrc -v output, and because of this the version checking code doesn't ever see the qrc version number. When I first looked at this I thought that it was reading the entire output from the "qrc -v" command, but because the wrapper first outputs the unsupported platform before the main qrc executable prints the version, the problem occurs.

I managed to try it on a CentOS machine, and see exactly the same problem. 

Regards,

Andrew.

OK Andrew. Thanks for your diagnostic.

Do you know a workaround?

It is not possible to avoid this test?

Yes - use a supported OS!

We do have an article which explains how to workaround this: When using (unsupported) CentOS, a new, frequent warning occurs since 617/123 ISR9. Can the warning be suppressed?

Note that whilst that article does give an environment variable to suppress the message, it makes it very clear that this does not mean that CentOS is implicitly supported by doing this. It's at your own risk. Using the env var given does fix the problem though (I tried it).

Andrew.

This is one of the reasons we have supported OS platforms. Sometimes you spend a lot of time trying to get to the bottom of a problem on a platform that we don't test on (such as I did with this issue...)

Andrew.

OK, I understand. It is just a pity that there is no free supported OS.

CentOS is roughly the same platform as Redhat.

Thank you very much for your help. You make a great work.

Best regards,

wighou