Porting Rtems code( TCP/IP) stack on proprietary RTOs

[Mahesh Revuri]

Hi,
     I took the RTEMS path when facing the same situation of yours. Joel's
answer should suffice.

Regards,
Mahesh

Joel Sherrill wrote:

> Vinod Singh wrote:
> >
> > Hi,
> >
> > We  have to do Rtems code porting to some proprietary Real Time
> > Operating system.
>
> If it is an in-house RTOS, then I encourage you to consider letting
> OAR add support for your API to RTEMS itself.  RTEMS is structured
> around a SuperCore that makes it possible to support a variety of
> tasking APIs.  That is how the Classic/RTEID/pSOS+, POSIX, and
> ITRON APIs all co-exist.
>
> In the long-run, this is a better option.  You will get a long
> more bang for your buck this way.
>
> > The following options are used for configuration
> > rtems-4.5.0 code:
> >
> > "../rtems-4.5.0/configure  --target=i386-rtems --prefix=/usr/local
> > --enable-cxx --enable-gmake-print-directory --disable-tests
> > --disable-posix --enable-networking --enable-bare-cpu-cflags=pentium
> > --enable-bare-cpu-model=pentium --enable-rtemsbsp=bare "
> >
> > The required target is not supported on rtems so we have chosen i386.
> > The bsp is bare and cpu model is pentium. My queries are :
> >
> > 1. Is there any method to configure for no-cpu target? When we have
> > tried to do that it takes by default host target on which it is running.
> >
> > 2. How to segregate target specific stuff from the code ? Any pointer in
> > this direction will be highly appreciated.
> >
> > regards
> > Vinod
>
> --
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel at OARcorp.com                 On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>    Support Available             (256) 722-9985