Re: [ECOS] Load arbitrary code on iPaq using RedBoot?

[Jon Read <jon at epoczone dot com>]

Gary,

Thanks for the prompt reply.

> We do this all the time :-)
That sounds encouraging. :-)

> First of all, use "go", not "exec" since the "exec" command is
> highly tailored to running Linux and does some "special" stuff.

Ok, I'll try that - although I would prefer to have the MMU disabled etc.

> Secondly, if you don't use eCos as your base, you'll have to do
> _everything_ [in general], which includes writing all of your
> own device drivers, interrupt/exception handlers, etc.
Yep, that's fine.

> Why don't you want to use eCos to help out?
To cut a long story short, I'm developing an embedded application that 
will take control of a machine during the boot process, before the OS 
(nucleus, uITRON, eCos, whatever) has had a look in.  It will a) display 
a progress indicator on screen, and b) write to flash.

As the iPaq isn't the intended final target, obviously the drivers will 
have to be re-written at a later date.

We don't have the development boards yet, so I'd like to make a start 
using what we do have, which, apart from a few assabet/lubbock type 
boards that are already being used, is basically an iPaq. :-)

Cheers,
Jon


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