Fundamentals of Real-Time Operating Systems

3/10/2011 12:54 PM EST

Jack Gannsle is an old hand in the embedded world. His presentation on RTOS' is a pretty nice intro to the topic, if you have a few notions of what an OS should be doing anyway. He presents the mutex and the semaphore without confusion. His discussion of whether or not to "roll your own" is sensible, and his conclusion: "no" is rational. Someplace towards the end of presentation, the sponsor plugs his own product, which to my mind is fine... overall, if you'd like a refresher on RTOS or want to see what it's about, this is a pretty good way to do so.

3/20/2011 3:31 AM EDT

A very thanks to "Micrium" and "Jack" for presenting some basics of RTOS is very easy and understanding way.This is surely one of the best presentations, i have been through.

Being from hardware-designer background, i always hv the inquisitiveness of how the actual software uses the hardware we design. Today i understood, how the RTC(Real Time Clock) and other timers present in system are used for clock-tics of OS.. And how kernel uses these clock tics for scheduling

thanks again..
with regards, pekon

3/20/2011 6:35 AM EDT

As a RTOS designer myself , I find this short course very informative and concise. Some more details on memory management would add value to the content. In my design i had found the bit map driven memory pool management very efficient and requiring less amount of code. Also some more explanation on importance of re entrant code and critical code section of the kernel may be included.

4/1/2011 2:57 AM EDT

It is a very interesting and informative and clearly brings out various issues in Real time Operating system

4/1/2011 10:38 AM EDT

How long is the presentation (I need to set aside some time to view it)?

4/6/2011 12:56 AM EDT

I have had my head stuck under automotive software systems for years with Proprietary RTOS’s. So I decided to look up and see what the fuss was about purchasing an RTOS. This presentation had advertisement written all over it. I feel there were a lot of misguiding statements about how many lines of code is needed to make an RTOS, what functionality is needed from an RTOS, and why roll your own. I would love to have that debate, but odds are it will occur the next time I meet one of those young engineers that are quick to learn an RTOS tool rather than learn to code properly. Don’t get me started on developing a proper CAN stack, Vector has cornered that market. I laugh when they tell me how much companies pay for one. One good note is that things have not changed much over the years. Finally, future embedded engineers should forgo an education and simple learn how to figure out what libraries they need to include with Embedded Linux. That’s scary.
Thank for the lesson.

4/6/2011 1:32 PM EDT

You guys might like to check out a contribution from Oz made by Barry Kauler,
200 pp book/disc :
Object Oriented Flow Design for Embedded Systems.
a new simple unified approach
terse code, v good and MUCH smaller than uCOS.
Google Barry Kauler Australia to find this.

4/6/2011 11:30 PM EDT

So where can I find a robust scheduler that gets the job done?

5/9/2011 11:05 AM EDT

a

1/10/2012 10:01 AM EST

It was a very good presentation. i understood many minute details of the RTOS system. As i belong to no english speaking country, somewords are difficult to understand, hence it would be very helpful if the sub titles of presentation were displayed as the presenter speaks .

1/20/2012 7:59 PM EST

anyone here knows how to implement keep alive memory? this is an automotive application where data is maintained in RAM and reused when ignition is cycled off to on. I tried many archives but was not able to find any valuable info.. Any info is appreciated.
Lou