X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=gamma;
	h=date:from:to:subject:message-id:in-reply-to:references:x-mailer
	:mime-version:content-type:content-transfer-encoding;
	bh=UAg+QRrTJJ6aywkHGo7tSdYgn/lYxHZODnuvkZha/6Y=;
	b=HhTOsJwIPnt9hipj2jNAw7qlYW7G7AdyiguppE8NzMUNg3aQapd3m1sVDL2GWk4iX3
	waaKEAAez0xX339uOP8hiowP/Az6Vwmtikt8/zKzEjoi5UDvM5QdYndChLzDMHU4OIYX
	CJ8YEGea+Wt0+J8txqZs/9JXXQDA3asoFfWhs=
Date:	Thu, 17 Nov 2011 22:53:59 -0500
From:	Vanessa Ezekowitz <vanessaezekowitz AT gmail DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Modern GAL/PAL design with gEDA?
Message-ID:	<20111117225359.2fcf159a@rainbird>
In-Reply-To:	<4EC5CBEE.5060904@optonline.net>
References:	<20111117204524 DOT 10e586f5 AT rainbird>
	<4EC5CBEE DOT 5060904 AT optonline DOT net>
X-Mailer:	Claws Mail 3.7.6 (GTK+ 2.20.1; i486-pc-linux-gnu)
Mime-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id pAI3qfK3025593
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 17 Nov 2011 22:07:26 -0500
gene glick <geneglick AT optonline DOT net> wrote:

> - I see people designing things left and right using programmable logic 
> of one sort or another, some of which are of such complexity that it 
> would be next to impossible to do using just lists of logic equations.
> >
> > Whatever the case, I don't want to have to resort to using closed-source
> > or proprietary software or operating systems to do any more of this than
> > is absolutely necessary.
> >
> 
> 
> Regardless of your front-end design entry method, you will always use 
> closed-source proprietary tools for the back-end synthesis and 
> place/route. 

Well that part doesn't bother me too much - I expected that at least the final one or two steps would involve proprietary tools.  It's the process of getting from Gschem to the data those tools need that is lost on me.

> So plan on using Xilinx or Altera or Lattice etc., no 
> matter what.  You can use vhdl or verilog as inputs to just about any of 
> these tools.

I thought about using verilog, but this is where I've hit a brick wall - gnetlist is willing to generate a verilog file out of my schematic:

gnetlist -v -o test.v -g verilog -O tpal cbr-refresh.sch

...but aside from the numbered-pin warnings I understand I can ignore, all the resultant file contains are lines declaring each instantiation of the various symbols, and a list of wires - but with what looks like an incorrect "model" line and without anything suggesting the type of chip the file is actually targeted at, and nothing declaring how the internal signals are mapped to the device's pins.  Nothing I've found on the web tells me how to set these parameters.

> gschem -> gnetlist -> verilog -> programmable_logic_proprietary_tools

This is the sort of workflow I expected actually, but the problem is finding newbie-friendly information on how to accomplish each step.

-- 
"There are some things in life worth obsessing over.  Most
things aren't, and when you learn that, life improves."
http://digitalaudioconcepts.com
Vanessa Ezekowitz <vanessaezekowitz AT gmail DOT com>

- Raw text -