Sonsivri
 
*
Welcome, Guest. Please login or register.
Did you miss your activation email?
May 26, 2017, 11:01:05 23:01


Login with username, password and session length


Pages: 1 [2]  All
Print
Author Topic: If you were going to start over tomorrow... Which RTOS?  (Read 4516 times)
0 Members and 1 Guest are viewing this topic.
baybay
Newbie
*
Offline Offline

Posts: 23

Thank You
-Given: 6
-Receive: 27


« Reply #25 on: September 29, 2016, 10:17:58 10:17 »

You can use CMSIS-RTOS api with RTX RTOS. CMSIS-RTOS API supported by some RTOSes. if you need, you can easily change rtos library.. API is the same for your perpective.. only static library will be changed on link time.
« Last Edit: September 30, 2016, 12:47:57 00:47 by baybay » Logged
monkey
Newbie
*
Offline Offline

Posts: 20

Thank You
-Given: 69
-Receive: 10


« Reply #26 on: October 21, 2016, 08:50:06 08:50 »

I think any RTOS is a great choice and code will become cleaner, but use an "OS" abstraction layer so you can easily change RTOSES in the future. Start with free one of course.
Look at what debug support for whatever IDE you use to help check task stacks , timers and mailboxes etc.

Many examples of abstraction layers on NXP, ST sample code.
Good luck

Logged
baybay
Newbie
*
Offline Offline

Posts: 23

Thank You
-Given: 6
-Receive: 27


« Reply #27 on: October 21, 2016, 09:27:22 09:27 »

I think any RTOS is a great choice and code will become cleaner, but use an "OS" abstraction layer so you can easily change RTOSES in the future. Start with free one of course.
Look at what debug support for whatever IDE you use to help check task stacks , timers and mailboxes etc.

Many examples of abstraction layers on NXP, ST sample code.
Good luck

CMSIS-RTOS api is also abstraction layer..

Logged
anotherandrew
Newbie
*
Offline Offline

Posts: 20

Thank You
-Given: 111
-Receive: 6


« Reply #28 on: October 23, 2016, 01:13:54 01:13 »

I'm the fan of FreeRTOS; it is fairly generic and seem to be the good standard for all ARM. CMSIS compliant version that comes with STM32Cube is also compatible with other Cortex platform. Different memory allocator allows me to tune per application, and debugging is also straight forward with gdb. Thread implementation is also reasonable with good set of common primitives.
Logged
nPn
Newbie
*
Offline Offline

Posts: 12

Thank You
-Given: 6
-Receive: 3


« Reply #29 on: May 01, 2017, 03:43:21 03:43 »

For what it's worth, un my personal experience the greatest barriers to adopting an OS for a micro project is writing peripheral drivers.

Basic OS stuff, like memory footprint, context switching times, synchronization cost, etc are very competitive across the board. Unless you plan to build devices in massive volume with cheapest parts, it's not worth optimizing small performance deltas.

I like ChibiOS for its simple peripheral drivers (most comprehensive are for STM32), but anything where I need full peripheral functionality and have to write my own driver, I'd look at something like uCOS or RTX since it's easier to write new drivers. Their commercial licensing terms are clearer too, since they have no open source contributors.
Logged
WeSo
Newbie
*
Online Online

Posts: 11

Thank You
-Given: 0
-Receive: 8


« Reply #30 on: May 01, 2017, 12:48:26 12:48 »

For what it's worth, un my personal experience the greatest barriers to adopting an OS for a micro project is writing peripheral drivers.
I agree, even the microcontrollers companies themselves have problems with it. For example, TI has its own RTOS (TI-RTOS) which doesn't work (its driver) with the I2S module of CC3200 but nevertheless the driver works perfect with FreeRTOS.

Almost 3 years later, add other vote for FreeRTOS.
Logged
Pages: 1 [2]  All
Print
Jump to:  


DISCLAIMER
WE DONT HOST ANY ILLEGAL FILES ON THE SERVER
USE CONTACT US TO REPORT ILLEGAL FILES
ADMINISTRATORS CANNOT BE HELD RESPONSIBLE FOR USERS POSTS AND LINKS

... Copyright 2003-2999 Sonsivri.to ...
Powered by SMF 1.1.18 | SMF © 2006-2009, Simple Machines LLC | HarzeM Dilber MC