rtel wrote on Tuesday, January 15, 2013:
It has the same functional model, but a few API differences, most notable in the two following areas:
1) SafeRTOS does not permit any dynamic memory allocation, so API calls that create an object (task, semaphore,etc.) have to pass in a buffer that will hold the object in an additional parameter. Generally in a safety critical application the buffer will be statically allocated.
2) As function names are prefixed with their return type, functions that are void in FreeRTOS but return error codes in SafeRTOS will have a different a prefix.
SafeRTOS is a fully safety certified product that comes with documentation packs that are qualified to various international safety standards - its price reflects that (really you are paying for the certification rather than the software).