From: Christof Bodner <oe8bck@gmx.net>
To: linux-hams@vger.kernel.org
Subject: Re: KPC3+ open-source code?
Date: Sun, 04 Jan 2009 17:10:03 +0100 [thread overview]
Message-ID: <1231085403.6565.0.camel@rosi> (raw)
Am Montag, den 22.12.2008, 13:56 -0800 schrieb Curt, WE7U:
> *) Open hardware for my shack which I could write new code for would
> definitely be on my wish list. Whether that's doing my own
> AVR-based TNC, helping with somebody else's AVR project, or waiting
> for Scott's next ARM-based TNC, I don't know. I'm picky about
> processors and compilers. I'm not a PIC fan. The stuff Scott did
> with the OpenTracker series and Motorola processors is great, but
> the compilers cost $$. Byon with his TT4/AVR project is heading in
> the right direction, but as far as I know it's not open-source. If
> he has a "normal" bootloader in it perhaps it can be used for other
> things via a GCC cross-compiler.
>
There is an AVR-based APRS module already available:
http://www.ralfwilke.com/amateurfunk/aprs_tracker/
(this site is in german, but try the Babelfish:
http://babelfish.yahoo.com/ it's not perfect, but you get a feeling of
what's about)
The hardware and software is based on
http://garydion.com/projects/whereavr/ and a kit is available at
http://www.beta.df6ef.de/index.php?option=com_content&task=view&id=57&Itemid=98
Worse luck, it's not! I mailed DF6EF for a kit but he said, this boards
were hand-made and he has no time make more of them. But he said, he
will contact me in case he gets professionally fabricated ones. For this
he needs orders. So who wants to join?
OK, it's "only" an APRS-module but we could think of a processor with a
bigger FlashRAM and/or higher clock rate for more complexity. The best
of all is, that there is an already working software. And the compliler
with the complete IDE is for free. And there is also a very cheap
possibility to program the controller, it's the parallel port. If you
want to see more, have a look at http://www.avrfreaks.net
So this is a "classical" HAM-approach. I'm very much in favor of such a
piece of crap ;-)
73 de Christof, OE8BCK
--
(0-0)
---------oOO--(_)--OOo-----------------------------------------------
Christof Bodner <oe8bck@gmx.net>
Linux - Life is too short for reboots
- First they ignore you. Then they laugh at you. Then they
fight you(*). Then you win. -- Ghandi
---------------------------------------------------------------------
email: mailto:oe8bck@gmx.net
Locator: JN76DO
---------------------------------------------------------------------
GnuPG public key: 0xB15DA60F (http://wwwkeys.eu.pgp.net)
Fingerprint 5222 4DEA 773A 60B3 22F9 D244 15EF 6645 B15D A60F
---------------------------------------------------------------------
next reply other threads:[~2009-01-04 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 16:10 Christof Bodner [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-22 23:41 KPC3+ open-source code? Chris Kantarjiev
2008-12-19 23:02 Chris Kantarjiev
2008-12-22 21:56 ` Curt, WE7U
2008-12-22 23:37 ` Bill Vodall WA7NWP
2008-12-23 6:13 ` Andrew Errington
2008-12-19 20:08 Curt, WE7U
2008-12-19 20:35 ` Bill Vodall WA7NWP
2008-12-19 20:51 ` Curt, WE7U
2008-12-19 21:56 ` don_reid
2008-12-19 22:01 ` Curt, WE7U
2008-12-19 22:58 ` Andrew Errington
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=1231085403.6565.0.camel@rosi \
--to=oe8bck@gmx.net \
--cc=linux-hams@vger.kernel.org \
/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