[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Replacing VxWorks with RTEMS
- Date: Tue, 08 May 2007 10:31:33 -0500
- From: joel.sherrill at oarcorp.com (Joel Sherrill)
- Subject: Replacing VxWorks with RTEMS
brad chisholm wrote:
> Hi Ali,
> This sounds good, is this 3 man months duration? We already have the
> wrappers which should save some time.
If you are mostly using POSIX, you shouldn't see a lot of problems.
In estimating the effort, be sure to know how much BSP work you will
have to do. Is there already an RTEMS BSP for your hardware?
Also VxWorks and RTEMS handle application configuratin differently.
That will have to be looked at.
> Ali Asgar Nasir wrote:
>> We have changed the RTOS in one of our application to RTEMS. It took us
>> around three months to do the same. We have implemented wrapper functions
>> around the original OS calls which we had in our legacy OS. This makes the
>> code changes in the actual application to minimum. We just then link the
>> wrapper's to the OS calls in the application and remove the legacy OS's
>> U need to be clear about the memory mapping and all hardware related stuff
>> of your target. It will make the changeover smooth.
>> -----Original Message-----
>> From: rtems-users-bounces+aliasgar.nasir=patni.com at rtems.org
>> [mailto:rtems-users-bounces+aliasgar.nasir=patni.com at rtems.org] On Behalf Of
>> brad chisholm
>> Sent: Thursday, May 03, 2007 3:56 PM
>> To: rtems-users at rtems.org
>> Subject: Replacing VxWorks with RTEMS
>> Hi there,
>> I am currently investigating the possibility of replacing VxWorks with
>> RTEMS 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 RTEMS running on a target platform and then to replace an
>> existing RTOS with RTEMS.
>> - 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.
>> Thank you for any information
>> rtems-users mailing list
>> rtems-users at rtems.com
>> World-Wide Partnerships. World-Class Solutions.
>> This e-mail message may contain proprietary, confidential or legally
>> privileged information for the sole use of the person or entity to
>> whom this message was originally addressed. Any review, e-transmission
>> dissemination or other use of or taking of any action in reliance upon
>> this information by persons or entities other than the intended
>> recipient is prohibited. If you have received this e-mail in error
>> kindly delete this e-mail from your records. If it appears that this
>> mail has been forwarded to you without proper authority, please notify
>> us immediately at netadmin at patni.com and delete this mail.
> rtems-users mailing list
> rtems-users at rtems.com