X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-SourceIP:	95.97.163.245
X-Authenticated-Sender:	b DOT mykendevelopment AT upcmail DOT nl
Message-ID:	<521CA130.70309@iae.nl>
Date:	Tue, 27 Aug 2013 14:53:04 +0200
From:	myken <myken AT iae DOT nl>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version:	1.0
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Tutorial: VHDL with gEDA
References:	<521B22D8 DOT 3030707 AT iae DOT nl> <CAMvDHVCZm+dYkFrbWoBMbnGvEv_nxr_OG+J3HM5EShhtd6kDBQ AT mail DOT gmail DOT com> <521C6317 DOT 7070605 AT iae DOT nl> <CAMvDHVCSRjqYw_wm7vO+qbX+bz373S=cvpN2zJ6_ZUC+WdL1bw AT mail DOT gmail DOT com> <521C7A68 DOT 1090900 AT iae DOT nl> <CAMvDHVD-CK77EbE7-LQUqQS-u0LJquX2U+3xAyr-J7ur8ikF4Q AT mail DOT gmail DOT com>
In-Reply-To:	<CAMvDHVD-CK77EbE7-LQUqQS-u0LJquX2U+3xAyr-J7ur8ikF4Q@mail.gmail.com>
Reply-To:	geda-user AT delorie DOT com

On 27/08/13 14:01, Vladimir Zhbanov wrote:
> First I should specify that I don't use vhdl myself.
> However, I followed your tutorial without modifying sources by
> your Perl script, and it gave me the result as follows:
>
> ENTITY xor1 IS
>      PORT (
>          Bi : in Std_Logic;
>          Ai : in Std_Logic;
>          Qo : out Std_Logic);
> END xor1;
>
> Is it right? (The result is compiled by ghdl without errors.)
>
> I also noticed that you don't set the pinseq attributes but AFAIK
> gnetlist uses them in its hidden job.
>

Crap, I've fallen into the confusion trap. Your right, gnetlist doesn't 
look at the pintype attribute in case of the ipad symbol instead it 
looks at the pinnumber attribute which should be set to "IPAD" for input 
signals. I think a pinnumber attribute should be a number, but well I 
work with what is available.
The VHDL code you show here is correct.

Like I write in the tutorial everything should work without any 
modification BUT it can be confusing to have an OUT printed inside an 
symbol which represents an input signal. Maybe I shouldn't use the word 
"bug". Should I just make the pintype attribute invisible then?
If time permits I would like to take this tutorial further and then it 
would be great if there is some consistency in attribute use.

Seams I'm caught between a technically correct definition of the pintype 
attribute and an easy to follow tutorial.

- Raw text -