Hello Gary,
The reason that we do not swap pins is because first of all the library
parts are not created as swappable I am told.
Secondly, doesn't Concept actually change the symbol (.body)?
Meaning that if pins 1234 were swapped to 1324 that the pin numbers
would swap in schematic, but NOT the pin names if only text?
And if the schematic .body was replaced or refreshed, would then be wrong.
Scary! Is this still the way it is?
I would love to swap pins, but this is the way it was described to me.
In the past, I had done it in other software that generated a WAS / IS
file and net list compare.
Thanks, Mark
Gary MacIndoe wrote:
William,
This has been a real PITA for me for a long time now. After I do rpak swaps, the engineer (using Concept HDL) does an import physical, then an export physical to complete a full loop to make sure we are in sync. If things change and I want to redo the rpak swaps, this bothersome NO_SWAP_GATE property (sometimes also NO_SWAP_GATE_EXT is there) is on some of the rpak sections and I have to remove it before I can swap function again.
We thought we had it figured out once but it turned out not to work (it looks like it should have worked!), in Program Manager:
- load in your *.cpm file
- click on Setup
- in the Tools tab, click on Setup... next to Packager-XL
- in the Properties tab, click on Property Flow Setup...
- in the Name column, find NO_SWAP_GATE (and NO_SWAP_GATE_EXT)
- click the box to remove the check in the Defined In Concept column for the above properties
- OK out of the Program Manager Setup windows
This should prevent Concept from reapplying the above properties, but it didn't work for us. We haven't tried it for a while, maybe it really works now!
Good luck!
Gary E. MacIndoe PCB Design Engineer Advanced Micro Devices, Inc. Longmont, Colorado
-----Original Message----- From: William Billereau [mailto:william.billereau@xxxxxxx] Sent: Tuesday, January 18, 2005 3:20 AM To: icu-pcb-forum@xxxxxxxxxxxxx Subject: [PCB_FORUM] LOCATION feedback
Hello All.
The packager assigns, the first time it runs, $LOCATION on Concept
parts.
After component placement and swaps, we backannote them on the BRD
and feedback changes to Concept.
Then some $LOCATION are changed to LOCATION (not all, but
especially component were swap pins or functions was made)
The same thing occurs with $PN properties that become PN
If you copy in the design a component with a LOCATION, it copies
the whole property (name and value) to the copy and the next
packaging will fail with such errors because of two instances of
LOCATION:
#1 ERROR(1109): Cannot package instance into package C59.
Schematic instance:
@TTCCI_LIB.TTCCI_TOP(SCH_1):PAGE1_I5@xxxxxxxxxxxxx~
CI_VME(SCH_1):PAGE1_I469@xxxxxxxxxxxxxxxxxxxxxx(CHIPS) (MODULE:
TTCCI_VME; PAR~
T: CAPCERSMDCL2)
Section 1 is assigned
@TTCCI_LIB.TTCCI_TOP(SCH_1):PAGE1_I5@xxxxxxxxxxx~
TCCI_VME(SCH_1):PAGE1_I143@xxxxxxxxxxxxxxxxxxxxxx(CHIPS) (MODULE:
TTCCI_VME; P~
ART: CAPCERSMDCL2)
#2 ERROR(101): Primitive
@TTCCI_LIB.TTCCI_TOP(SCH_1):PAGE1_I5@xxxxxxxxxxxxxx~
I_VME(SCH_1):PAGE1_I469@xxxxxxxxxxxxxxxxxxxxxx(CHIPS) is not packaged.
#3 ERROR(100): State file not written for design TTCCI_TOP.
And swaps (in the case of PN) are no more allowed (NO_SWAP_GATE
properties are attached to functions.
Does anybody know how to avoid this?
Thanks in advance.
William.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
_____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________
