On Mon, 14 Apr 2008 07:51:00 +0100, Chris H wrote:> In message <IO-dnWaR0svMup_VnZ2dnUVZ_oqhnZ2d@giganews.com>, ROB > <rob701101@yahoo.com> writes >>Hi, >> I am new to any RTOS and wanted to learn more about it. Can some post >>me small & freely available RTOS with documents details & source code. >>Also let me know, if these RTOS are absolutely FREE to use for >>commercial requirement. I am looking for small(<10KB), FREE(cost 0 >>cents), popular(used readily) RTOS :-) > > > There are many free RTOS but most if not all are usually chargeable for > commercial development > > Why would you want a free rtos for a commercial development? If you are > looking to be paid for your work you should pay others who contribute to > it. > > The free RTOS that are really free (ie FOSS) will usually require that > you publish all your source code as well..Check your license agreements, I think you're confused. The ones that I looked at only require you to publish the RTOS source, and IIRC in the case of eCos that's only necessary if you modify the source rather than just using it. -- Tim Wescott Control systems and communications consulting http://www.wescottdesign.com Need to learn how to apply control theory in your embedded system? "Applied Control Theory for Embedded Systems" by Tim Wescott Elsevier/Newnes, http://www.wescottdesign.com/actfes/actfes.html
Learn RTOS
Started by ●April 13, 2008
Reply by ●April 14, 20082008-04-14
Reply by ●April 14, 20082008-04-14
"ROB" <rob701101@yahoo.com> wrote in message news:IO-dnWaR0svMup_VnZ2dnUVZ_oqhnZ2d@giganews.com...> Hi, > I am new to any RTOS and wanted to learn more about it. Can some post > me small & freely available RTOS with documents details & source code. > Also let me know, if these RTOS are absolutely FREE to use for commercial > requirement. I am looking for small(<10KB), FREE(cost 0 cents), > popular(used readily) RTOS :-) > > Thanks in advance. > >If you want to "learn" then by far the best release is Jean Labrosse's book on MicroC/OS-II. About $70 from amazon, etc. It is a detailed explanation of RTOS concepts and includes source code for a running RTOS. The latest version of the MicroC/OS-II (uCOS) code is freely available on the micrium website for non-commercial use. There are many free RTOS available as others have mentioned, but you will not beat the Labrosse book if you want to learn. Absolutely FREE and commercial seems to be an oxymoron. -- Scott Validated Software Corp.
Reply by ●April 14, 20082008-04-14
> 10kb could be just the basic kernel with the mailbox/semaphore primitives, > static memory model and hard linkage to the application code. Developing > such thing is a weekend project.I'm playing devils advocate here - quoting from "Taming Software Complexity" by Jack Gansell, Embedded Systems Engineering this month: "Of the three RTOSes I looked at (�C/OS-II, eCos, and FreeRTOS), total cyclomatic complexity (the sum of all of the individual v(G)s) is 690, 445, and 258 respectively. Note that these numbers say nothing about the comparative quality of the code as those that offer more functionality will have more functions and higher total complexity. But to those of you who think you can write an operating system in a weekend, well, it's clear that just writing the tests will consume far more time than that." -- Regards, Richard. + http://www.FreeRTOS.org & http://www.FreeRTOS.org/shop 17 official architecture ports, more than 5000 downloads per month. + http://www.SafeRTOS.com Certified by T�V as meeting the requirements for safety related systems.
Reply by ●April 15, 20082008-04-15
Op Mon, 14 Apr 2008 08:51:00 +0200 schreef Chris H <chris@phaedsys.org>:> The free RTOS that are really free (ie FOSS) will usually require that > you publish all your source code as well..That doesn't sound like freedom at all. -- Gemaakt met Opera's revolutionaire e-mailprogramma: http://www.opera.com/mail/
Reply by ●April 15, 20082008-04-15
"Boudewijn Dijkstra" <boudewijn@indes.com> writes:> Op Mon, 14 Apr 2008 08:51:00 +0200 schreef Chris H <chris@phaedsys.org>: >> The free RTOS that are really free (ie FOSS) will usually require >> that you publish all your source code as well.. > > That doesn't sound like freedom at all.Well in that case, it is a good thing it is *not true*. -- John Devereux
Reply by ●April 15, 20082008-04-15
Chris H <chris@phaedsys.org> writes:> In message <IO-dnWaR0svMup_VnZ2dnUVZ_oqhnZ2d@giganews.com>, ROB > <rob701101@yahoo.com> writes >>Hi, >> I am new to any RTOS and wanted to learn more about it. Can some post >>me small & freely available RTOS with documents details & source code. >>Also let me know, if these RTOS are absolutely FREE to use for commercial >>requirement. I am looking for small(<10KB), FREE(cost 0 cents), >>popular(used readily) RTOS :-) > > > There are many free RTOS but most if not all are usually chargeable > for commercial development > > Why would you want a free rtos for a commercial development? If you > are looking to be paid for your work you should pay others who > contribute to it. > > The free RTOS that are really free (ie FOSS) will usually require that > you publish all your source code as well..I heard that if you buy a commercial OS, usually they can claim royalties on sales of all your code. -- John Devereux
Reply by ●April 15, 20082008-04-15
Chris H wrote:> The free RTOS that are really free (ie FOSS) will usually require that > you publish all your source code as well..Are you sure about that? Or is it a case of "if you use my shared code, then you must share your code", which is entirely different situation.
Reply by ●April 15, 20082008-04-15
Terryc <newsfourspam-spam@woa.com.au> writes:> Chris H wrote: > >> The free RTOS that are really free (ie FOSS) will usually require >> that you publish all your source code as well.. > > Are you sure about that? > > Or is it a case of "if you use my shared code, then you must share > your code", which is entirely different situation.Yes, Chris was alluding to the GPL, which you paraphrase above. But in fact most free RTOSs are *not* GPL licenced, (as David Brown pointed out). Even programs that are (like e.g. linux) do not require publishing "all your source code", just the parts that link to the kernel. So you could build or buy hardware supported by linux, and install your own proprietary software on to it. But if you need to modify the kernel (e.g. write a special device driver) you would need to publish *that*. -- John Devereux
Reply by ●April 15, 20082008-04-15
Terryc wrote:> Chris H wrote: > >> The free RTOS that are really free (ie FOSS) will usually require that >> you publish all your source code as well.. > > Are you sure about that? > > Or is it a case of "if you use my shared code, then you must share your > code", which is entirely different situation. >In most cases (including GPL'ed software which is not directly linked, such as the Linux kernel), the rule is roughly "if you use my shared code, then you must shared your modifications and changes to it". Your own code is entirely your own business, and you only need to consider licenses when you directly link to other software. There are some people (those who believe that "free software" is "morally better" than mere "open source software") who want you to share all *your* code as well. But in most cases, that's a desire rather than a requirement.
Reply by ●April 15, 20082008-04-15
On 2008-04-15, Boudewijn Dijkstra <boudewijn@indes.com> wrote:>> The free RTOS that are really free (ie FOSS) will usually >> require that you publish all your source code as well.. > > That doesn't sound like freedom at all.It's also not true. -- Grant Edwards grante Yow! Do you like "TENDER at VITTLES"? visi.com
