Reply by MArk January 12, 20042004-01-12
So can anyone say when RTOS would be necessery
it seems to me that for 8051 complexity of projects
it is almost never needed?

What kind of applications would "need" RTOS?


Reply by Eric January 7, 20042004-01-07
Another small RTOS to check out is Sciopta (www.sciopta.com).
It's good for 8/16/32 bit - based on assembler and c (source code included)
and it's royalty free.....


"Mickey" <mmmh@mmmmh.com> wrote in message
news:bt4r86$dh0$1@garrison.globalnet.hr...
> Is anyone here using RTOS from Keil? > > Does it make job much easier? > > What are it's advantages and dissadvantages? > > Thanx, Mickey. > >
Reply by TheDoc January 4, 20042004-01-04
"Mickey" <mmmh@mmmmh.com> wrote in message
news:bt4r86$dh0$1@garrison.globalnet.hr...
> Is anyone here using RTOS from Keil? > > Does it make job much easier? > > What are it's advantages and dissadvantages? > > Thanx, Mickey. > >
I have not used Tiny, but I can say the FULL version of RTX51 works extremely well, even on a plain 8051 at 11.059MHZ.. quite efficient, even with banking support for my application. Your application may or may not need an RTOS.. as always, it's the application that determines the resources and OS ( if any )..
Reply by Thad Smith January 3, 20042004-01-03
Mickey wrote:
> "Jack Klein" <jackklein@spamcop.net> wrote in message
>>>Does it make job much easier? >>What job is that? > I ment to comment this question of yours above but I realised it is in > place, I spoke of "job" as generally a medium sized project (device), > like using keys, LCD, EEPROM, AD and so ...
IMO, the major factors are whether you need to doing more than one thing "simultaneously" (multi-tasking), and whether the various tasks have complicated states, which would make round-robin processing messy. Thad
Reply by Mickey January 3, 20042004-01-03
Hi, Mark.

> I looked into their Tiny RTOS some years ago.
What was the reason you considered that RTOS in the first place?
> When it switches contexts it > swaps out all 256 bytes of on-board RAM, which made it too slow for our > purposes. That was for a "basic" 8051, it may do better with some of the > newer and faster 8051 derivatives.
I think they have worked it out allready. They should have in few years.
> Do you really need a full-featured RTOS? We found that the best move for
us
> was to roll our own - a simple round-robin task switcher that was quite > effective for our moderate-complexity application.
Why did you make your own RTOS, was it too complex to handle all the things without RTOS?
Reply by Mickey January 3, 20042004-01-03
"Jack Klein" <jackklein@spamcop.net> wrote in message
news:13fcvvch9nkbtki0ub69iofgj8onpkss73@4ax.com...

I have also done quite a few things without RTOS I just wanted to find
out is it worth to learn for example Keil RTOS, and does it make
development much faster and does it take too much resources and
so on.

Thanks for comments anyways.

> > Does it make job much easier? > > What job is that?
I ment to comment this question of yours above but I realised it is in place, I spoke of "job" as generally a medium sized project (device), like using keys, LCD, EEPROM, AD and so ...
Reply by Mark Ainsworth January 3, 20042004-01-03
I looked into their Tiny RTOS some years ago.  When it switches contexts it
swaps out all 256 bytes of on-board RAM, which made it too slow for our
purposes.  That was for a "basic" 8051, it may do better with some of the
newer and faster 8051 derivatives.

Do you really need a full-featured RTOS?  We found that the best move for us
was to roll our own - a simple round-robin task switcher that was quite
effective for our moderate-complexity application.

Mark Ainsworth

