public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: "C. Adam Lamb" <alamb@ilxlightwave.com>
To: <ecos-devel@sourceware.org>
Subject: Intention to Port eCos to STR9
Date: Wed, 14 Jun 2006 20:17:00 -0000	[thread overview]
Message-ID: <00c001c68fef$94598bd0$63000a0a@corp.ilxlightwave.com> (raw)

Hi Gang,

I’m currently looking into porting eCos to the STR912 processor.  The
processor is on the bleeding edge (it just came out), so I’m still waiting
for my eval board.

My first goal in this message is to both let everyone know that I should be
starting to work on this soon and see if anyone else might be working on
this as well…

Second goal is to have someone with some eCos experience make sure my
porting approach isn’t too far off.  I’m definitely new to eCos, so any
pointers will be awesome (I have been reading some of the other “How do I
port to X” threads).  The STR9 is using an ARM966-E/S core, so my intention
is to start with the eCos port that is for that core and adapt it to the
STR9.  I will be using the all of the GNU tools for building and debugging. 
I intend to purchase either Signum System’s JTAG Jet with Trace or the PEEDI
JTAG Emulator if I can’t get my company to pony up for the slightly more
expensive device from Signum.  Both of those devices claim to be compatible
with the GNU debuggers.  Anyone with experience with either of those
devices?  Other suggestions?

By the time I am finished with the port (the complete port might take 6
months or more depending on my employers priorities), I hope to have drivers
for USB, Ethernet, Flash, SPI, …, and possibly GPIB.  I’m not sure my
employer will allow me to contribute the GPIB portion, but we’ll see…  I
intend to contribute everything else back that I can.

Should be fun getting to know you all!  I hope to be more of a help than a
hindrance in this forum when it’s all said and done.  Forgive me while I
spin up!

Thanks!

Adam Lamb
Sr. Firmware Engineer
ILX Lightwave Corp
Bozeman, MT

             reply	other threads:[~2006-06-14 20:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 20:17 C. Adam Lamb [this message]
2006-06-14 21:09 ` Andrew Lunn
2006-06-14 21:15   ` Re[2]: " Evgeny Belyanco
2006-06-14 21:33     ` Andrew Lunn
2006-06-15  8:54   ` Ilija Koco
2006-06-15 14:55     ` C. Adam Lamb
2006-06-15 15:12       ` Andrew Lunn
2006-06-15 21:56         ` Joakim Langlet
2006-06-15 22:11           ` C. Adam Lamb
2006-08-28 10:29           ` fabio
2008-07-28  6:48             ` Mohd_Arif
2006-06-16  9:44       ` Ilija Koco
2006-06-16 14:47         ` Porting " C. Adam Lamb
2006-06-17  9:47           ` Ilija Koco
2006-06-17  9:59             ` Ilija Koco
2006-08-27 15:51 ` Intention to Port " Evgeny Belyanco

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='00c001c68fef$94598bd0$63000a0a@corp.ilxlightwave.com' \
    --to=alamb@ilxlightwave.com \
    --cc=ecos-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).