CMSIS-RTOS

You could try mbedOS. I believe it's based off CMSIS-RTOS. os.mbed.com/.../index.html

FreeRTOS can be also used with CMSIS-RTOS. I can put it this way, which one is better a native FreeRTOS or a FreeRTOS with CMSIS-RTOS?

BigG, why do you prefer mbedOS over FreeRTOS? Is it easy usage and mass libraries or are there any technical advantages? 

I used mbed platform long time ago it is good for fast prototyping but it has so many abstractions that hides many things like Arduino platforms. I want something that can be used for real-time applications which can be also certified if required. 

MBED OS and CMSIS-RTOS are changing so fast that I can't follow anymore what they are, what they wrap and what they are based upon 

I know TI-RTOS and FreeRTOS fairly well. Although they are completely different, I find it easy to switch and port between the two, because the concepts are the same:

• scheduler
• tasks
• messages and queues
• semaphores
• events (between tasks)

If I had to make a training :) that's targeting a particular vendor or controller, I'd choose an OS that has good examples from that vendor.
If you then build a training example for the concepts above, I think you handle the 80% that's common between all of the RTOSes. 

Thanks  Jan Cumps. Therefore, I think it is better to go with native FreeRTOS. I am targeting STM32 because we have STM32 kits but I want it to be vendor independent. I think FreeRTOS is not bad as it can support many vendors.

As you mentioned, schedulers, tasks, semaphores, mutex, messages, events, interrupts are main elements and I want to cover those. Those are fundamentals. I just want to make sure, the thing I am teaching is the most beneficial. 

Normally I don't pay much attention to emailed newsletters but this one caught my eye as the latest from ST mentions Azure RTOS with STM32F7.

www.st.com/.../x-cube-azrtos-f7.html

Self promotion :) : balearicdynamics and I made a project last year, with FreeRTOS, that uses most of the principles there:

• scheduler and task
• semaphore/mutex
• message queue
• events and inter-task messages
• tasks going to sleep
• interrupt 

additional:

• controller going to low power
• controller wakes up via HW interrupt when data arrives on UART and kicks off a message.
• wifi
• AWS IoT / MQTT

It is interesting. I am biased against Microsoft products but this one looks OK. It also supports certifications. However, "X-CUBE-AZRTOS-F7 is only an STM32Cube integration of middleware stacks from Microsoft^® Azure^® RTOS." It is a bit confusing, I need to look for Azure RTOS in detail. 

Thanks Jan Cumps. It looks like a good example of RTOS project. I will also investigate low power RTOS design but I have a long way to go before I dive into it. 

This part is most of the time vendor dependent.
What is independent: telling FreeRTOS what sleep modes are allowed. FreeRTOS knows when a next job is due and will know how to wake up.
What is dependent: how you work with HW drivers in low power and wake up FreeRTOS when a HW event happens. Like most of the HW/driver logic, this is not abstracted by the RTOS.

msimon said:

need to look for Azure RTOS in detail. 

It's FreeRTOS. My example above uses it.

Sorry, it was reply to BigG's comment but it sit under yours. I have also read you made hello world project with FreeRTOS, blinking an led :) 

No, Azure RTOS is Threadx - previously a commercial RTOS from Express Logic.

It has many similarities to FreeRTOS.

No, Azure RTOS is Threadx - previously a commercial RTOS from Express Logic.

It has many similarities to FreeRTOS.

You are right. I was mixing with Amazon's RTOS. That's the one I'm using in my example.