Testing Real Time Operating System for Hardness

Question

I have an embedded device (Technologic TS-7800) that advertises real-time capabilities, but says nothing about 'hard' or 'soft'. While I wait for a response from the manufacturer, I figured it wouldn't hurt to test the system myself.

What are some established procedures to determine the 'hardness' of a particular device with respect to real time/deterministic behavior (latency and jitter)?

Being at college, I have access to some pretty neat hardware (good oscilloscopes and signal generators), so I don't think I'll run into any issues in terms of testing equipment, just expertise.

Answer 1

With that kind of equipment, it ought to be fairly easy to sync the o-scope to a steady clock, produce a spike each time the real-time system produces an output, an see how much that spike varies from center. The less the variation, the greater the hardness.

Answer 2

To clarify Bob's answer maybe:

Use the signal generator to generate a pulse at some varying frequency. Random distribution across some range would be best.

use the signal generator (trigger signal) to start the scope.

the RTOS has to respond, do it thing and send an output pulse.

feed the RTOS output into input 2 of the scope.

get the scope to persist/collect mode. get the scope to start on A , stop on B. if you can.

in an ideal workd, get it to measure the distribution for you. A LeCroy would. Start with a much slower trace than you would expect. You need to be able to see slow outliers. You'll be able to see the distribution.
Assuming a normal distribution the SD of the response time variation is the SOFTNESS. (This won't really happen in practice, but if you don't get outliers it is reasonably useful. ) If there are outliers of large latency, then the RTOS is NOT very hard. Does not meet deadlines well. Unsuitable then it is for hard real time work. Many RTOS-like things have a good left edge to the curve, sloping down like a 1/f curve. Thats indicitive of combined jitters. The thing to look out for is spikes of slow response on the right end of the scope. Keep repeating the experiment with faster traces if there are no outliers to get a good image of the slope. Should be good for some speculative conclusion in your paper.

If for your application, say a delta of 1uS is okay, and you measure 0.5us, it's all cool.

Anyway, you can publish the results ( and probably in the publish sense, but certainly on the web.)

Link from this Question to the paper when you've written it.

Answer 3

Hard real-time has more to do with how your software works than the hardware on its own. When asking if something is hard real-time it must be applied to the complete system (Hardware, RTOS and application). This means hard or soft real-time is system design issues.

Under loading exceeding the specification even a hard real-time system will fail (hopefully with proper failure indication) while a soft real-time system with low loading would give hard real-time results. How much processing must happen in time and how much pre/post processing can be performed is the real key to hard/soft real-time.

In some real-time applications some data loss is not a failure it should just be below a certain level, again a system criteria.

You can generate inputs to the board and have a small application count them and check at what level data is going to be lost. But that gives you a rating specific to that system running that application. As soon as you start doing more processing your computational load increases and you now have a different hard real-time limit.

This board will running a bare bones scheduler will give great predictable hard real-time performance for most tasks. Running a full RTOS with heavy computational load you probably only get soft real-time.

Edit after comment
The most efficient and easiest way I have used to measure my software's performance (assuming you use a schedular) is by using a free running hardware timer on the board and to time stamp my start and end of my cycle. Or if you run a full RTOS time stamp you acquisition and transition. Save your Max time and run a average on the values over a second. If your average is around 50% and you max is within 20% of your average you are OK. If not it is time to refactor your application. As your application grows the cycle time will grow. You can monitor the effect of all your software changes on your cycle time.

Another way is to use a hardware timer generate a cyclical interrupt. If you are in time reset the interrupt. If you miss the deadline you have interrupt handler signal a failure. This however will only give you a warning once your application is taking to long but it rely on hardware and interrupts so you can't miss.

These solutions also eliminate the requirement to hook up a scope to monitor the output since the time information can be displayed in any kind of terminal by a background task. If it is easy to monitor you will monitor it regularly avoiding solving the timing problems at the end but as soon as they are introduced.

Hope this helps

Answer 4

I have the same board here at work. It's a slightly-modified 2.6 Kernel, I believe... not the real-time version.

I don't know that I've read anything in the docs yet that indicates that it is meant for strict RTOS work.