From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] arduino and plan9
Date: Wed, 11 Sep 2013 11:55:17 +0200 [thread overview]
Message-ID: <79ec8739de0c9bf7b873d93a7b4038fe@proxima.alt.za> (raw)
In-Reply-To: <b2aa4274de0e7c0db595ea03c8681647@quintile.net>
> Anyone used forsyth's atmel compiler (other than himself of course)?
Never got around to it, but I recall building it afresh recently, I
can't quite remember how it panned out.
There's an avr-gcc distribution that is very easy to install on Linux
or Windows and pretty much without peer. Winavr is the name for the
Windows version. Not that I'm knocking forsyth's efforts, but if you
want immediate results, that would be my choice.
That said, the arduino software is also quite usable, despite its
roots. Takes very little getting used to, but I've only used in a
Linux environment. That is talks JTAG (at least, that's what I think
it does: you can program the board through USB without shedding a drop
of blood, courtesy of AVRDUDE) is definitely an asset in my book.
++L
prev parent reply other threads:[~2013-09-11 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 8:54 Steve Simon
2013-09-11 9:55 ` lucio [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=79ec8739de0c9bf7b873d93a7b4038fe@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).