( ESNUG 296 Item 3 ) ---------------------------------------------- [7/23/98]
Subject: Cadence Support Ain't Worth Shit For Verilog-XL Behavioral Profiler
> I've been unsuccessful trying to get the Behvioral Profiler option in
> Verilog-XL to work and was wondering if anyone out there may have had
> similar experiences. I've tried Cadence Customer support for the past
> 3 months (!), with no luck at all. They've had me install OS patches,
> upgrade to the latest rev, re-install from new CDs that they shipped to
> me, all with no luck. I'm really frustruated at this point and was
> hoping someone out there might be able to help.
>
> When I bring up a design with the "+profile" and issue a "$startprofile"
> command, I get the following message: "Signal 26 current ignored".
>
> Running for a few cycles after this and issuing a "$reportprofile"
> command gives a mesage that are 0 samples in the report -- I end up
> getting no useful information at all.
>
> I had the same problem with my previous rev of XL (2.6.1 ?), which is
> why I upgraded to 2.6.8 (release 97B) in the first place. I'm running
> on a Sparc-10, running Sun 0S 4.1.3. I also had the same result with a
> sparc-20 running 4.1.4. I've also tried it with and without the "+turbo"
> and "+gui" options.
>
> Cadence has pretty much given up at this point, though they tell me that
> this specific problem was fixed when they went to 2.6.8. I don't
> understand why they can't give me at least a pointer as to what to look
> for, if they have seen this error before.
>
> I'm very disappointed with the support I've gotten from Cadence. Not
> only is my problem not solved after 3 months of going around in circles,
> but the support person didn't even know the proper install procedure
> when I was upgrading. He said that I had done it incorrectly (I followed
> the directions that came with the CDs) only to retract later and have
> to re-do it the way I had done originally.
>
> - Chip Natarajan
> Young Chang R&D
From: Achim Gratz <gratz@ite.inf.tu-dresden.de>
If that program runs at Cadences support site, have them send you the
output of ldd for each executable involved plus the size and xsum of
the libraries in question and cross check with yours. If you're
lucky, you are just picking up an uprev dynamic library that Cadence
in it's infinite wisdom has also partly linked in statically. Make
sure your environment and especially LD_LIBRARY_PATH is set to the
absolute minimum and create a wrapper script to keep it that way for
the cadence commands you use.
- Achim Gratz
TU Dresden Dresden, Germany
|
|
