This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: How to separate the embedded binary in 2 binaries to separate driver source and application source
- From: Grant Edwards <grante at visi dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: Mon, 17 Nov 2008 15:18:28 +0000 (UTC)
- Subject: [ECOS] Re: How to separate the embedded binary in 2 binaries to separate driver source and application source
- References: <3fae21000811170616j51c9652bk104623e9a9cfab9e@mail.gmail.com>
On 2008-11-17, Emmanuel Coullien <coullien.emmanuel@gmail.com> wrote:
> 1) How is possible to get two binary with the eCos development
> tools (For example is it possible to use REGIONs to tell
> the application where are flash or I2C drivers) ?
Link the two binaries separately.
> 2) Is someone have ever done a such"driver binary"
Yes -- though not in eCos.
> or have ever separate the binary in two way in the eCos
> development process and call functions from the application
> which are in an other binary ?
Sure. That's how it currently works when applications make
calls into routines that are in RedBoot (and vice versa).
--
Grant Edwards grante Yow! I'm totally DESPONDENT
at over the LIBYAN situation
visi.com and the price of CHICKEN
...
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss