Stats

  • Locked Locked
  • Replies 4
  • Subscribers 164
  • Views 13820
  • 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

enhanced part development for DEHDL

hoki

 Hello,

 how can we handle a part with different pack_types (jedec_types) and different symbols (for DEHDL)?

Symbols (Symbol versions: sym_1, sym_2, sym_3) have different pin counts and if we choose over pack_type a part with 4 pins, DEHDL shall be use the correct SYM_n version with 4 pins. Other symbols have more or less pins.

We don't want a diffrent section of pins, we want different symbols for each pack_type.

This is required to handle e.g. different mosfet types in one part entry of a part table to filter over all available mosfets in the component browser. And there are diffrerent jedec_types with e.g. 2 / 3 /  .. DRAIN or SOURCE pins.

 

 

 

  • chads108

     Should be easy in Part Developer.  Create the different pack_types and then the different symbols.  Then make sure the association of symbols to appropriate pack_type is correct.

    Chad

  • hoki

     Hi Chad,

    thanks for the answer. Yes it works with Part Developer. But I'm little confuse, that this association information is stored in ../metadata/revision.dat and not in chips.prt ??!! Normally all important information shall be stored in chips.prt.

    Only the Component Browser looks into the association information stored inside revision.dat. But ConceptHDL ignore the information and you can use features "version" and "modify" and get not the correct sym related to choosen pack_type.

    I think this is a very poor implemented feature.

    My expectations are:

    * association is stored inside chips.prt in the body section

    * DEHDL handle the association: "version" and "modify" shows only the matching symbols (related to the choosen packtype) 

     What do you think?

      

     

  • chads108

    The association data is not stored in the revision.dat file.  It just stores version information for a part.  Here is a quote from the User Guide:

    "The information stored are the name of the view, the type of the view, major and minor revision numbers, the date and time of creation, the name of the creator, the library to which the part belongs, and the modification history." 

    You can actually delete this file and still place the symbol just fine, so actually, the important data is stored in the chips.prt file, such as the association.  Now as you stated, yes, you can manuall modify, or version the symbol in DE HDL, but you can do that with pretty much any symbol.  My suggestion would be, don't do that.  It will most likely not package correctly.

    In summary, if you place the components using Part Browser, you shouldn't have a problem.  If you start manually changing things, you will probably run into problems.  Could everything be locked down programmatically?  Probably, but then you loose the flexibility of the product.  What would then work for you, might not work for somebody else.

     Chad

  • hoki

     Yes it is correct, I deleted metadata and it still works.

    But, I have another opinion: If Part Browser can handle the version of symbols correct, DEHDL commands like version or modify should it also. Why I need flexibility when the result could be a problem?

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.