Stats

  • Locked Locked
  • Replies 7
  • Subscribers 125
  • Views 15694
  • 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

auto sim with multiple dspf files for the same block

Karev11

Hi,


Is there a way to automate sims that replace same block with multiple dspf files?


thanks,

Kevin

  • Andrew Beckett

    Hi Kevin,

    I had hoped that it would be possible in ADE XL to do this via setting up a variable for the DSPF file name on the test editor Setup->Simulation Files form, filling in the DSPF file as (say) VAR("DSPFFILE") and then setting the variable DSPFFILE to be "file1.dspf","file2.dspf". Even with a single file name it doesn't work though (gives a syntax error during netlisting). This is probably a bug that needs fixing - you could contact customer support about this.

    Alternatively we've recently introduced the ability to have DSPF views in your library under each cell. However, there was not support for multiple such views initially and via CCR 1661606 this will be fixed in IC617 ISR10. Then you could have a config view to specify one of them, and through the ADE XL feature of being able to do "Add Config Sweep" (right mouse button menu over global variables) you could sweep the view. 

    Regards,

    Andrew.

  • Karev11
    Thanks Andrew for the reply.

    I tried the 2nd method as you mentioned. Not exactly sure what should be placed in the dspf view, I simply put the path to my dspf.gz file and it doesn't seem working. There's netlist error:

    ERROR (OSSHNL-381): Missing or corrupt .oa file in cellview 'lib_A/cell_A/dspf_rcworst'. The OSS netlister can only
    process cellviews that have a valid .oa file. This file can be created by
    either importing the cellview using tools like 'Verilog In' or 'VHDL IN', or by
    opening and writing the text file in the Library Manager.

    Also, in setup->sim files, I often specify port order = spf, buf delimiter ="<> []", how should these be included into the dspf view?

    Thanks,
    Kevin
  • Andrew Beckett

    Kevin,

    To use a DSPF view, you have to be using IC617 ISR8 (or ICADV123) or later; prior to that the view existed, but the support to create the supporting database to allow netlisting wasn't enabled. With that version, the contents of the DSPF file has to be pasted into the view (so it being gzipped wouldn't work either).

    As I said, support for multiple such views is only coming in a future release (due mid-March). Support for the advanced options to set bus delimiters hasn't been added  yet - that's requested in CCR 1397832.

    Kind Regards,

    Andrew.

  • Karev11
    OK, looks like my option at this point is requesting a fix for VAR("DSPFFILE") method then. whch should be more convenient if fixed.
    Thanks!
    Kevin
  • Andrew Beckett

    Hi Kevin,

    When you do that, can you post the case number here, so that I can track the request (and provide support if needed to encourage implementation of this feature)?

    Thanks,

    Andrew.

  • Karev11
    Hi Andrew,
    the case number is : 46073499

    Thanks,
    Kevin
  • Karev11

    Hi Andrew,

    The solution from Cadence AE is to use dspf view, which just as you mentioned, requires copy and paste dspf files. I stopped half-way trying to implement it: 1. starRC extraction by default generates dspf.gz files and in my case they are >6MB, it seems to take forever to unzip just one. 2. limit of file editor buffer size will probably require multiple copy and paste, will could also be troubling.  3. multiple views will multiply the effort required from 1 and 2.

    AE didn't comment on setting up a variable and pointing to different .dspf.gz files, which would be the ideal solution in my opinion. Do you mind taking a look at the status here: is it going to a new feature or a bug that needs to be fixed?

    Thanks,
    Kevin

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.