Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 14197
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Convert Assura .rul to Diva?

goofycat

Hello,

 

1. Assura may need to be installed separately. However, is Diva always installed alongside Virtuoso?

a) which executable file or shared libraries (.so), or paths should we check for Dvia's existence?

 

2.

Moderator: Excerpt removed because of concerns about potentially posting confidential material.

    This is an excerpt from "~ /1P6M_1.8V_3.3V_MM_RF/Assura/drc/drc.rul". Although it is listed under folder named Assura, almost all commands are Diva commands/syntax.

    a) Is Assura a superset of Diva and supports all Diva commands?

    b) Given that there is RCX tool (Dracula to Assura) exists which converts Dracula to Assura, and in view of the many same commands in Assura .rul files as to those in Diva .rul files, is there any official tool for converting Assura .rul to Diva .rul file?

     

     

    3) I am confused between Diva and Dracula. From GXL>Verify, Virtuoso seems to be prepared to launch Diva (from the divaDRC.rul filename). Is Diva the default choice for verification, instead of Dracula?

     

     

    G

    Parents
    • Andrew Beckett

      Some answers:

      1. Diva is installed without you needing to do anything else; it's linked in with Virtuoso
      2. Note - you should be wary of posting rule decks here as you're probably breaking an NDA with the foundry they came from (I don't know who). It may be something that you own, so that might not be the case - I'm just giving a warning (I'll edit your post to remove the material just in case). Anyway:
        a) It is a superset, but Assura may require some changes to Diva rules to make them work properly in Assura. There is a translator divaToAssura (as part of the ASSURA package) which does this - although that is intended more as a starting point rather than a fully-qualified out of the box tool.
        b) No. If the foundry provides rules for Assura, you should use Assura rather than trying to make them work in Diva. I see little reason to do this (it would be rare for an organisation to only have licenses for Diva, and not for Assura or PVS; Assura can be run using Assura or PVS licenses). Yes, you have to install the ASSURA stream, but other than that it's straightforward.
      3. There is no "default choice". Dracula is an older (slightly) verification tool than Diva, but the focus was very much on batch verification and so you ran Dracula from the command line. There is a product called Dracula Interactive (Launch->Plugins->Dracula Interactive) which was for the debug of the Dracula results, but for launch you ran from the command line. With Diva, the focus was more on interactive verification within Virtuoso - similarly with its predecessor PDV in the Edge tools - and hence the presence of the Verify menu within the Virtuoso Layout Suite. Note that if you add Assura or PVS you also get menus in the layout editor to launch them and debug the results.

      Regards,

      Andrew.

    Reply
    • Andrew Beckett

      Some answers:

      1. Diva is installed without you needing to do anything else; it's linked in with Virtuoso
      2. Note - you should be wary of posting rule decks here as you're probably breaking an NDA with the foundry they came from (I don't know who). It may be something that you own, so that might not be the case - I'm just giving a warning (I'll edit your post to remove the material just in case). Anyway:
        a) It is a superset, but Assura may require some changes to Diva rules to make them work properly in Assura. There is a translator divaToAssura (as part of the ASSURA package) which does this - although that is intended more as a starting point rather than a fully-qualified out of the box tool.
        b) No. If the foundry provides rules for Assura, you should use Assura rather than trying to make them work in Diva. I see little reason to do this (it would be rare for an organisation to only have licenses for Diva, and not for Assura or PVS; Assura can be run using Assura or PVS licenses). Yes, you have to install the ASSURA stream, but other than that it's straightforward.
      3. There is no "default choice". Dracula is an older (slightly) verification tool than Diva, but the focus was very much on batch verification and so you ran Dracula from the command line. There is a product called Dracula Interactive (Launch->Plugins->Dracula Interactive) which was for the debug of the Dracula results, but for launch you ran from the command line. With Diva, the focus was more on interactive verification within Virtuoso - similarly with its predecessor PDV in the Edge tools - and hence the presence of the Verify menu within the Virtuoso Layout Suite. Note that if you add Assura or PVS you also get menus in the layout editor to launch them and debug the results.

      Regards,

      Andrew.

    Children
    • goofycat
      in reply to Andrew Beckett

      Thanks very much, questions are all resolved.

    Community Guidelines

    The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.