From: Ilija Kocho <ilijak@siva.com.mk>
To: Lukas Riezler <lukas.riezler@googlemail.com>
Cc: ecos discuss <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] RedBoot necessary for porting ecos?
Date: Mon, 14 Jan 2013 21:13:00 -0000 [thread overview]
Message-ID: <50F474DA.1080309@siva.com.mk> (raw)
In-Reply-To: <CAM0fDaeUunmB91FGSVA9XXp4PEYTjs7m48fikrmXsv3YngvW0A@mail.gmail.com>
Lukas
On 13.01.2013 18:21, Lukas Riezler wrote:
> Hi Michael & Ilja!
>
> Thank you very much for your answers!
>
> So, if I'm right now, I need to port ecos before RedBoot is able to
> run...and I don't really need RedBoot for my intention. (?)
> Is there any suggestion which existing ecos-port for Cortex-M I should
> take to be my template?
Instead of suggesting I'll try to list specifics of existing ports, I
hope it will help you pick one that's closest to your system.
- STM32 is the initial Cortex-M port and probably was used as model for
others, contains wide span of memory configurations and probably most
complete driver set, including USB but lacks Ethernet (which you can
finf in Bugzilla), You already noticed STM32 support for external
interrupts.
- LM3S is nice example for a tiny system with very little memory.
- Kinetis, A2FXXX and LPC17XX have Ethernet.
- LPC 17xx is example for reusing drivers from other architecture (ARM
and Cortex-M are considered separate architectures in eCos)
- Kinetis and A2FXXX feature Consolidated Interrupt Priority Scheme,
- Kinetis features wide range of memory models including single chip and
systems with external memory. Single-chip memory models are generically
supported on variant level.
> > Porting eCos to Cortex-M is relatively straight-forward (compared to
> > other architectures) because some essential components are
> > implemented/defined on architectural level: interrupt controller,
> > systick, and general memory map.
>
> If I take a look in the existing port for stm32, there is a also
> interrupt handling header-file in the variant-layer. But these are
> onley special interrupts for the peripherals - did I understand right?
Yes.
> Sorry for my "simple" questions - but I need to get basic knowledge
> and a solid overview :-)
>
>
I take it that you have read eCos docs. Additional information regarding
porting you shall find in Massa's book.
http://www.informit.com/content/images/0130354732/downloads/0130354732.pdf
HTH
Ilija
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2013-01-14 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 0:55 Lukas Riezler
2013-01-11 4:33 ` Michael Jones
2013-01-11 8:37 ` Ilija Kocho
2013-01-11 7:55 ` Ilija Kocho
2013-01-11 15:25 ` Michael Jones
[not found] ` <CAM0fDaeUunmB91FGSVA9XXp4PEYTjs7m48fikrmXsv3YngvW0A@mail.gmail.com>
2013-01-14 21:13 ` Ilija Kocho [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=50F474DA.1080309@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-discuss@sourceware.org \
--cc=lukas.riezler@googlemail.com \
/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).