Wind River Partners With Red Hat On Embedded Linux
An anonymous reader writes "According to LinuxDevices: 'Calling embedded Linux and VxWorks 'the standards in device software development,' Wind River today announced a dual operating system strategy that adds a newly developed embedded Linux distribution -- Red Hat Embedded Linux -- alongside its proprietary VxWorks real-time operating system.'"
Here are the things that WR ships when you go to use VxWorks for your embedded system project:
Components Included
Development tools:
TORNADO Integrated Development Environment
GNU and DIAB C/C++ Compilers
WIND VIEW system analyzer
SNiFF+ PRO code visualization tool
Full VxSim
TORNADO BSP DEVELOPER'S KIT
Runtime Components:
VxWorks embedded RTOS
TrueFFS flash file system
VxFusion
VxVMI
VxMP
So, how far does Linux have to come to match these tools?
oes embedded Linux have any advantages whatsoever over say QNX or TRON?Yes, it's a heck of a lot easier to port Open Source applications to, so you don't have to write all your code from scratch. Also, it's oriented towards protected address spaces for each process, unlike vxWorks or pSOS. On the down side, most people consider it to have a larger memory footprint -- but then, memory is cheap and getting cheaper (that's what keeps Microsoft in business!)
"Freedom means freedom for everybody" -- Dick Cheney
What makes you thing WRS is throwing in the towel on the proprietary nature of VxWorks? They could take some things out of Linux that might help performance or increase capability in some areas of VxWorks. I don't think they want to use the Linux kernal as a whole. Maybe they want to see if the can have TWO OSes to sell or maybe a hybrid. I don't suspect you'll see things coming out to the Open Source from WRS whatever they do with Linux, they are quite proprietary with their software. I once tried to get source for vxWorks (customer wanted it) many years ago. I recall the asking price was 50K plus run-time fees.
If you are a solid embedded engineer who REALLY knows how things work and not just a code slinger you can make vxWorks do some very nice things for you. But you have to be careful or you kill the OS and have to start over. The BSPs are very configurable if you know how the processor actually WORKS. Using VxWorks is not a job for the average programmer, you don't just hack it out and expect it to work. I have taken almost all of the classes they offer (not in the last 5 yrs thought) and found them to be well taught and service we had at a major defense company was excelllent. I could call up the local tech guy and get good answers. Of course YMMV on tech support as we are talking people here. I don't recall seeing Linux with drivers for VME bus and MIL-STD-1553 as VxWorks has. But maybe if Linux hits the embedded market someone will do that. I've not heard of anyone with a sour impression of VxWorks. Plus they HAVE managed to stay in business, if they were as bad as you imply I think as small as the market for embedded OSes is over the last 15yrs (it's getting bigger now) they would have gone under.
As for Tornado and the Debugger, I've seen much better IDEs. The tools were often much buggier than the BSPs and the OS. Unless they have improved since the last time I used them I think they were more in the way than helpful.WRS is pretty much the leader in embedded general purpose OSes. There are others that are better for specific purposes.
Oh, and this stuff about vendors tieing you to a platform..ever seen Windows run on anything but a X86 Architecture? If it works for Redmond you can bet everyone is going to try to emulate it in their market. Software vendors are a Monkey See Monkey do bunch with Microsoft as the head monkey.
Back to lurk mode...