[ECOS] RedBoot necessary for porting ecos?

Ilija Kocho ilijak@siva.com.mk
Fri Jan 11 07:55:00 GMT 2013


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



More information about the Ecos-discuss mailing list