it looks like PHDL compiler 2.1 has a bug. In the PART section all the parts are listed like this (refdes devices@footprint):
PART
J1 devices@PJ-002AH-SMT
MTG1 devices@MOUNT_HOLE_125
OSC1 devices@CB3LV-3I
PS1/C3 devices@CC0805
PS2/C43 devices@TANT3528
PS2/C5 devices@CC0603
X/D8 devices@LED_1113F
X/D9 devices@LED_1113F
X/P1 devices@MOLEX-87332-1420
The "devices" is coming from the file name, devices.phdl, that holds the device definitions. The "devices" string should be the device name. For example:
X/P1 devices@MOLEX-87332-1420
should be
X/P1 JTAG_CONN@MOLEX-87332-1420
How are you guys working with this?
Pete
Anonymous
Guys, I talked to Chuck and he has basically the same problem in the 2.0 compiler.
I bumped up the priority because he is ready to go into layout and he needs to be able to generate a correct netlist (.asc) file.
Hey Pete,
I'll take a look at it.
I think it should be a fairly simple fix.
I think the bug probably hadn't been found yet since we've been mainly
using eagle and just now looking into altium.
Josh
On Tue, Nov 20, 2012 at 8:24 AM, peter dudley padudle@users.sf.net wrote:
Hey Pete,
When I looked at it, it looks like the generator is working correctly.
The "devices" string is being pulled from the LIBRARY attribute in each of
your device definitions in the devices.phdl file, which all seem to be set
to "devices". The generator pulls from the FOOTPRINT and LIBRARY required
attributes to create the .asc file.
The generated output looks like this:
REFDES LIBRARY@FOOTPRINT
Looking at your email and the devices.phdl file in the refdesign folder, it
looks like this is happening correctly.
Is this the format you think is correct for a .asc file?
Josh
On Tue, Nov 20, 2012 at 11:06 AM, Joshua Mangelson joshuagm@users.sf.netwrote:
I seem to remember this change happening when it was requested that the
device name needed to support all sorts of special characters to allow
consistency with the names from PADS libraries. We thought at the time the
best way to fix it would be to pull from a quoted attribute (which didn't
have any restrictions on characters) instead of using the device name which
was constrained to conventional identifier rules in traditional programming
languages. Hence the LIBRARY attribute was born. If you modify the
library attribute in each device and give it your device name, it should
fix the problem.
On Tue, Nov 20, 2012 at 12:51 PM, Joshua Mangelson joshuagm@users.sf.netwrote:
Ok,
I understand how it works. I guess LIBRARY is a little bit of a misnomer. I
had no idea what it did.
It is not a bad idea to have a completely unconstrained attribute for this
purpose. Perhaps, PARTNAME or something would be more natural. On the other
hand, we could probably just use the name of the device. Perhaps, that
would be the default and only if a LIBRARY (or PARTNAME) attribute is
defined it would override the device name in the netlist generation.
Let's do nothing for now until we figure out what happens with PHDLIF.
Pete
From: Brad [mailto:briching@users.sf.net]
Sent: Tuesday, November 20, 2012 10:16 PM
To: [phdl:bugs]
Subject: [phdl:bugs] Re: #37 PADS .asc output incorrect.
I seem to remember this change happening when it was requested that the
device name needed to support all sorts of special characters to allow
consistency with the names from PADS libraries. We thought at the time the
best way to fix it would be to pull from a quoted attribute (which didn't
have any restrictions on characters) instead of using the device name which
was constrained to conventional identifier rules in traditional programming
languages. Hence the LIBRARY attribute was born. If you modify the
library attribute in each device and give it your device name, it should
fix the problem.
On Tue, Nov 20, 2012 at 12:51 PM, Joshua Mangelson
joshuagm@users.sf.netwrote:
Hey Pete,
When I looked at it, it looks like the generator is working correctly.
The "devices" string is being pulled from the LIBRARY attribute in each of
your device definitions in the devices.phdl file, which all seem to be set
to "devices". The generator pulls from the FOOTPRINT and LIBRARY required
attributes to create the .asc file.
The generated output looks like this:
REFDES LIBRARY@FOOTPRINT
Looking at your email and the devices.phdl file in the refdesign folder, it
looks like this is happening correctly.
Is this the format you think is correct for a .asc file?
Josh
On Tue, Nov 20, 2012 at 11:06 AM, Joshua Mangelson joshuagm@users.sf.net
wrote:
Hey Pete,
I'll take a look at it.
I think it should be a fairly simple fix.
I think the bug probably hadn't been found yet since we've been mainly
using eagle and just now looking into altium.
Josh
On Tue, Nov 20, 2012 at 8:24 AM, peter dudley padudle@users.sf.net wrote:
Guys, I talked to Chuck and he has basically the same problem in the 2.0
compiler.
I bumped up the priority because he is ready to go into layout and he
needs to be able to generate a correct netlist (.asc) file.
incorrect.*
Status: Open
Created: Tue Nov 20, 2012 01:26 PM UTC by peter dudley
Last Updated: Tue Nov 20, 2012 01:26 PM UTC
Owner: nobody
it looks like PHDL compiler 2.1 has a bug. In the PART section all the
parts are listed like this (refdes devices@footprint):
PART
J1 devices@PJ-002AH-SMT
MTG1 devices@MOUNT_HOLE_125
OSC1 devices@CB3LV-3I
PS1/C3 devices@CC0805
PS2/C43 devices@TANT3528
PS2/C5 devices@CC0603
X/D8 devices@LED_1113F
X/D9 devices@LED_1113F
X/P1 devices@MOLEX-87332-1420
The "devices" is coming from the file name, devices.phdl, that holds the
device definitions. The "devices" string should be the device name. For
example:
X/P1 devices@MOLEX-87332-1420
should be
X/P1 JTAG_CONN@MOLEX-87332-1420
How are you guys working with this?
Pete
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/phdl/bugs/37/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/prefs/
incorrect.*
Status: Open
Created: Tue Nov 20, 2012 01:26 PM UTC by peter dudley
Last Updated: Tue Nov 20, 2012 03:24 PM UTC
Owner: nobody
it looks like PHDL compiler 2.1 has a bug. In the PART section all the
parts are listed like this (refdes devices@footprint):
PART
J1 devices@PJ-002AH-SMT
MTG1 devices@MOUNT_HOLE_125
OSC1 devices@CB3LV-3I
PS1/C3 devices@CC0805
PS2/C43 devices@TANT3528
PS2/C5 devices@CC0603
X/D8 devices@LED_1113F
X/D9 devices@LED_1113F
X/P1 devices@MOLEX-87332-1420
The "devices" is coming from the file name, devices.phdl, that holds the
device definitions. The "devices" string should be the device name. For
example:
X/P1 devices@MOLEX-87332-1420
should be
X/P1 JTAG_CONN@MOLEX-87332-1420
How are you guys working with this?
Pete
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/phdl/bugs/37/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/prefs/
incorrect.*
Status: Open
Created: Tue Nov 20, 2012 01:26 PM UTC by peter dudley
Last Updated: Tue Nov 20, 2012 03:24 PM UTC
Owner: nobody
it looks like PHDL compiler 2.1 has a bug. In the PART section all the
parts are listed like this (refdes devices@footprint):
PART
J1 devices@PJ-002AH-SMT
MTG1 devices@MOUNT_HOLE_125
OSC1 devices@CB3LV-3I
PS1/C3 devices@CC0805
PS2/C43 devices@TANT3528
PS2/C5 devices@CC0603
X/D8 devices@LED_1113F
X/D9 devices@LED_1113F
X/P1 devices@MOLEX-87332-1420
The "devices" is coming from the file name, devices.phdl, that holds the
device definitions. The "devices" string should be the device name. For
example:
X/P1 devices@MOLEX-87332-1420
should be
X/P1 JTAG_CONN@MOLEX-87332-1420
How are you guys working with this?
Pete
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/phdl/bugs/37/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/prefs/
bugs:37 http://sourceforge.net/../bugs:37 PADS .asc output incorrect.
Status: Open
Created: Tue Nov 20, 2012 01:26 PM UTC by peter dudley
Last Updated: Tue Nov 20, 2012 03:24 PM UTC
Owner: nobody
it looks like PHDL compiler 2.1 has a bug. In the PART section all the parts
are listed like this (refdes devices@footprint):
PART
J1 devices@PJ-002AH-SMT
MTG1 devices@MOUNT_HOLE_125
OSC1 devices@CB3LV-3I
PS1/C3 devices@CC0805
PS2/C43 devices@TANT3528
PS2/C5 devices@CC0603
X/D8 devices@LED_1113F
X/D9 devices@LED_1113F
X/P1 devices@MOLEX-87332-1420
The "devices" is coming from the file name, devices.phdl, that holds the
device definitions. The "devices" string should be the device name. For
example:
X/P1 devices@MOLEX-87332-1420
should be
X/P1 JTAG_CONN@MOLEX-87332-1420
How are you guys working with this?
Pete
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/phdl/bugs/37/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/prefs/