|
I'm never prepared for the culture shock from going between Windows development to embedded development, but today it's slightly less because I'm looking at an operating system called On Time. The main feature as far as I can tell that makes it different from other RTOSs that I have seen is the fact that it uses Windows executables for it's applications. You have to run them through a translation stage to get them to stop being executables and become usable, but it means that you can take advantage of your favourite IDE and compiler. This means that your embedded code can be optimised by VC++, or I might give the Intel C++ compiler a try this afternoon, and so you have the best optimisations that are available. One of the things that as a Windows programmer I know, but it's harder to convince an embedded coder, is that your compiler will beat your non-design optimisations hands down every time. Of course there's nothing like using the correct algorythm for the job in the first place.
The really interesting thing about this system is that it implements a few of the Win32 API calls. It supports threading, disk access and a nice chunk of other functionality. At the moment I'm wondering if Rotor could be convinced to compile under it... Not that I'll ever be daft enough to ever try.
What other blogs are saying about this post.
11:45:52 AM 
|
|
