rtos

Problem I am creating a Windows 7 based C# WPF application using .Net 4.5 , and one its major features is to call certain functions that interface with custom hardware with a set of user defined cycle times. For example the user might choose two functions to be called every 10 or 20 milliseconds and another every 500 milliseconds. The smallest cycle time the user can choose is 1 milliseconds. At first it seemed that the timings were accurate and the functions were called every 1 millisecond as required. But we later noticed that about 1-2% of the timings were not accurate, were some functions

I stumbled across a free state machine tool . This appears to be for programming embedded systems graphically. By doing so, the author claims that the resulting code is more maintainable than if an RTOS had been employed. This tool is based on UML, which is nice to know, but has a steep learning curve. I would like to know what some of the more experienced programmers here think of this tool. I am developing an embedded application for the LM3S5P36 microcontroller. TI has an IDE called Code Composer Studio (CCS). I have not got into CCS yet, but I doubt it has the cool feature of being able to

Is it necessary to code RTOS in C language always? Why can't that be coded in java or some other technology..?? Is that because of the absence of pointer concept in java? Garbage collection is the big reason against Java being Real Time. JIT is another, but it could be overcome. In general though, C being effectively portable assembly gives very predicable run-time performance, and that's essential for reliable real-time execution. Real time systems can be programmed in other languages too. Java has a Java RTS System for example. Contrary to other answers, there is reasonable amount of work on

I am looking for tools and techniques for prototyping (virtual prototyping), simulation, and testing of deeply embedded C code on desktop Windows, including building realistic embedded front panels consisting of buttons, LEDs, and LCD displays (both segmented and graphic). I'm specifically interested in a possibly low-level approach, using pure C code and raw Win32 API rather than MFC, .NET/C#, vxWidgets or Qt. I'd also like to use free development tools, such as Visual C++ Express with Platform SDK and ResEdit for editing resources. I'm looking for code examples to render graphic LCDs (from

I am looking for mostly used 5 Real-Time operating systems. I searched on Google and Wikipedia has a list of RTOSs, but they are in random order and also I am not convinced that all of them really operating real-time. One more question: can we include Windows 7? When we set priority of 5 tasks, for example to realtime. Real-time operating systems that I have come in contact with, in order of (subjective) impact: VxWorks QNX eCos RTLinux Especially VxWorks has a long history in critical applications - for example, in cars and various NASA space platforms. It is however neither free nor open

I mean how and why are realtime OSes able to meet deadlines without ever missing them? Or is this just a myth (that they do not miss deadlines)? How are they different from any regular OS and what prevents a regular OS from being an RTOS? Benoit Meeting deadlines is a function of the application you write. The RTOS simply provides facilities that help you with meeting deadlines. You could also program on "bare metal" (w/o a RTOS) in a big main loop and meet you deadlines. Also keep in mind that unlike a more general purpose OS, an RTOS has a very limited set of tasks and processes running.

I have been developing an RTOS based embedded software in C and I have encountered a problem regarding shared resource access from several threads. I have two problems. The first one is seting and getting a value of state variable in state machine. Below is the header file for StateMachine "object": typedef enum{ STATE_01, STATE_02, STATE_03, STATE_04 }state_e; // state machine instance typedef struct{ state_e currState; }StateMachine; extern state_e GetState(StateMachine*); extern void SetState(StateMachine*, state_e); The implementation of the access methods is following: state_e GetState