VxWorks vs Windows CE
wmta...@my-deja.com
Windows CE, especially on the stability and reliablity?
The system requirements are Ethernet support, embedded browser support,
GUI support.
I can't think too much positive of Windows CE, except there have lots
of Winodws programmers (not too many WindRiver developers). Besides
that VxWork has: small footprint, cheap (license), stable (?), no
memory leakage (?), etc.
Your advice is really appreciated.
W.T.
Sent via Deja.com http://www.deja.com/
Before you buy.
Mike Albaugh
: Does anyone know what's the positive and negative when using VxWorks vs
: Windows CE, especially on the stability and reliablity?
: The system requirements are Ethernet support, embedded browser support,
: GUI support.
: I can't think too much positive of Windows CE, except there have lots
: of Winodws programmers (not too many WindRiver developers).
This may or may not be an "advantage". I have many times had
to clean up the mess resulting from managment using "desktop trained"
programmers for embedded/reliable systems. It is not a pretty sight. :-)
That is to say, if a programmer knows _only_ Windows, and
_refuses_ to learn anything else, that programmer is a poor choice
for embedded (or any high-reliability) programming. If said programmer
knows (or is willing to learn) other APIs and methodologies, then
the issue is almost moot. IMHO, AFAICT, YMMV, IIRC :-)
Mike
| alb...@agames.com, speaking only for myself
Michael Carstens-Behrens
WinCE compared to VxWorks
WinCE has
- no deterministic real time behaviour
- OS calls are not fully documented
- sophisticated architecture
- large footprint, requires more system ressources
- is slower
but VxWorks has
- very expensive tools
- GUI consist of several packages, which have to be licensed additionally
(UGL, it's similar to DDI, Zinc, ...)
Regards, Mike...
wmta...@my-deja.com wrote:
> Does anyone know what's the positive and negative when using VxWorks vs
> Windows CE, especially on the stability and reliablity?
> The system requirements are Ethernet support, embedded browser support,
> GUI support.
> I can't think too much positive of Windows CE, except there have lots
> of Winodws programmers (not too many WindRiver developers). Besides
> that VxWork has: small footprint, cheap (license), stable (?), no
> memory leakage (?), etc.
> Your advice is really appreciated.
>
> W.T.
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
--
----------------------------------------------------------------------
Michael Carstens-Behrens NEC Electronics (Europe) GmbH
Voice/Tel.: +49 211 6503-861, Fax -533 Technical Product Support
EMail : Carstens...@ee.nec.de Oberrather Strasse 4
/* PGP key available on request */ D-40472 Duesseldorf
david lindauer
it. The big factor is the up-front costs; wind river stuff is very
expensive and then like you say training for your engineers is expensive as
well.
The downside to CE is it's a microsoft product, and not very
reliable... I expect the wind river stuff to be highly reliable in
comparison. Also when we were looking into it we isolated some things you
just cannot do with it that we needed to do (don't know what, I wasn't
heavily involved in that).
In the long run an investment in wind river might actually come out
cheaper as you deal with all the issues surrounding CE. Plus wind river
has a *very* good development setup compared to what you are going to find
for CE and that may well increase productivity.
To decrease the up-front costs of wind-river, we chose two
microprocessors that we are going to use on future products and bought the
package for them.
David
Rosimildo DaSilva
>reliable...
Believe it or not, this seems to me the major asset that Win CE has...
Rosimildo.
Hugh Johnson
of your product):
Per Chip License fees:
VxWorks from about $0.50/ea to $1.00 ech (in qty)
WinCE Approx $38.00/ea
how much do you think it is worth in quantities?
My 2 cents
Hugh
In article <38343540...@notifier-is.net>, david lindauer
<dlin...@notifier-is.net> wrote:
> We're only now getting wind river so I don't have much to say about
>it. The big factor is the up-front costs; wind river stuff is very
>expensive and then like you say training for your engineers is expensive as
>well.
> The downside to CE is it's a microsoft product, and not very
Ernesto Guevara
Development system, full
VxWorks $20,000 USD
WinCE $ 1,000 USD
My 2 pesos
Ernesto
Hugh Johnson <HJoh...@ZoneAutomation.Com> wrote in message
news:s3bla5...@corp.supernews.com...
William Tang
first year, you'll get it paid back by using VxWorks.
Ernesto Guevara <ern...@ANTISPAMrdx.com> wrote in message
news:RapZ3.615$7K5....@cmnws01.we.mediaone.net...
david lindauer
Ernesto Guevara wrote:
> How does *this* sound
>
> Development system, full
> VxWorks $20,000 USD
> WinCE $ 1,000 USD
>
> My 2 pesos
> Ernesto
>
actually VxWorks costs a lot more by the time you pump in seat licenses,
internet connectivity, support for multiple processors, training, support,
etc...
David
Gene S. Berkowitz
news:s3bla5...@corp.supernews.com...
> How does this sound: (if you are going to produce more than just a few
> copies
> of your product):
>
> Per Chip License fees:
> VxWorks from about $0.50/ea to $1.00 ech (in qty)
>
> WinCE Approx $38.00/ea
>
> how much do you think it is worth in quantities?
Actually, VxWorks royalties don't approach $1.00 until you are
talking one million plus quantities.
--Gene
Casey Lang
ge...@ma.ultranet.com says...
In fact, the list price for the run time license
for 100 units is around $42,000 + $186 per unit after
that. This doesn't include the tools or the $13,500
OEM license to use them. The run time license cost per
unit drops as the quantity goes up, but that $1.00 figure
is for a LOT of units, not just a 'few' copies.
--
Casey Lang
Gary Drummond
Wow, now I know why so many requests for Linux variants have been
bounced around on this group... Maybe we could create a GNU one?
Gary
Gene S. Berkowitz
says...
> Casey Lang wrote:
>
>
> > In fact, the list price for the run time license
> > for 100 units is around $42,000 + $186 per unit after
> > that. This doesn't include the tools or the $13,500
> > OEM license to use them. The run time license cost per
> > unit drops as the quantity goes up, but that $1.00 figure
> > is for a LOT of units, not just a 'few' copies.
> >
> > --
> > Casey Lang
>
> Wow, now I know why so many requests for Linux variants have been
> bounced around on this group... Maybe we could create a GNU one?
>
> Gary
That's why Cygnus developed eCos ('e'mbedded 'C'ygnus 'o'perating
's'ystem, an open-source RTOS, and one of the reasons that Cygnus
is being bought by Red Hat...
--Gene
Rosimildo DaSilva
>>
>> Wow, now I know why so many requests for Linux variants have been
>> bounced around on this group... Maybe we could create a GNU one?
>>
>> Gary
>
>That's why Cygnus developed eCos ('e'mbedded 'C'ygnus 'o'perating
>'s'ystem, an open-source RTOS, and one of the reasons that Cygnus
>is being bought by Red Hat...
>
RTEMS is a very good RTOS. It is free.
Rosimildo.