From: Michael Jones <mjones@linear.com>
To: Ilija Kocho <ilijak@siva.com.mk>
Cc: Lukas Riezler <lukas.riezler@gmx.net>, ecos-discuss@sourceware.org
Subject: Re: [ECOS] RedBoot necessary for porting ecos?
Date: Fri, 11 Jan 2013 15:25:00 -0000 [thread overview]
Message-ID: <4E5FDD54-4DE8-4B81-9BB2-4D92D36FCBD5@linear.com> (raw)
In-Reply-To: <50EFC56F.4040506@siva.com.mk>
Lukas,
Ilija is correct, I was in a hurry and did not see the word "port" in your request. Therefore, my recommendations assumed your platform was supported.
Mike
On Jan 11, 2013, at 12:55 AM, Ilija Kocho <ilijak@siva.com.mk> wrote:
> Hello Lukas
>
> Actually RedBoot works on top of eCos so before eCos is ported you can't
> run RedBoot.
>
> 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.
>
> In most cases, all you need to make in order get first eCos "Hello
> World!" on serial line are:
> 1. Clocking
> 2. Diagnostic (HAL) serial support.
>
> Once you have reached this point, you can start with device drivers
> (serial, Ethernet, etc).
>
> Regarding peripheral drivers: Before you start coding, do some research
> through eCos source tree, it is possible that your chip has some
> peripherals that are already supported for other architectures, then you
> can probably use the same drivers (with or without some tweaks). Usually
> the manufacturers combine same peripherals with different architectures.
> For instance LPC17xx uses drivers from LPC2xxx.
>
> Have fun!
> Ilija
>
> On 11.01.2013 01:55, Lukas Riezler wrote:
>> Hello everyone!
>>
>> First I have to say, that I'm quite new in microcontroller theme (and my english is not so good).
>> But I'm interested to get ecos run on my IAR-EvalBoard with CortexM3 (FM3).
>> I've read a lot of stuff but though I have some elementary questions:
>>
>> - is it a requirement to work with RedBoot or is it also possible to port ecos without using RedBoot?
>> - I know that RedBoot is based on the ecos-HAL. Does it mean, if I port RedBoot to my target, that I can use later the same HAL-Code for ecos?
>>
>> With kind regards,
>> Lukas R.
>>
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2013-01-11 15:25 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 [this message]
[not found] ` <CAM0fDaeUunmB91FGSVA9XXp4PEYTjs7m48fikrmXsv3YngvW0A@mail.gmail.com>
2013-01-14 21:13 ` Ilija Kocho
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=4E5FDD54-4DE8-4B81-9BB2-4D92D36FCBD5@linear.com \
--to=mjones@linear.com \
--cc=ecos-discuss@sourceware.org \
--cc=ilijak@siva.com.mk \
--cc=lukas.riezler@gmx.net \
/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).