From: Michael Jones <mjones@linear.com>
To: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] How to get eCos up on Kinetis
Date: Wed, 02 Jan 2013 01:15:00 -0000 [thread overview]
Message-ID: <9ECFA388-1BB0-4B8B-994A-926B4268C783@linear.com> (raw)
I finally succeeded getting eCos up on my Tower K60 Kinetis Board with a complete tool chain. I just posted all the details on my blog for the next newbie that tries this.
The post covers:
- Why I picked eCos as an alternative to MQX
- Some linux pitfalls for the MQX user migrating to linux and a few issues with Parallels VM and linux
- How to install gnutools and how to compile eCos from CVS
- How to get around a 64 bit gnu compiler problem
- Why I gave up on Redboot
- Differences between MQX OSBDM and OpenOCD/JTAG
- How to setup OpenOCD with a JTagKey (adapter, drivers, config files, compiling)
- How to setup Eclipse to compile and debug
- How to setup eCos for printf on a terminal using a USB to RS232 adapter and Tower serial board
I am sure a few details got missed, and I probably hacked in a few places where a better solution exists. But at least if you are an MQX user with little linux experience, and you have a Tower board, you can probably setup everything with less trouble. Existing experts will not learn much from this post other than what starting from square one is like, not knowing about things like OpenOCD or Eclipse.
John Dallaway and Ilija Kocho, thanks for all the help getting unstuck a few times and for your patience.
You can find the post at:
http://www.eeweb.com/blog/mike_jones/getting-ecos-running-on-freescale-tower
Mike
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2013-01-02 1:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9ECFA388-1BB0-4B8B-994A-926B4268C783@linear.com \
--to=mjones@linear.com \
--cc=ecos-discuss@ecos.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).