"Jack Klein" <jackklein@spamcop.net> wrote in message
news:13fcvvch9nkbtki0ub69iofgj8onpkss73@4ax.com...
> On Fri, 2 Jan 2004 23:33:38 -0000, "Mickey" <mmmh@mmmmh.com> wrote in > comp.arch.embedded: > > > Is anyone here using RTOS from Keil? > > I have used a few different RTOS from different vendors, and written a > few myself, but I haven't used that one. > > > Does it make job much easier? > > What job is that? > > > What are it's advantages and dissadvantages? > > > > Thanx, Mickey. > > There are two very different issues here. > > 1. Whether or not your project requires an RTOS at all or not. I > have done quite a few projects with 8051 family controllers and never > needed one. Originally it was not too likely that many applications > that needed an RTOS could even fit well on an 8051, but newer > derivatives are faster and have larger memory spaces, so it is > possible. > > 2. If your project could benefit from an RTOS, exactly what RTOS > would be best depends a great deal on your application and its > requirements. > > Below is copy of a reply to another post I made here in > comp.arch.embedded to another poster's question about use of an RTOS > in embedded systems. I still feel that it is a very satisfactory > answer. At least one small company that produces an RTOS for several > embedded processors thought it was satisfactory also -- they asked me > for permission to quote it on their web site, which I gave. > > ======== > To answer the question of when there is a need for an RTOS, the answer > is almost never, at least in the sense that something that is possible > with one would be literally possible without one. > > As to when it might be a very good idea to use an RTOS, that's a > little different. In my experience it becomes a good idea to consider > using an RTOS when the requirements for a system include a large > number of asynchronous events, multiple priority levels, and a > significant percentage of processor loading. > > There are many different RTOS, commercial, freeware, and open source, > that can be used on different processors, but that is mostly practical > for 16-bit and up processors. > > As to a good place to read about, and ask questions about, RTOS issues > is news:comp.realtime. Look for their FAQ, there is a large amount of > information. > ======== > > The full thread may be found at the following link: >
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&c2coff=1&th=fc49592d79e3803d&rnum=1
> > -- > Jack Klein > Home: http://JK-Technology.Com > FAQs for > comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html > comp.lang.c++ http://www.parashift.com/c++-faq-lite/ > alt.comp.lang.learn.c-c++ > http://www.contrib.andrew.cmu.edu/~ajo/docs/FAQ-acllc.html
Reply by Jack Klein January 3, 20042004-01-03
On Fri, 2 Jan 2004 23:33:38 -0000, "Mickey" <mmmh@mmmmh.com> wrote in
comp.arch.embedded:

> Is anyone here using RTOS from Keil?
I have used a few different RTOS from different vendors, and written a few myself, but I haven't used that one.
> Does it make job much easier?
What job is that?
> What are it's advantages and dissadvantages? > > Thanx, Mickey.
There are two very different issues here. 1. Whether or not your project requires an RTOS at all or not. I have done quite a few projects with 8051 family controllers and never needed one. Originally it was not too likely that many applications that needed an RTOS could even fit well on an 8051, but newer derivatives are faster and have larger memory spaces, so it is possible. 2. If your project could benefit from an RTOS, exactly what RTOS would be best depends a great deal on your application and its requirements. Below is copy of a reply to another post I made here in comp.arch.embedded to another poster's question about use of an RTOS in embedded systems. I still feel that it is a very satisfactory answer. At least one small company that produces an RTOS for several embedded processors thought it was satisfactory also -- they asked me for permission to quote it on their web site, which I gave. ======== To answer the question of when there is a need for an RTOS, the answer is almost never, at least in the sense that something that is possible with one would be literally possible without one. As to when it might be a very good idea to use an RTOS, that's a little different. In my experience it becomes a good idea to consider using an RTOS when the requirements for a system include a large number of asynchronous events, multiple priority levels, and a significant percentage of processor loading. There are many different RTOS, commercial, freeware, and open source, that can be used on different processors, but that is mostly practical for 16-bit and up processors. As to a good place to read about, and ask questions about, RTOS issues is news:comp.realtime. Look for their FAQ, there is a large amount of information. ======== The full thread may be found at the following link: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&c2coff=1&th=fc49592d79e3803d&rnum=1 -- Jack Klein Home: http://JK-Technology.Com FAQs for comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html comp.lang.c++ http://www.parashift.com/c++-faq-lite/ alt.comp.lang.learn.c-c++ http://www.contrib.andrew.cmu.edu/~ajo/docs/FAQ-acllc.html
Reply by Mickey January 2, 20042004-01-02
Is anyone here using RTOS from Keil?

Does it make job much easier?

What are it's advantages and dissadvantages?

Thanx, Mickey.