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.
Part Number: MSP430FR5994
Announcing the release PRTOS, an open-source preemptive real time operating system kernel for bare-metal applications.
PRTOS is released by Cleveland Engineering Design - the developer of the CoRTOS cooperative real time OS, also available on Sourceforge.
PRTOS presently supports the MSP430 and AVR architectures.
PRTOS is available on Sourceforge at https://sourceforge.net/projects...
PRTOS has one of the smallest footprints of any true preemptive system: 4.3kB with all the features below (ti MSP430 compiler, no optimizations);
PRTOS provides the following features:
Delay & Time
ISR -> task functions
Nicholas LIndan - Cleveland Engineering Design, LLC
CCS8.2,tirtos_msp43x_2_20_00_06,compiler TI v16.9.9.LTS,XDCtools 3.32.0.06
and the following defaults:
I have obtained the following MSP5994 benchloop example project results:
Computing the Min, Max, Avg cycles for each [BIOS API]
5 5 5 Hwi_restore()3 3 3 Hwi_disable()113 113 113 Hwi_dispatcher_prolog133 133 133 Hwi_dispatcher_epilog247 247 247 Hwi_dispatcher609 609 609 Hardware_Interrupt_to_Blocked_Task402 402 402 Hardware_Interrupt_to_Software_Interrupt71 71 71 Swi_enable()18 18 18 Swi_disable()28 28 28 Post_Software_Interrupt_Again149 149 149 Post_Software_Interrupt_without_Context_Switch343 343 343 Post_Software_Interrupt_with_Context_Switch1 7741 6173 Create_a_New_Task_without_Context_Switch231 231 231 Set_a_Task_Priority_without_a_Context_Switch322 322 322 Task_yield()55 55 55 Post_Semaphore_No_Waiting_Task260 260 260 Post_Semaphore_No_Task_Switch382 382 382 Post_Semaphore_with_Task_Switch70 70 70 Pend_on_Semaphore_No_Context_Switch414 414 414 Pend_on_Semaphore_with_Task_Switch18 18 18 Clock_getTicks()
Could you post equal or similar test results for PRTOS?
I very appreciate small PRTOS footprint you have presented.
If I had answered to your question, please mark this post as Resolved.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Tomasz Kocon:
Tomasz Kocon wrote:
> I have obtained the following MSP5994 [I am assuming ti RTOS] benchloop example project results:> Computing the Min, Max, Avg cycles for each [BIOS API]> 5 5 5 Hwi_restore()> 3 3 3 Hwi_disable()> 113 113 113 Hwi_dispatcher_prolog ...> Could you post equal or similar test results for PRTOS?
Every RTOS implementation is different. Although all, hopefully, meet the same needs they all have a different view of what an RTOS is, how to implement it and what API to wrap around it. I haven't made a count of the number of RTOS offerings on the web but I would guess there are at least 100. The one-and-only true RTOS is usually the one a person imprinted on because it was the first one they learned - like the first language they learned at their mother's' knee.
PRTOS is very different from ti's RTOS in almost every respect with the exception that it is possible to use either one to design a given product.
A comparison of the two based on the above would be meaningless. The ti API calls you list have no counterpart in PRTOS, and the API calls in PRTOS have no counterpart in ti's offering. - it would be like comparing apples to peaches. That doesn't illegitamize either offering - either the RTOS or the fruit.
One very big difference is that PRTOS is a naked kernel. ti's implementation is surrounded by a cloud of communications drivers. If you need some of those drivers you might be better off with ti's offering. If your product is naked or uses a communications protocol not present in ti's offering you might be better off with PRTOS.
If you are starting out just learning about RTOS then the PRTOS model is much simpler and the documentation clearer. Of course, if you are already a ti maven that comparison would be reversed. I encourage those that may be intrigued to download the PRTOS documentation - its only a 40 page PDF - and see for themselves -- sourceforge.net/.../.
An even simpler learning platform is the CoRTOS cooperative RTOS - also available on Sourceforge at sourceforge.net/.../
> I very appreciate small PRTOS footprint you have presented.
Thank you very much. FWIW the basic PRTOS kernel compiles to ~1.3kB -- with all the options turned on the size is ~4kB (varies, of course, with optimization levels and all that).
In reply to Nicholas Lindan:
V102 is released on Sourceforge
This version adds semaphores and makes minor updates to the documentation.
Mitch Ridgeway wrote:
> This looks awesome!
Err, no, not awesome. Just yet-another RTOS kernel. Going to the moon, now that was awesome. I mean, if the word keeps getting devalued what are people going to say when something really awesome comes along?
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.