[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnucap-devel] language plugin help
From: |
al davis |
Subject: |
Re: [Gnucap-devel] language plugin help |
Date: |
Sun, 15 Apr 2012 11:54:46 -0400 |
User-agent: |
KMail/1.13.5 (Linux/2.6.32-5-amd64; KDE/4.4.5; x86_64; ; ) |
On Sunday 15 April 2012, John Griessen wrote:
> since when I've tried using verilog-a gnetlist output
> with gnucap in the past, I only got partial functioning.
That's true.
To Felix and others .... John is referring to the "verilog"
target of gnetlist, a part of gEDA, which is not part of Gnucap.
The verilog target of gnetlist does not pass attributes, which
are essential to the use of it with gnucap. Also, the pin names
are wrong in the sense that they do not follow established
naming conventions.
Gnucap's verilog input is "partial" too in the sense that it
requires a netlist item to be on one line.
I can post an example ...
A resistor that should be outputed as:
resistor #(.r( 3.)) R1 (.p(1),.n(2));
is actually outputed as:
RESISTOR R1 (
.\2 ( unnamed_net1 ),
.\1 ( unnamed_net6 )
);
The defects:
1. No value for the resistor.
2. Pin names are "\2" and "\1". They should be "p" and "n".
The problem is partly with the symbol. That is where the pin
names are specified, and that is where the attributes come from.
The pin name problem and attribute naming issue are common to
both John's and Savant's work.
The single line issue is a gnucap problem.
Re: [Gnucap-devel] language plugin help, address@hidden, 2012/04/15