|
From: Peter D. <hd...@ho...> - 2012-11-27 11:02:54
|
Guys,
I paste here the .p file for the little test design I did. It looks like
just the "*PADS-LIBRARY-PART-TYPES-V9*" section is required. In the .pdf
file that is called Part Type Definition.
For each part type there is an entry. The first item comes from the
DxDesigner DEVICE attribute. I think we decided to use an attribute called
LIBRARY in PHDL (Let's reconsider that sooner or later.)
The second item comes from the DxDesigner PKG_TYPE attribute. We use the
FOOTPRINT attribute in PHDL.
In the specification there is some historical cruft. I don't think we ever
want more than one "pcbdecals". The rest can always be "I TTL 0 1 0 0 0".
In the Gate Format, I think we want to make everything a "normal part" and
avoid gate swapping. That is:
GATE 0 N 1
where N is the number of pins on the part. Then there is a list of pins by
alphanumeric pin number. We don't want to allow pinswap and we don't care
whether the pin is source, load, ground or whatever. We can make them all
source (S).
So below CAP_0603 should come from our LIBRARY attribute and CC0603 should
come from the FOOTPRINT attribute.
***************************************************
*PADS-LIBRARY-PART-TYPES-V9*
ATX12V ATX12V I TTL 0 1 0 0 0
GATE 0 6 1
6 0 S
5 0 S
4 0 S
1 0 L
2 0 L
3 0 L
CAP_0603 CC0603 I TTL 0 1 0 0 0
GATE 0 2 1
2 0 L
1 0 L
PC28F128P30 PC28F128P30 I TTL 0 1 0 0 0
GATE 0 64 1
A1 0 L
C3 0 L
D3 0 L
C4 0 L
A5 0 L
B5 0 L
C5 0 L
D7 0 L
D8 0 L
A7 0 L
B7 0 L
B1 0 L
C7 0 L
C8 0 L
A8 0 L
G1 0 L
C1 0 L
D1 0 L
D2 0 L
A2 0 L
C2 0 L
A3 0 L
B3 0 L
F6 0 L
B4 0 L
E6 0 L
F2 0 B
E2 0 B
F3 0 B
F4 0 B
F5 0 B
H5 0 B
G7 0 B
E7 0 B
G3 0 B
E4 0 B
E5 0 B
G5 0 B
G6 0 B
H7 0 B
E1 0 B
E3 0 B
F8 0 L
B6 0 S
B8 0 S
E8 0 S
F1 0 S
G2 0 S
H1 0 S
H8 0 S
D4 0 L
A6 0 L
H3 0 L
D5 0 L
D6 0 L
G4 0 L
A4 0 L
B2 0 L
H2 0 L
H4 0 L
H6 0 L
F7 0 S
G8 0 L
C6 0 L
*END*
From: Joshua Mangelson [mailto:jos...@gm...]
Sent: Monday, November 26, 2012 11:53 PM
To: Peter Dudley
Cc: <phd...@li...>
Subject: Re: [phdl-devel] .p file info
Here is the PADS documentation for the the .p file.
Josh
On Wed, Nov 21, 2012 at 4:22 AM, Peter Dudley <hd...@ho...> wrote:
Guys,
I pulled up my Mentor tools to see how the .p file works. I also contacted
the Mentor support line to see if they have a document describing that
format.
Right now I can give you an example file.
Here is the simple schematic.
<<...>>
Here is the .asc file that came out of it.
<<...>>
And here is the .p file that came out.
<<...>>
I tried deleting parts of the .p file but it seems to all be needed. The
last column on the pin listings is either S, L or B but I don't know what
that column means. I tried changing them all to L and that worked fine.
Pete Dudley
hd...@ho...
www.HDLGuy.com
----------------------------------------------------------------------------
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
phdl-devel mailing list
phd...@li...
https://lists.sourceforge.net/lists/listinfo/phdl-devel
|