Stats

  • State Not Answered
  • Replies 5
  • Subscribers 24
  • Views 5935
  • Members are here 0
More Content

Component RefDes / page number problem - Allegro Design Entry HDL (17.2-2016)

skus

Hi,

In the schematic, I use the code below for Ref Des Pattern to assign refdes according to their corresponding page numbers.

($PHYS_DES_PREFIX)($PHYS_PAGE)[0-9](01) or

($PHYS_DES_PREFIX)($PAGE)[0-9](01)  - i don't know the difference to be honest but they both work.

I am not sure if that's a correct approach but it usually works. There is one exception. If I copy or cut some components from another page and paste them to a new page, with this code, sometimes the refdes is assigned with their previous page numbers but not with their current one. How can I fix this?

thanks

Parents
  • S0undman99
    0

    I think that the key is that you have to do a "Save Hierarchy" before you package. What that does is it will basically re-save the instances of the components you copied to that specific page. Nothing 'wrong' with not doing that Save Hierarchy, it just doesn't do a full save of all the details to all the schematic pages.

    FYI, I use the second example there (just $PAGE), and it works great.  I believe that's what is in the help guides and such too.  Also, I think that PHYS_PAGE will be different than PAGE if you were to start adding pages and/or moving pages from one place to another in your design.

    Also, a trick, if you want to "override" the page, then you can add a property to the components called "PAGE", and the packager will take that.  So, like when we went to a 10-page schematic once, I took all the components on page 10 and gave them a "PAGE" property with the value set to "A", so I would get UA01 and UA02 (I basically told Concept that i wanted this to be page "A")

  • skus
    0 in reply to S0undman99

    Thanks for the recommendations. I tried "Save Hierarchy" but it didn't work. I also tried adding a custom property named "PAGE". But it didn't work either. Cadence still uses the old page number.

    I tried something else. I changed the code like this:

    ($PHYS_DES_PREFIX)($MADEUP)[0-9](01)

    I added a property named $MADEUP. I assumed it will take the variable under $MADEUP but it still uses the old page number in the refdes! I really don't understand how or why it is happening.

  • S0undman99
    0 in reply to skus

    are you using the "Repackage" option when you are running the export physical command?  You may need to reset to "$LOCATION=?" and then use the repackage option.  if that doesn't work, then I"m sorry, but I don't know what's happening, and I would reach out to Cadence support.

Reply
  • S0undman99
    0 in reply to skus

    are you using the "Repackage" option when you are running the export physical command?  You may need to reset to "$LOCATION=?" and then use the repackage option.  if that doesn't work, then I"m sorry, but I don't know what's happening, and I would reach out to Cadence support.

Children
  • skus
    0 in reply to S0undman99

    Yes I use "repackage" option and reset the $LOCATION to ? via global property change. I will try to reach Cadence support. Thanks for the help!

  • Raam PCB
    0 in reply to skus

    Hi, go to view / console window, on console window enter "hier_write -forcereset" and hit enter. the hierarchy page will get reset and saved. keep file backup before you do this procedure.

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.