( ESNUG 430 Item 6 ) --------------------------------------------- [06/16/04]
Subject: ( DVcon 04 #9 ) How To Get Black Box Abilities In Verplex LEC
> As far as enhancements go, I would like Verplex to have the ability to
> "black-box" modules up front. I requested this type of enhancement a
> while ago, but have not seen it yet. Case in point, our last design had
> a wrapper for each RAM. The RTL versions were clean, but the
> gate-versions had BIST logic, etc. that our vendor inserted (they owned
> the BIST insertion). It would have been great to have been able to add
> a section to our scripts that black-boxed the wrappers upfront, rather
> than having to weed through all the warnings that popped on the BIST
> logic. And, it would have been even nicer, because you would not have
> FV checking the two memory arrays against each other, which would
> have sped up the FV run.
>
> Having said that, Cadence did buy Verplex, and we all know what tends to
> happen to acquired tools... My hope is that Cadence can avoid the
> classic pitfalls as they "assimilate" the Verplex product line.
>
> - Mike Bly of World Wide Packets, Inc.
From: Andrew MacCormack <andrewm=user domain=cadence got calm>
Hi, John,
I've recently been on a project where we're using Verplex a lot and have
just been in the training course. At least in the latest version of Verplex
LEC, you can say:
add notranslate module <module-name-plus-wildcards> -golden/-revised/-both
before reading in libraries or designs and it will black-box anything
matching your pattern(s) as it reads them in. This sound like what Mike Bly
was looking for... please forward to him, or post this in ESNUG.
Also, on a related note, the training course covered Verplex LEC Verify
which does a lot of the super-lint checks that tools like Implied Intent
deal with. This is BlackTie functionality which is now included with LEC,
too. I know this maybe sounds like a sales pitch, me coming from a Cadence
subsiduary, but I guess that a lot of your readers own LEC already and
didn't realise that this functionality was there (I know I didn't and I
work here...)
And on PSL, I was interested to see that it is starting to gain some
momentum. We've been starting to use it on Design Foundry projects, too;
sometimes it is just the easiest way to check for something. Also, running
ncvlog with the -assert option will also automatically create assertions
for your full_case and parallel_case statements, so you know if those
pragmas are being violated (this is also something that lec -verify checks
for, too.)
- Andrew MacCormack
Cadence Design Foundry Alba Campus, Scottland
|
|
