This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ecos usage question


On 2008-08-30, Dave Milter <davemilter@gmail.com> wrote:

> As I understand I build ecos as library and then link it to my code,
> move it to bootable storage and my device is ready to run,

Correct.

> but 1)what about reflashing, I mean updating software in
> device, what preferred way? At now I see only one way:
> building also redboot, and first of all boot it, then it boot
> my software or reflash my software or reflash itself,

Exactly.

> but I actually will have on flash two ecos libraries, one
> linking with my software and another linking with redboot.

Correct.  Keep in mind that RedBoot uses very, very little of
what's in the eCos library.  Bascially it uses the flash
routines, the Ethernet driver, and some initialization and
serial I/O routines.

> 2)What about FPU? I see in code C implementation of math.h
> functions, what about if want use assembler variants which gcc
> produce?

Dunno.  None of my eCos projects use floating point.

> 3)related to (2), I doubt that gcc which recommended as
> default toolchain for arm support FPU that I will use
> (VFP9-S), can I use more recent versions of gcc, like 4.1 to
> build ecos?


-- 


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]