INtime® 3.1 Software - tenAsys

INtime 3.1 Software
This flowchart shows steps typically taken by RT software designers. When complete,
the prototype system is ready to test, debug, and fine-tune.
Figure 5-1. Typical development cycle for INtime applications
Decide which parts of the
application are RT and
which are Windows.
Define the application.
No
Is special hardware
needed
Yes
Build or purchase
custom hardware
Write code
No
Is an INtime
driver available
Yes
Compile/assemble
code
Write and test driver
Use available driver
Link with operating system
interface libraries
Partition the application into RT and Windows components.
Define processes, then define threads, interrupt levels, and priorities. Decide which objects to
use. Define interrupts, handlers, and levels.
Decide on hardware and device drivers. Decide how to implement a multi-user environment and/
or an operator interface.
Decide if you need custom hardware that solves a unique problem or gathers data in a unique way.
56