Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Operating Systems Software Linux

Embedded Linux Tools Market a Myth? 290

nadamsieee writes "EETimes is running a story that proclaims that the embedded Linux tools market is a myth The author, Dan O'Dowd, sites variety of problems (challenges?) with embedded Linux ranging from poor real-time performance to lack of broad developer support. Dan concludes: "Considering all of the possible support avenues, Linux support ends up being lower quality and more costly than the alternatives of using a homegrown operating system or purchasing a proprietary one." Maybe Dan should check out the success stories at LinuxDevices.com or perhaps try a more traditional embedded OS that also happens to be Free."
This discussion has been archived. No new comments can be posted.

Embedded Linux Tools Market a Myth?

Comments Filter:
  • by gotem ( 678274 ) on Thursday January 15, 2004 @01:49PM (#7988316) Homepage Journal
    Linux support ends up being lower quality and more costly than the alternatives of using a homegrown operating system
    why is a support from an open source OS diferent from a home grown one?
    • by Anonymous Coward on Thursday January 15, 2004 @01:52PM (#7988368)
      Dan O'Dowd is President and chief executive officer of Green Hills
      Software,Inc.
      Green Hills sells compilers and RTOS for embedded
      systems. (They have been the market for a long time).
      No wonder he does not like Linux.
      • Being a competitor does not make him automatically wrong. In fact, one might say that he's an expert on the matter.
        • ... with a clear conflict of interest, as well as a biased point of view. Even if what he says makes sense, selective presentation of facts can be used to support any conclusion.
        • He might not be wrong per se. However his articles, opinions, and thoughts will be BIASED. This is especially true if he is indeed an executive. A HUGE chunk of compensation executives are tied to company performance (whereas an engineer's is based more on personal performance or product design or whatever). Therefore, it is reasonable to expect this person to be biased AGAINST his competition. Whatever an executive says is pretty much straight out of company PR. In fact, many executive commentary is run th
    • Because, assuming basic competency, if you write it from scratch, it does _exactly_ what you want it to do, it's developed just the way you want it, and with the documentation that you want and need.

      With Open Source, you can easily end up spending more time modifying it to your specific needs than it takes to write it from scratch, especially if the source you're looking at is using a method for doing things that is not suitable for your problems. Especially since lack of or inferior documentation is all t
      • Basically, what Slashdot is saying with this article summary is that articles that are pro-Linux are good and truthful, and articles that aren't pro-Linux and point things out are misguided and false and simply must be uneducated.

        And people accuse Microsoft of bias.
      • Before I reply, I should disclose that I'm a minor stockholder in an embedded Linux company, so my opinion may be biased. There, now that that's out of the way....

        Most embedded Linux developers do just that: they write their own system on top of a Linux kernel. The value-add from embedded Linux companies is having people with more Linux kernel experience porting Linux to your custom hardware.

        The article's author shows a lack of understanding of the future of embedded systems. In the past, he would ha

        • I was thinking the same thing. For things like set-top boxes, etc, embedded Linux or Windows or whatever should be suitable. I think the author's points are only valid for mission-critical real-time systems (like some you mentioned, along with medical devices, trains, etc).

          Sivaram Velauthapillai
  • by j0keralpha ( 713423 ) * on Thursday January 15, 2004 @01:50PM (#7988351)
    The article is IMHO unnecessarily inflammatory, but the author highlights a problem not only for the embedded linux market but for the entire linux market. The lack of support for what are admittedly GOOD products is gnawing, and makes the enterprise usefulness of some of them fairly limited. You and I might be able to figure stuff out on our own, but Joe CEO wants everything he uses to be backed 24/7/365 by the company making it. And you know what? Hes right.
    • by lurvdrum ( 456070 ) on Thursday January 15, 2004 @01:54PM (#7988406)
      Then let Joe CEO take out a paid for support contract - heaven knows there are enough companies getting into the Linux support game now. With all the money he saves avoiding proprietary operating software he can certainly afford it.
      • I'm not sure if the "give it away and make money on service" model will really work for small development companies. While being able to charge for support would be nice, most small companies don't have the people to handle it.

        I've also seen what happens to a company that suddenly changes its income model from selling software to supporting some very large clients, and it's not always pretty. ("Why yes, we'll uproot an entire development team and have them live out of a suitcase onsite for a couple months-

      • by EmbeddedJanitor ( 597831 ) on Thursday January 15, 2004 @02:25PM (#7988815)
        I'm sure a Linux support contract would be lower cost than an Microsoft one or Sun, IBM,....

        The biggest problem is that people get it into there minds that Linux==free, therefore they feel they're getting cheated when they spend any money on Linux-based services and software.

    • You and I might be able to figure stuff out on our own, but Joe CEO wants everything he uses to be backed 24/7/365 by the company making it.

      Yeah. That's why Joe CEO calls up Red Hat and buys Enterprise Linux and a 2 year support contract. Support is out there for those willing to pay for it...
    • You and I might be able to figure stuff out on our own, but Joe CEO wants everything he uses to be backed 24/7/365 by the company making it. And you know what? Hes right.

      If Joe CEO want's this kind of support for anything then they had better be prepared to pay for it. As for this support comming from the company who made the widget this isn't usually a condition with anything else so why should it be with software. Anyway when it comes to proprietary software all you know is who supplied it to you. Did t
    • The lack of support for what are admittedly GOOD products is gnawing, and makes the enterprise usefulness of some of them fairly limited. You and I might be able to figure stuff out on our own, but Joe CEO wants everything he uses to be backed 24/7/365 by the company making it. And you know what? Hes right.

      You know, having 24/7 support doesn't always mean much. Here at work we use Rational tools (now owned by IBM). Sure, we have a big honking support contract, but you know what happens when I call them

      • Everything I say is my OPINION... that goes without saying I guess... :)

        I find it interesting that the PHB thinks that Microsoft stands behind their product, but knows better than to actually call up Microsoft as an end user and try to get help.

        It's more of a BUSINESS decision than a technical one. The reason management does that is to mitigate risks. That is to say, shift the blame onto someone else. As the saying goes "No one ever got fired for buying from IBM" (I hope I'm getting the quote right)
    • ... the author highlights a problem not only for the embedded linux market but for the entire linux market.

      DYT?

      This isn't just a problem with Linux, it's a problem with the all platforms.

      Bad support? Poor/buggy software? High prices and low quality?
      I've heard that about everything.

      Of course, not everyone says that, but the ones that don't are trying to sell you something.

      -- this is not a .sig

    • but Joe CEO wants everything he uses to be backed 24/7/365 by the company making it. And you know what? Hes right.

      And where does he get that now? Certainly not from MS, IBM, CA, or any other vendors we deal with. We have to PAY for support like that. You can get 24/7/365 OSS support for less money if you're willing to pay for it. I don't know any CEO's with the mistaken impression that if they buy proprietary software there's going to be a company standing by to assist 24/7/365 and they're even starti

  • by BoldAC ( 735721 ) on Thursday January 15, 2004 @01:52PM (#7988366)
    Founded in 1982, Green Hills Software Inc. is the technology leader for real-time operating systems and software development tools for 32- and 64-bit embedded systems. Our royalty-free INTEGRITY(R) RTOS, compilers, MULTI(R) and AdaMULTI Integrated Development Environments and Green Hills Probe(TM), offer a complete development solution that addresses both deeply embedded and maximum reliability applications.

    http://www.ghs.com/news/230325c.html

    Doesn't this guy sale his own embedded options?

    Wouldn't he push his own product over linux?

    What am I missing?

    AC
    • No kidding (Score:5, Informative)

      by JoeBuck ( 7947 ) on Thursday January 15, 2004 @02:02PM (#7988507) Homepage

      EE Times regularly gives space to marketing droids to flog their stuff, and regular readers know how to distinguish these marketing puff pieces from the very good stuff that the full-time staff writes.

      If someone at one of the embedded Linux companies asks, EE Times will probably be happy to give them equivalent space next week to answer.

    • I have to use the Green Hills compiler / debugger tools at work.

      Trust me, they SUCK.

      I could go into many examples of how the product is inferior to even a bunch of xterms running vi and gcc. From dongle/license frustration to waiting twice as long for builds than, say, gcc/make, to getting the right bit of magic scripts to work with their probe, I don't think there is one redeeming thing I can say about it.

      Of course this guy is going to disrespect gcc and Linux tools. His own product is horrible.
  • Not in asia (Score:4, Interesting)

    by Anonymous Coward on Thursday January 15, 2004 @01:52PM (#7988367)
    article [eetasia.com]
  • by Czernobog ( 588687 ) on Thursday January 15, 2004 @01:52PM (#7988378) Journal
    I had to work with Lineo Linux and a cross compiler (from a British company, the name of which I can't remember right now) on porting Apache (of all things...) on a MIPS/RISC board.
    I have to say I was fairly underwhelmed by the whole experience and the quality of linux-related knowledge and support out there.
    Mind you that was 3 years ago.

  • by PlanetX 00 ( 623339 ) on Thursday January 15, 2004 @01:52PM (#7988381)
    He is from GreenHills software look at all of their OS offerings and you know why he is saying this. Linux is eroding his bottom line.
  • Well (Score:3, Funny)

    by DAldredge ( 2353 ) <SlashdotEmail@GMail.Com> on Thursday January 15, 2004 @01:53PM (#7988390) Journal
    So let me get this straight, a person who sells a competing product says that a less expensive product is not as good as the one he makes.

    I also love there support for Native Win32 processors as you can see on this page. http://www.ghs.com/products/rtos/threadx.html

    • Re:Well (Score:2, Funny)

      by sik0fewl ( 561285 )

      Yes, it's really disappointing that they don't support the Intel architecture.

      Oh well, I guess I'll go with Linux, I know it runs on the Intel architecture.

    • Re:Well (Score:3, Insightful)

      by dasmegabyte ( 267018 )
      So let me get this straight. A person who works in the embedded market makes a comment on the embedded market and he's automatically wrong because he works in the embedded market?

      Is it at all likely that the guy has worked with Linux himself and had it turn out badly? Or that his customers have come to him with cobbed solutions based on Linux? Is it possible he wanted to support Linux, but found so little quality development in his segment that he realized he'd be doing most of the work himself, AND hav
  • Or... (Score:2, Redundant)

    by nonmaskable ( 452595 )
    ...perhaps Green Hills Software (Dan O'Dowd's company) has an axe to grind and came up with this agitprop.

    Come on editors - at least point out the conflict of interest!
  • by HotNeedleOfInquiry ( 598897 ) on Thursday January 15, 2004 @01:54PM (#7988401)
    To throw Linux at any and all embedded applications is a big mistake. Unless you need stuff like multiple TCP/IP servers and multitasking, you are better off with a smaller OS. There are millions of DOS-based controllers out there that won't be replaced with Linux anytime soon because they are cheaper than the hardware needed to support Linux. Likewise, PIC controllers can do things cheaper than DOS controllers for trivial tasks.

    There is no one-size-fits-all in the embedded controller market. Linux has it's niche, but it can't fit everywhere.

    • by Apreche ( 239272 ) on Thursday January 15, 2004 @02:10PM (#7988610) Homepage Journal
      http://tron.um.u-tokyo.ac.jp/TRON/ITRON/home-e.htm l

      Itron, the #1 operating system in the world. Untouchable in the embedded world. Linux is nice because it makes interoperability with the desktop smooth if you have the same OS on both. But in terms of quality ITRON is #1 for a reason other than marketing (which is the reason Windows is #1).
      • Is ITRON a standard or an implementation? It looks just like a standard from the web site.
      • I've heard about this TRON embedded OS and have spent some time looking over the materials you linked to on the site. My interest is piqued, but I am confused.

        Is there any implementation of this that I can download and play around with? Preferrably something that runs on x86, but some cheap dev board would do. I see the link to the ItIts project, or whatever it is called, but I can't read Japanese so it doesn't help me too much.
    • But, Linux is not one single entity...

      For the very small scale devices you mention, uClinux (microcrontroller linux) is probably more appropriate.

      uClinux is used in everything from modems to DVD players.
  • With both Windows CE [microsoft.com] for small applications and Windows XP Embedded [microsoft.com] for more demanding apps, Microsoft has been making a strong push for what's an extremely hot market. With everything getting smaller and smaller embedded OS's are going to be far more important.

    It's not free but the developer tools for embedded Windows devices are extremely similar to those normal Windows, so developers have less of a hard time migrating.

  • by Anonymous Coward
    Go to his company's web site (search google
    for Green Hills Software) and you'll see that
    they make an embedded real time OS. He's hardly
    an objective reporter. This is basically an
    ad for his company disguised as an editorial.
    Not to say that his arguments are wrong but
    take everything he says with a grain of salt.
  • by polyp2000 ( 444682 ) on Thursday January 15, 2004 @01:55PM (#7988422) Homepage Journal
    The guy that wrote the article...

    Dan O'Dowd is President and chief executive officer of Green Hills Software,Inc. (Santa Barbara, Calif.)

    Green Hills Software [ghs.com]

    Green Hills Software are a large RTOS manufacturer, so of course he is going to say that. Whether or not his statements are true or not I find it difficult to believe someone whose business relies on their own Proprietary OS.

    They also have a not dissimilar marketing bumpf on their website

    our product is so much better than everyone elses! [ghs.com]

    nick ...

    • From that page : "Microsoft Windows, MacOS, Unix, and Linux often crash, lock up, or go crazy."

      Woah, these guys would have a field day on slashdot fighting all the zealots from all the sides simultaneously.

      One thing that they do not mention in their little glorification, it's that these OS have to support thousands of devices, poorly written drivers, 3d graphic cards in conjonction with directx/opengl, run that recently released game that is really cool, and more.

      I'm pretty sure any of those systems w
      • I was reading that page, and can't help but wonder- what the hell does "go crazy" mean in context of one of those OSes? When the user fucks up, and the system doesn't work as they wanted it to because they did something wrong? They use the phrase "go crazy" a handful of times.

        Real-time, embedded OSes are a world apart from MacOS, Windows, Unix and Linux. You don't use those OSes for most RT applications, but that is good. You should use the right tool for the job.

        But even if you took Linux, Mac OS, or W
  • I know little about embedded OS's, but the article is a bit self-serving in that the author, Dan O'Dowd is president and CEO of Green Hills Software, (http://www.ghs.com) that makes "Integrity", an ...you guessed it... embedded OS.

    Take a look. http://www.ghs.com/products/safety_critical/integr ity-do-178b.html

    So while he may be right, the information is coming from the wrong person to be trustworthy.

    I think Dan needs to hire a PR flak.

  • by NineNine ( 235196 ) on Thursday January 15, 2004 @01:56PM (#7988433)
    That's great that Taco included the link to Linuxdevices.com, but I went to look, and they were mostly stupid consumer gee-whiz gadgets, or some Net tool (ie: router). What IT people don't seem to understand is that there are many, mayn industries out there that dwarf the IT industry. "Embedded" OS's can be used in all kinds of devices in all kinds of industries. I didn't see a single manufacturing tool using Linux as an embedded OS, for example. So other than the "this is neat, we're using Linux" devices, where are these real world applications?
    • This is a good point. And I don't just think in the big corporate embedded systems. How about some lowend consumer grade automated routers or cutters? I know lots of people with home woodshops who'd love that. There are lots of little markets like that where Linux could do great.

      Of course everyone wants the bigger companies, but I think if they could demo products outside of traditional geek tools they could really generate more interest for bigger companies.

    • What else would you expect to be listed at LinuxDevices.com?

      Most of the "embedded" Linux devices are the bigger, more powerful things like you mention- PDAs, routers, kiosks, etc. Linux couldn't run on a lot of the hardware in a lot of other "embedded" operations without running ELKS or uClinux. For instance- Linux plus the Qtopia GUI on my Zaurus C760 takes up a whopping 18 MB on boot- absolutely gigantic compared to the 2-4 MB of WinCE or something even less on PalmOS.

      I too would be interested in find
  • No (Score:4, Insightful)

    by glenrm ( 640773 ) on Thursday January 15, 2004 @01:57PM (#7988448) Homepage Journal
    Embedded Linux Tools Market a Myth? No. When I read that Wind Rivers was looking into Linux you knew which way things were going.
  • by linuxguy ( 98493 ) on Thursday January 15, 2004 @01:57PM (#7988449) Homepage

    I sold my iPod and bought a Rio Karma. Finally
    after 5 mp3 players I have one that I think I will
    keep for a while.

    I am not going to do a review here as there are
    plenty of good reviews of this product on the web
    that google will help you find.

    However to me this truly remarkable embedded
    device based on a free OS says a lot.
  • by torpor ( 458 ) <ibisum@@@gmail...com> on Thursday January 15, 2004 @02:01PM (#7988491) Homepage Journal
    Move along.

    I work in embedded systems in Germany, and there is -plenty- of linux going on ... lots and lots.

    Linux levels the playing field in grand new ways, even for the embedded folks, even for the snooty ones.

    Dan will eat crow.
    • Linux levels the playing field in grand new ways, even for the embedded folks, even for the snooty ones.

      The last thing companies who are doing fairly well out of proprietary software want is a level playing field. Especially if it means they have to work hard to gain and retain ("lock ins" are rather more difficult with OSS) customers.
  • by fatwreckfan ( 322865 ) on Thursday January 15, 2004 @02:01PM (#7988494)
    "For embedded use, Linux must be ported to appropriate processors and modified to work in diskless, resource constrained, and custom hardware environments. Real-time performance capabilities are also often required."


    Sweet jesus no! Not different processor architecures! Apparently this guy hasn't heard of Debian [debian.org].

    And real-time capabilities? How about the Real-time Application Interface [polimi.it]

    This guy simply sounds like he has a grudge against GNU and Linux.
    • Sweet jesus no! Not different processor architecures! Apparently this guy hasn't heard of Debian.

      The embedded market is full of wacky microprocessors made by companies you've never heard of, with wildly different clock speeds, alignments and memory and I/O interfaces. These are chosen by device makers and integrators based on their needs, and then put into things other than desktop PCs and PDAs. Your ridiculous snide remark aside, I suggest you at least Google a bit before posting. That will help you unde

      • by Svartalf ( 2997 ) on Thursday January 15, 2004 @02:54PM (#7989262) Homepage
        In actuality... Anyone considering the use of most of the RTOS choices out there are typically looking at one of the following CPUs:

        x86
        PPC
        ARM
        MIPS
        Coldfire
        DragonBall

        The goof-ball stuff usually ends up using the roll-your-own stuff and is not typically used in most contexts because you have to find silicon, find tools to begin with (since it's custom, there's no standard tools- uh, gee whiz, what do you know, you have to build tools, just like he said...), and you have to certify the operation of the damn thing.

        It's simpler and easier to use an off the shelf part from one of the usual suspects than to use something else.

        Now, having said this, you've got choices, depending on what you want to do because you've got standard tools and standard operating system choices...

        VxWorks
        QNX
        Lynx
        pSOS
        RTEMS
        eCos
        Linux

        Of the aforementioned, the licensing on the last three are very attractive and depending on what you're trying to do, you really want to use them instead of the others.

        The article from the author in question is guilty of lying by omission of key facts in the embedded systems industry. He's right about all of it. But what he doesn't tell you is that for most everything done, you're either not using an OS and using something like a PIC, Z8, or Z80 or you're using a more robust CPU with an OS and much more memory- something that Linux, RTEMS, and eCos do well with on most counts for embedded systems. IF you know what you're doing in the first place- you have do design your code for read-only conditions, etc. in the first place and most of Linux is happy fine with it. I know, I DO embedded Linux stuff. Real time? Don't need it all that often- most embedded devices just need memory and resource management, they don't need rate monotonic scheduling of tasks, etc. Real time is actually bandied about far more than is really, really needed- and worse yet, it's more defined by the box you draw around things. Throw enough CPU and memory Muscle at something and even Desktop or Server NT can be "real time" for the purposes of the definition.
  • The author of this 'article' is the president of a company that sells embedded RTOS's and related tool - therefore, he's biased to begin with. Most likely, he sees his company's market being deeply penetrated by Linux and is trying to stop the erosion with this article.
  • by Helmholtz Coil ( 581131 ) on Thursday January 15, 2004 @02:01PM (#7988504) Journal
    Good thing I read the article, now I know to drop the last two years' worth of work and get a "real" OS!

    Sarcasm aside, while I could maybe grant that there isn't a very large market in commercial compilers for Linux in the embedded space, there is definitely a market for Linux itself in the embedded space.

    I just finished a proof of concept project in December. Now that we're moving towards a commercial system, we're looking to reduce power draw and size. Because we're using Linux, I can switch to a different SBC with a different processor and architecture without too much trouble (the compiler toolset was provided by the SBC manufacturer, basically just a cross-compiling GCC).

    My application isn't a real-time system, so I can't comment on whether Linux is applicable as a real-time OS, but on the other hand I need to be able to resolve time on the nanosecond scale, and Linux/GCC does that just fine. So despite the article I think I'll stick with what works for me.
    • Sarcasm aside, while I could maybe grant that there isn't a very large market in commercial compilers for Linux in the embedded space, there is definitely a market for Linux itself in the embedded space.

      but would you say that the linux embedded market is increasing or will increase? I don't know exactly what a lot of embedded stuff runs, but i assume a real small bare-bones OS as a controller that's not much more than a fancy 64K asm program?

      As stuff is expected to become more "intelligent", will we see
    • by barawn ( 25691 ) on Thursday January 15, 2004 @02:17PM (#7988715) Homepage
      My application isn't a real-time system, so I can't comment on whether Linux is applicable as a real-time OS, but on the other hand I need to be able to resolve time on the nanosecond scale, and Linux/GCC does that just fine. So despite the article I think I'll stick with what works for me.

      Realtime performance means fast interrupt servicing, and this is the part I don't understand: uClinux gives interrupt latencies of about 10-40 microseconds to the top half of the interrupt handler, about 50-100 microseconds to the bottom half of the interrupt handler, and about 300 microseconds from interrupt -> data read if the bottom half is putting data through the I/O and another process is reading it. That's on a 66MHz system - so it's about a thousand clock cycles or so to the top half. That's not bad. Granted, other RTOSs are better - I've also used Microware's OS-9000, and that's got an interrupt service latency in the tens of microseconds, and that's even after using system events to signal another process. So that's really quite good. But depending on what you need, I can't see how uClinux could really hurt you that much. If you desparately need speed, try to put as much as you can in the top half, and you should get quite good performance. (Plus I think there are other ways to get the latency down, but I've never bothered, as it's never been important)

      Plus having the source is incredibly helpful. You can actually figure out what the heck is going on in certain cases without wasting days upon days trying to talk to crappy customer support for commercial RTOSes. Ugh. Maybe if the project I work with had infinite money, sure, but...
      • Realtime performance acutally means having very specific and guaranteed worst-case interrupt servicing and task scheduling that is fast as well.

        Draw a big enough box around the problem and even stock Windows can be "real time".
  • You should have seen the look on all of our faces when a well known PLC manufacturer recently showed us their new unit that has a linux mini computer in it. Every single person in the room asked when we could lay our hands on one of them as we want and need it immediately. Or wait somebody had better tell linksys that it will not work.
  • Bizarre opinion. (Score:3, Insightful)

    by Performer Guy ( 69820 ) on Thursday January 15, 2004 @02:06PM (#7988564)
    Seems downright bizzarre that anyone would suggest homegrown as a cost effective option.

    IT is full of idiots yelling at the tide though, move along, there's nothing to see here folks.
    • Seems downright bizzarre that anyone would suggest homegrown as a cost effective option.

      Depends on the particular product.

      For many types of net-connected appliances (NAS servers, routers, firewalls, webcams,..), advanced PDA/cellphones, TiVo'ish media players and similar, Linux makes a lot of sense. Most of these devices are really mini-PCs, and Linux runs well on those.

      But if we're talking washing machines, refridgerators, watches and other tiny stuff Linux is often the wrong choice because the hardwa
  • Facts? (Score:2, Insightful)

    by McLoud ( 92118 )
    The author exposes a lot of "facts" about using linux in embedded device, but doesn't open the tests made, which linux version he made the tests or with what kind of software. All the problem I've seen in software for embedded generally lies in bad written software, so what? I can make the same claims targetted at any SO/device and will this make that SO/device bad?
  • Over the last year there have been a lot of criticism in the press about linux. Now, i do understand that linux, in its infinite forms, will still never be a "be-all, end-all" perfect solution for everything. It's an OS, it's got its faults like any other.

    However, why suddenly all the criticism and negative press? I have a few theories:

    1) The SCO case introduced linux to a lot of journalists that previously had never heard of it. Kind of hard to swallow, since "linux" *is* damn near a household name n
  • He is right though (Score:5, Insightful)

    by scorp1us ( 235526 ) on Thursday January 15, 2004 @02:14PM (#7988677) Journal
    He is 100% right, provided it is 2003. The 2.6 kernel goes a LONG way in supporting the embedded segment. In 2004, average ram and flash will almost double, clock cycles will almost match that growth.

    He is right about size - Linux is too big when compared to the competition.

    What he does fail to understand is the real reasons people switch to embedded linux. Not for gains today, but gains tomorrow. EL (Embedded Linux) provides hardware abstraction, simplifies programming and opens you up to standard technologies.

    The problem with most EL projects today is that they are ports of legacy systems. One will realize much benefit int he now if the start from scratch. Backwards compatibility is the problem here.

    If you look at all the sucessfull EL prodects, 90% are new designs or use 20% or less old code. It realyl does shorted your TTM and maintance costs, if you don't bother porting old code.

    In the end EL is about the future, not the now. But we must use it now to bring about the future.

    I've worked on 2 embedded linux projects professionally, and those is my opinions.
  • by codepunk ( 167897 ) on Thursday January 15, 2004 @02:14PM (#7988678)
    For 200 points what operating system would you like
    your heart monitor to be running?

    1. Linux
    2. XP Embedded
    3. Windows CE

    Survey says.....Linux...
  • Right and wrong (Score:5, Insightful)

    by Alinraz ( 533041 ) on Thursday January 15, 2004 @02:19PM (#7988736)
    Ok, first my quals:
    * I am an embedded programmer.
    * I've used a variety of embedded OSs including both vendor (pay) and home-grown (free except for labor) and Linux.
    * I love Linux. I use it at work and home as my desktop, and at work on servers. I have contributed to several projects including ALSA and gcc and binutils.

    The way I see it, Dan is both right and wrong.

    He's right in that Linux is not approprate for many "true" embedded applications. Most apps have very stringent memmory requirements, don't need most services, and work on severly limited chips (over 70% of all processors sold are 8-bitters). Also, Linux can not meet the real-time reqirements of many applications (feel free to flame me, but it is definately true, despite any "real-time layers" that have been added to Linux). For example, I work on a product that has 512k of SRAM, with a processor clock speed of 156 MHz, and it's "clock tick" has to be less than 40 usec (typical times of Linux include 5 msec). We use an in-house "OS" which isn't a true OS anyway, just a tightly coded main loop in order to meet our requirments.

    On the otherhand, we have another "embedded" project that does use Linux. It is the best OS for the job in this case.

    As usual in engineering, one must chose the right tool for the right job.

    But, for companies that make development tools, we'd be a poor choice on that Linux system because it is highly modded and they'd not be able to support it econommically.

    What it comes down to is embedded projects MUST chose the right tools for the right job, and Linux is not allways the right tool.

    For embedded tools vendors, Linux OSs will be difficult to support for the very reasons that Dan mentions.

    But this doesn't mean that there's no place for Linux in embedded or psudo-embedded applications (psudo-embedded apps look like embedded systems on the surface, but are usually full-featured general purpose systems on the inside. Think TiVo).

    The Linux support I'd like to see from tools vendors is better tools on the Linux workstations. Support gcc and binutils for more processors or optimize the code output better on gcc. Help with gdb, insight and DDD to make your hardware emulators work with them on the workstation. I'm tired of having to keep a dual-boot system just to run VisionClick so I can debug my 5407 embedded systems.
    • Re:Right and wrong (Score:3, Informative)

      by red_gnom ( 545555 )

      Also, Linux can not meet the real-time reqirements of many applications (feel free to flame me, but it is definately true, despite any "real-time layers" that have been added to Linux). For example, I work on a product that has 512k of SRAM, with a processor clock speed of 156 MHz, and it's "clock tick" has to be less than 40 usec (typical times of Linux include 5 msec).

      Linux with RTAI on 150MHz CPU has no problem with delivering Hard Real-Time with jitter not exceeding 20 usec (It can be much less).
  • by decaf_dude ( 171976 ) <83rumx2zf001@NOSPaM.sneakemail.com> on Thursday January 15, 2004 @02:20PM (#7988742) Homepage
    From the article:

    Dan O'Dowd is President and chief executive officer of Green Hills Software,Inc. (Santa Barbara, Calif.)


    So I Googled for Green Hills Software [google.com] and found that Green Hills Software [ghs.com] is "The Leader In
    Real-Time Operating Systems". Their Products page lists several RTOS, development platforms, debuggers, compilers, etc.


    So much for disclosure at EETimes...

  • by markov_chain ( 202465 ) on Thursday January 15, 2004 @02:30PM (#7988890)
    The author points out several times that Linux, due to its general purpose design, is too inefficient/memory hungry/not real-time capable/etc. for embedded applications. However, he failed to account for the current trend of hardware becoming capable enough for those things not to matter any longer, especially in non-critical applications like Web interface for devices, home routers, media gateways, etc. The phenomenon of not coding PC software in hand-optimized assembler is spreading to high-end embedded devices.
  • The authoer has a point when it comes to "hard" real-time applications, or extremely cheap/tiny systems for throwaway-type products. There's no point adopting one of the rather tortured real-time linux adaptations, when there are plenty of solid RTOSes out there that are built from the ground up to do this job.

    Where Linux is useful is in the larger, more flexible products (handheld devices, etc.). Here you can often get away with using a more-or-less normal linux distro adapted to your processor architectu
  • This article seems to be about commercial tools for embedded linux, and how the market is soft for such software products. A few of the posters here seem to think he is putting down Linux, but rather states that, in order to make money in software tools, developers need to go somewhere else.
    From the article:

    Because most embedded Linux users roll-their-own, that leaves less than half of the market to the six-or-so major commercial distributions. Since none of them is dominant, no specific integration is ab

  • Can't Imagine (Score:3, Interesting)

    by WindBourne ( 631190 ) on Thursday January 15, 2004 @02:48PM (#7989186) Journal
    Why CEO's of competeing companies to Linux keep saying these things. They must be correct, since there are so many studies by learned people.

    LOL ROTL.
  • by tz ( 130773 ) on Thursday January 15, 2004 @02:54PM (#7989278)
    First, he seems entirely unaware of RTLinux which is a full speed RT layer that sits below Linux and has the reliable near-zero latency he calls for, and it is a commercial product (with an open source side).

    IF you need that hard real-time, it is probably the best solution. The 2.6 kernel might be "soft" real-time, but again, that means quantifying the required latency.

    For many things including lots of existing systems you need a smart peripheral or second small processor (like a UART with a FIFO).

    Much of the rest is confusion.

    First, it is easier to "roll your own" OR buy proprietary? He says that it would be to difficult to look inside the Linux kernel to figure out something (not possible with most proprietary OSes without a big $ source license), buy you can apparently recode the whole easily.

    There are places where "roll your own" fits - I typically can do most things in careful interrupt driven events, and foreground (every N milliseconds) and background loops. When you get into task switching or MM, it gets hard.

    If you are very limited, e.g. using existing hardware that doesn't have room and can't be upgraded, the proprietary uOSes are probably best. One thing to note - if he is comparing like to like, the proprietary OSes get big when you add things like network stacks and filesystems (which may not have things like journaling - can you scandisk your flash?).

    The current "small" platforms run linux fine. ARM and MIPs (think Zaurus and AMD's PDA platform) are well supported, and there is uCLinux. Here again, if you can get beyond a certain hardware threshold, you can find a lot of things available.

    His article was titled "The myth of the embeddedLinux TOOLS market". That is probably true in that most people are likely to prefer GCC to something else (or it would be nice if they took the same command line switches instead of having to redo complex compiler invocations just to use the proprietary version). And they would probably prefer to mix and match (use GNU ld and ELF or whatever the Linux target object format is).

    But what does that have to do with Linux? Or Windows CE (which isn't doing too well either and has far worse timing and resource problems).

    Support? It's there, but harder and probably not at the same level, but a Linux wizard isn't an Embedded wizard, and vice-versa and if you are already being cheap, you aren't going to pay me (who happens to know both spaces) what I'd ask any more than you would buy a support contract.

    Let me summarize my perspective (I do embedded for a living).

    1. Linux isn't a panacea, but is or can be an acceptable solution for a very wide range of embedded products. The rest fall into the custom or proprietary niches. Linux tends to get better and hardware gets cheaper. It also helps in many things having the desktop and target run the same thing.

    2. The free tools (compilers, etc.) aren't broken, so the market for "good" or better tools isn't going to be large. A tool cannot correct a design error (trying to run Linux in 64K which seems to be his example). Specialty tools have a better chance, but not "Our proprietary IDE now can compile the Linux Kernel" type tools.

    (Think filesystems - even if you had a "better" filesystem, it would have to be a lot better or have some critical feature for someone to want to pay for it instead of using one of the various systems already there).

    3. There are add-ons and products in other areas that have a market - like RT-linux which can be used as-needed. There are prototyping boards and systems that come with Linux preconfigured with most of the configuration work done. There are consulting and support services - if you want or need to pay for them, and are competetive with the proprietary OS.

    He is correct with the basis of his article - It isn't easy to sell bottled watter in the rain next to a public fountain. But his criticisms of Linux and of the development process and targets are way off. But he doesn't consider reasons for picking Linux legitimate though the engineers probably did consider things carefully.
  • Typical... (Score:5, Informative)

    by jasno ( 124830 ) on Thursday January 15, 2004 @03:18PM (#7989693) Journal
    Hello, Embedded Developer here.

    First, let me point out that the article was written by the president and CEO of Green Hills, a vendor of proprietary development tools and several RTOSes.

    Second, let me point out a mistake made by many, many analysts when talking about 'embedded' linux. The 'embedded' market ranges from 8-bit microcontroller based devices, to PC style hardware, to cell phones and set-top boxes, satellites and mars rovers. So it is very difficult to come up with an assessment of any technology that applies uniformly to the entire space.

    I've worked in practically every segment of the embedded market(DSP based consumer electronics, 8-bit control systems, headless PC's, set-top boxes, cell fones, networking appliances). I've used a variety of tools/solutions ranging from expensive and proprietary to free and open.

    I recently had a client interested in using embedded linux for a cell fone design. They were put off by the $80k price tag for vxWorks, and so they decided to try linux. They were able to squeeze the system down to around 2MB on an ARM9/TI-OMAP. The realtime performance was acceptable. And to support the development they purchased several JTAG BDM debuggers. Its not that they were looking for a free ride, but $80k for a proprietary OS with limited features didn't seem like good business sense.

    Also, the support I've received on mailing lists and IRC is above and beyond anything I've ever seen from a commercial vendor. In fact, I used to work for one of the biggest RTOS vendors around, and I found it more difficult to get answers out of my own company than the linux community.
  • Most embedded applications have real-time performance requirements. Really? I can think of very few for which "real time" is really a requirement. Certainly it is not necessary for all those routers, firewalls, access points etc. running Linux. In fact, I beleive in most cases the real time requirement results from bad design; memory is cheap, buffer up the events and process them at your leisure. Can anybody cite an application which actually requires "real time" performance that can't be addressed by inte
  • Can you say "bias"? (Score:4, Informative)

    by El ( 94934 ) on Thursday January 15, 2004 @03:23PM (#7989765)
    Dan O'Dowd is President and chief executive officer of Green Hills Software,Inc.

    Gee... don't they sell non-Linux tools? Do you think there is any possibility that the author might have some bias on the subject of embedded Linux tools?

  • Here is a Linux-powered satellite receiver appliance [intldata.ca]. I actually use these.
  • The people who make RTEMS [rtems.com], Online Applications Research Corporation [oarcorp.com] are a very cool bunch who were early adopters in the real time operating system space. They have worked very closely with RMS on licensing in the mid 90's and were one of the first groups using GCC as a cross compiler. Their business model is support oriented plus government contracts.

    (I have no financial stake in OAR or RTEMS, other than having good feelings about their involvement in OSS)
  • Yeah right (Score:3, Interesting)

    by soccerisgod ( 585710 ) on Thursday January 15, 2004 @03:37PM (#7989935)

    If it's a myth, I have to say it's a pretty profitable one. All the money I've been making last year I've been making writing mythical software for an automotive company... If only there were more myths like this - I'd be filthy rich! :)

  • by 13Echo ( 209846 ) on Thursday January 15, 2004 @03:44PM (#7990082) Homepage Journal
    This article is stupid...

    Why? Because the author has HIS OWN operating system products and services at:

    http://www.ghs.com/ [ghs.com]

    In fact, this guy claims to be the authority on operating systems... Read on to learn just why you should choose their "INTEGRITY" product over Microsoft Windows, MacOS, Unix, and Linux, etc.

    http://www.ghs.com/RTOSLeader.html [ghs.com]

    It's Andrew Tanenbaum all over again.

    Glad we have an author here that can back his article up with facts, and not just crap.
  • The complaints about the tools are a supply-side problem. The demand is there, so there's a market. But the suppliers are not meeting that demand properly (bad tools and delivery models). That means there's still a market demand there. It's the tools that are a myth; the market is real, and evolving.

Over the shoulder supervision is more a need of the manager than the programming task.

Working...