Embedded-test hardware real-time operating system

I have an embedded device (Technologic TS-7800) that advertises real-time functionality, but I didn’t say “hard” or “soft”. ​​When I waited for the manufacturer’s response, I thought There is no harm in testing the system yourself.

In terms of real-time/deterministic behavior (delay and jitter), what are the established procedures to determine the “hardness” of a particular device?

During college, I can use some very neat hardware (good oscilloscope and signal generator), so I don’t think I will encounter any problems with testing equipment, just professional knowledge.

p>

I have the same board here. This is a slightly modified 2.6 kernel, I believe…not Real-time version.

I don’t know that I have read anything in the document, which shows that it is suitable for strict RTOS work.

I have an embedded device (Technologic TS-7800) that advertises real-time functionality, but it doesn’t say “hard” or “soft”. When I wait for the manufacturer’s response, I don’t think it will do any harm to test the system by myself. < p>

In terms of real-time/deterministic behavior (delay and jitter), what are the established procedures to determine the “hardness” of a particular device?

During college, I can use some very neat hardware (good oscilloscope and signal generator), so I don’t think I will encounter any problems with testing equipment, just professional knowledge.

p>

I have the same board here. This is a slightly modified 2.6 kernel, I believe…not a real-time version.

I don’t know that I have read anything in the documentation, which shows that it is suitable for strict RTOS work.

Leave a Comment

Your email address will not be published.