The output files for PADS layout should include the .p file. The .p file contains an association between the PADS part type and the PADS package type. This is leftover PADS cruft from the old days when parts were produced in the same pin out for through-hole and surface mount packages. The layout engineer could change the part to surface mount in order to make his layout work better.
Anyway, having the .p file helps the layout guy avoid a bunch of work creating the part-package associations.
I suggest we work on this when we get back to writing the PHDLIF to PADS converter.
Pete
Anonymous
Diff:
Guys, I bumped this one up also. .p file generation is really considered necessary to go into layout. A few experienced old guys like me know how to create that in PADS but others would just discard the PHDL -> PADS flow if it is not generated by us. I sent in an example .p file a long time ago. I'm sure I can provide another one if anybody can work on it. This .p file is not as important as the problem in the .asc netlist format.
I have talked to the guys about this one and it has not been implemented yet. Pete – can you point us in the right direction for info on the .p file structure, syntax, and content so we can get it implemented?
From: peter dudley padudle@users.sf.netamp#112;amp#97;amp#100;amp#117;amp#100;amp#108;amp#101;amp#64;amp#117;amp#115;amp#101;amp#114;amp#115;amp#46;amp#115;amp#102;amp#46;amp#110;amp#101;amp#116;
Reply-To: "[phdl:bugs]" 35@bugs.phdl.p.re.sf.netamp#51;amp#53;amp#64;amp#98;amp#117;amp#103;amp#115;amp#46;amp#112;amp#104;amp#100;amp#108;amp#46;amp#112;amp#46;amp#114;amp#101;amp#46;amp#115;amp#102;amp#46;amp#110;amp#101;amp#116;
Date: Tuesday, November 20, 2012 8:28 AM
To: "[phdl:bugs]" 35@bugs.phdl.p.re.sf.netamp#51;amp#53;amp#64;amp#98;amp#117;amp#103;amp#115;amp#46;amp#112;amp#104;amp#100;amp#108;amp#46;amp#112;amp#46;amp#114;amp#101;amp#46;amp#115;amp#102;amp#46;amp#110;amp#101;amp#116;
Subject: [phdl:bugs] #35 .p file is missing for PADS output option
Guys, I bumped this one up also. .p file generation is really considered necessary to go into layout. A few experienced old guys like me know how to create that in PADS but others would just discard the PHDL -> PADS flow if it is not generated by us. I sent in an example .p file a long time ago. I'm sure I can provide another one if anybody can work on it. This .p file is not as important as the problem in the .asc netlist format.
bugs:35http://sourceforge.net/../bugs:35 .p file is missing for PADS output option
Status: Open
Created: Sun Nov 18, 2012 11:34 AM UTC by peter dudley
Last Updated: Tue Nov 20, 2012 03:25 PM UTC
Owner: peter dudley
The output files for PADS layout should include the .p file. The .p file contains an association between the PADS part type and the PADS package type. This is leftover PADS cruft from the old days when parts were produced in the same pin out for through-hole and surface mount packages. The layout engineer could change the part to surface mount in order to make his layout work better.
Anyway, having the .p file helps the layout guy avoid a bunch of work creating the part-package associations.
I suggest we work on this when we get back to writing the PHDLIF to PADS converter.
Pete
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/phdl/bugs/35/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/prefs/