Stats

  • Locked Locked
  • Replies 4
  • Subscribers 164
  • Views 14068
  • Members are here 0
More Content
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

Constraint Manager Deleting User Defined Properties during DCF import.

pdxg8r

Hey All,

I'm  seeing something very interesting with constraint manager between 2 different databases

 Here's the situation:

If I import a database-specific DCF file using the Overwrite option in Constraint Manager on DatabaseA, my user-defined PROPERTY definitions on my components are deleted.

If I do the same thing to DatabaseB, the user-defined PROPERTY definitions are left in tact.

The contents of the DCF files are the same in the sense that they contain the same type of information.

 Can anyone think of why CM would delete PROPERTY def's in one instance and not another?

 

Thanks in advance!

  • eDave
    Property flow is controlled by the propflow.txt file that is in the cdssetup folder (at the same level as the cpm). If this is present in your design it will override the default site file.
  • pdxg8r
    Thanks for the response Dave, I'm a bit confused. You said that if it's present in my design. Would the database be pointing to it somehow in a setting? I found propflow.txt in my cadence\spb16.3\share\cdssetup\ directory, But the property that is being erased is not there. Do I need to add it to that file? Thanks again.
  • eDave
    If there is a propflow.txt file in the cdssetup folder at the same level as your project cpm, your flow will ignore the file in cadence\spb16.3\share\cdssetup\. Only the properties listed in the file will transfer. The file is managed through the Packager Setup utility/Property Flow Setup in your Project Manager tools menu.
  • fxffxf

    In the dcf file, you should look at the origin flag (Origin attribute in dcf) for the property definitions in question. I would bet that the Allegro DatabaseB for the properties defs left intact are set to gBackEnd while Allegro DatabaseA has another setting for those properties (like gFrontEnd). To see these origin flags in the Allegro Database, you would need to export a dcf file.

Cadence Guidelines

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.