Stats

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

Maestro: Could not find state ..../spectre/active active

HoWei

Hi,

We do have 2 similar maestro views "maestro_lpe" and "maestro_sch". Both view do contain variables and outputs in the users workarea.

The user checked in the files in our revision control system SOS.

When checking out the cell by other users, the "maestro_sch" is not working. No variables and outputs are visible for other users after checkout of this cell. In the CIW the following message comes:

WARNING (ADE-1077): Could not find state /icd/sim/hflroic_g6r3/uidn5147/sos_main/sim/G6R3_tb/mm_test_sig_and_xt/maestro_sch/G6R3_tb/mm_test_sig_and_xt/spectre/active active.
WARNING (EXPLORER-1648): The 'G6R3_tb/mm_test_sig_and_xt/maestro_sch' cellview has been opened in the read-only mode.
       The setting for the number of history entries to be saved, specified using the
       Save Options form or the adexl.simulation saveLastNHistoryEntries environment
       variable, will be applied only to the histories created in this session.
       Histories saved in the previous sessions will not be removed.

When comparing the content of the view-folders of "maestro_sch" and "maestro_lpe" I see that a file "active.state" is only existing in "maestro_lpe". That is also true for the users folders - not only for the checked-out folders. But the user does see all outputs and variables.

What can be the problem here  - any idea ?

IC6.1.8.010 on RHEL6 and RHEL7

Parents
  • HoWei

    Apparently the file "active.state" is created when the "maestro_sch" is checked out and opened-for-edit. But the message in CIW still appears and the variables and outputs are not shown.

    It seems like the file "maestro.sdb" contains all these variables and outputs in the users workarea.

    But in the checked-out workarea this file does not contain the variables and outputs.

    There seems to be an issue with our revision control system, that it does not send the correct file content to the repository.

Reply
  • HoWei

    Apparently the file "active.state" is created when the "maestro_sch" is checked out and opened-for-edit. But the message in CIW still appears and the variables and outputs are not shown.

    It seems like the file "maestro.sdb" contains all these variables and outputs in the users workarea.

    But in the checked-out workarea this file does not contain the variables and outputs.

    There seems to be an issue with our revision control system, that it does not send the correct file content to the repository.

Children
  • Andrew Beckett
    in reply to HoWei

    This suggests that something has got lost (maybe in your Design Management system). The active.state contains all the test setup, whereas the maestro.sdb contains the overall view of all the tests including global variables.

    Perhaps your design management tool is not honouring the "co-managed set" (either because it's not properly using GDM or has an outdated replica of the same co-managed information).

    Regards,

    Andrew.

  • HoWei
    in reply to Andrew Beckett

    Can you explain what you mean with "co-managed-set" ?

  • Andrew Beckett
    in reply to HoWei

    If you run:

    UNIX> `cds_root virtuoso`/bin/dregprint -dataFormat Maestro


    DataFormat Maestro {
    Pattern = maestro.sdb;
      Default_Editor = Maestro-Editor;
      updaterProg = ccpAdexlUpdtr;
      Co_Managed = data.dm results/*/*.rdb results/*/*.log results/*/*.db *.state xmlstate maestro.sdb master.tag ScriptDir/* ScriptDir/.record ScriptDir/.recordDetail states/*     states/*/test_states/*/*/*/*/* states/*/test_states/*/*/*/*/.record states/*/test_states/*/*/*/*/.recordDetail states/*.sdb states/*/*.state states/*/ScriptDir/* states/*/ScriptDir/.record states/*/ScriptDir/.recordDetail documents/* documents/*/* documents/*/*/* documents/*/*/*/* documents/*/*/*/*/* documents/*/*/*/*/*/* documents/*/*/*/*/*/*/* datasheets/*.* states/*/test_states/*/*/*/*/.sevSaveDir waveformSetup/*/* test_states/*.state test_states/*.ScriptDir/* test_states/*.ScriptDir/.record test_states/*.ScriptDir/.recordDetail *.TCL;
    dfII_ViewType = maestro;
      Initial_File = maestro.sdb;
    }

    This tells you the pattern for the files that should be managed together. So that means that when you check in a cellView, all of the files must be managed together as they are interrelated. It's rather complicated because of legacy support for some unconverted files from ADE XL so in practice most of those files don't exist (the above is from IC618 by the way).

    Regards,

    Andrew

  • HoWei
    in reply to Andrew Beckett

    Our revision-control-system (Cliosoft SOS) does apply co-managed-sets to the cellviews - I checked that. The cellview is managed as one entity. I does not operate on separate file inside the cellview. The folder "maestro_sch" has only 3 files (data.dm, maestro.sdb, master.tag).

    The above comment, that the "maestro.sdb" is an empty file is not true anymore - after changing revision back and forth it was showing the correct content. May I did not properly update before - but the revision control system can be ruled out from the culprits.

    But problem remains.

    Then I copied the files from the users workarea directly to my workarea.

    But problem remains.

    Tried with IC6.1.7

    But problem remains.

    Any idea what the above WARNING (ADE-1077) means ?

    The file it is looking for does not exist in the user workarea at all.

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.