From: wireless <wireless@tampabay.rr.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] OT: HiTech-C question
Date: Mon, 15 Nov 2010 09:25:31 -0500 [thread overview]
Message-ID: <4CE142DB.5060001@tampabay.rr.com> (raw)
In-Reply-To: <20101115073713.475b4adf@osage.osagesoftware.com>
Previously you wrote:
> Checking on IAR's website, they support some PIC processors, but not
> the PIC16 processor currently involved.
Deal with a salesman via email on IAR offerings. Often they
have versions not found published. IAR has an outstanding
(few) compiler developers. Best in the micro world, imho.
Ask who they'd use for your specific part/problem, if they
do not offer a suitable version for your specific (part) chip.
> James, I'd appreciate your posting your PIC open source references.
These are old and unfiltered from a long time:
from bookmarks file:
5382. http://www.embedded.com/190302110
5383. http://www.state-machine.com/
5384. http://www.circuitcellar.com/library/toc.asp
5385. http://www.ethernut.de/en/index.html
5386. http://www.sics.se/~adam/uip/index.php/Main_Page
5387. http://www.sics.se/~adam/uip/download.html
5388. http://www.edtp.com/
5389. http://liquorice.sourceforge.net/
5390. http://www-ccs.cs.umass.edu/~shri/iPicTech.html
5391. http://savannah.nongnu.org/projects/lwip/
5393.
http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1824&appnote=en011993
5394. http://forum.microchip.com/tm.asp?m=54189
5395. http://www.sics.se/~adam/uip/
5398. http://picnic.sourceforge.net/
5399. http://picnic.sourceforge.net/v2/wiki/
5400. http://pikdev.free.fr/
5401. http://piklab.sourceforge.net/
5402. http://hyvatti.iki.fi/~jaakko/pic/picprog.html
5403. http://home.pacbell.net/theposts/picmicro/
5404. http://picfloat.sourceforge.net/
5405.
http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010029&part=DM163004
5406.
http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1469&filter1=function
5407. http://www.beyondlogic.org/
5408. http://www.gnupic.org/
5409. http://huizen.dds.nl/~gnupic/
5410. http://groups.google.com/group/pickit-devel/
5411. http://mdubuc.freeshell.org/Jolt/
5412. http://www.oopic.com/
5413. http://www.yty.net/pic/
5414. http://www.piclist.com/techref/microchip/tcpip.htm
5415. http://www.piclist.com/techref/microchip/routines.htm
5416. http://pikdev.free.fr/
5417. http://piklab.sourceforge.net/
5418. http://www.chebucto.ns.ca/~rakerman/port-table.html#IANA
5419. http://www.piclist.com/techref/piclist/index.htm
5424. http://www.mypic32.com/web/guest/contestants
> Again, thank you all for sharing your knowledge and expertise.
Drop me some email off-line, as I'd be interested in
collaboration on PICs via wine/gentoo workstation
development. I'm BUSY right now, but in a few weeks, I'll be
finishing an old PIC(18F8720) project from 4 years ago
(customer has funding YIPEE!!!!!!!!!!!!)
James
prev parent reply other threads:[~2010-11-15 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 2:10 [gentoo-embedded] OT: HiTech-C question David Relson
2010-11-15 3:37 ` Peter Stuge
2010-11-15 7:44 ` Mike Frysinger
2010-11-15 11:22 ` wireless
2010-11-15 12:25 ` Arkadi Shishlov
2010-11-15 14:45 ` wireless
2010-11-15 16:05 ` Peter Stuge
2010-11-15 18:13 ` wireless
2010-11-15 18:53 ` Peter Stuge
2010-11-15 19:28 ` Arkadi Shishlov
2010-11-15 14:53 ` Peter Stuge
2010-11-15 12:37 ` David Relson
2010-11-15 14:25 ` wireless [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=4CE142DB.5060001@tampabay.rr.com \
--to=wireless@tampabay.rr.com \
--cc=gentoo-embedded@lists.gentoo.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