This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Comparison of Embedded RTOS

Other Parts Discussed in Thread: MSP430F5338

Hi Team,

One of my customers is looking to work with TI RTOS on the MSP430F5338. During the discussion, on of the queries that came up was that if there is any documented comparison/advantages in terms of features of our TI-RTOS vs the commonly available embedded OS such as FreeRTOS, micro OS etc. Do we have something of this sort available that can be shared with the customer?

Thanks in advance

  • Nishant:

    We don't have anything in detail for a couple of reasons:

    1. The companies behind FreeRTOS and uCOS are partners and we don't regard them as competition. As long as the customer uses TI Silicon, it's OK.

    2. Although I will discuss some general distinctions below, many embedded RTOS products are pretty similar in features and a customer could be successful regardless of which one they chose. In terms of FreeRTOS v TI-RTOS, TI-RTOS generally has more features but FreeRTOS has a smaller footprint.

    I think the following differences are of most relevance:

    1. Cost. Most RTOS products, except FreeRTOS and TI-RTOS, will cost money (uCOS is free only for non-commercial use). This is often a big deciding factor and is certainly a big reason why FreeRTOS is so successful.

    2. Integrated drivers, BSPs, and Stacks. FreeRTOS is a kernel-only solution. For something like an MSP430, that may be fine but for devices with more peripherals, especially networking ones, and memory, customer will likely want additional stacks (e.g. TCP/IP), device drivers, and board initialization code. Writing these or integrating free stacks on FreeRTOS takes effort. TI-RTOS provides these pre-integrated and tested.

    IMO, most customers will not make decisions based on minor features like number of priority levels, etc.

    Regards,

    Nick