[ECOS] Replacing VxWorks with ECOS

[ECOS] Replacing VxWorks with ECOS

[brad chisholm]

Hi there,

I am currently investigating the possibility of replacing VxWorks with
ECOS in an existing product that has been released to customers.

I am trying to get a feel for the length of time the change will take,
can anyone give practical advice on the length of time it has taken them
to get ECOS running on a target platform and then to replace an
existing RTOS with ECOS.

- We use a predominantly posix interface into the RTOS.
- For a guide to system complexity, we run approximately 50 threads
concurrently, use semophores, mutexes and signals. There are hard
real-time deadlines and we use 3rd party stacks.

There is a BSP for the processor we use in our product.

Thank you for any information
Regards
Brad

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

Re: [ECOS] Replacing VxWorks with ECOS

[Mike Arthur]

Brad,

Just like the answer you got on the RTEMS mail list, it should be
relatively straight forward because of your usage of POSIX.  Do you
have an eCos BSP for the processor or for your development board?

To give you a data point: it took 2 days to convert a VxWorks CAN
driver library to a functioning library in eCos.  To get the code,
CDL, and header written to fit the eCos CAN driver paradigm took about
a week and half.  The major effort was learning the eCos CAN driver
paradigm.  The finished driver is 2k lines including comments,
defines, and code.

Mike




On 5/11/07, brad chisholm <brad.chisholm@step01.co.uk> wrote:
> Hi there,
>
> I am currently investigating the possibility of replacing VxWorks with
> ECOS in an existing product that has been released to customers.
>
> I am trying to get a feel for the length of time the change will take,
> can anyone give practical advice on the length of time it has taken them
> to get ECOS running on a target platform and then to replace an
> existing RTOS with ECOS.
>
> - We use a predominantly posix interface into the RTOS.
> - For a guide to system complexity, we run approximately 50 threads
> concurrently, use semophores, mutexes and signals. There are hard
> real-time deadlines and we use 3rd party stacks.
>
> There is a BSP for the processor we use in our product.
>
> Thank you for any information
> Regards
> Brad
>
> --
> 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