RTOS brands

Hey, that's cool: An RTOS in hardware.

But my experiences spans 2 decades and seven or more RTOS vendors .. of which only two vendors have given what I consider to be

Generally I have not been the one making the original decision... just dealing with the consequences! :-(

It should be remembered once you pick an RTOS for a product, you are pretty much locked in for the life of the product.

There is nothing worse than working on a RTOS, where you don't have source, where the vendor decides to stop supporting a particular processor!

Since moving to rtems, on the rare occasions where I have had a problem I have ALWAYS been pleasantly surprised by the level of support the developer community provides!

Generally I would say whatever you do, commercial or open source make sure you get an RTOS with source code, that way you ALWAYS have the option of fixing problems yourself.

Regards

Paul

hi, this is really cool RTOS, because it's based on HW. However, is there any customer adopting it? and is it cheap?

I add one more: Worse if you have no source at all.

Only thing our customers struggle a bit: Our kernel is written in assembler. It is sometimes the first time they need to see assembler sources :-)

That sounds a lot like OSE.

/RogerL

We are kind of a spin-off. But only the basic idea (direct message passing) is the same which is _not_ an ENEA brand BTW. More on Sciopta's history ?

Sciopta's functionality is comparable OSE Delta with the size of 2 times OSE Epsilon :-) On ARM: 2K (minimal set of functions needed for an application) to