Background
The major reason for Rational Statemate users to perform Embedded Rapid Prototyping is to verify that the model functions properly in a real world environment. Today with Rational Statemate, when a model is tested it must simulate the environment that the system ultimately interacts with. Often the environment is very complex and difficult to completely describe via modeling, test vector files or programs. In the final analysis, the most accurate description of the target environment that insures the accuracy of the specification is only found by bringing the specification (i.e. model) to the actual target environment. This is the essence of Embedded Rapid Prototyping.
The following figure illustrates one such application of embedded rapid prototyping. Here, the engineer is able to run the Rational Statemate software on a laptop computer placed within the passenger compartment of a test vehicle. The laptop is linked to a convenient rack mounted embedded prototyping system located in the back of the vehicle. This embedded development system uses standard CPU hardware and embedded operating system (frequently a Real Time Operating System, or RTOS) with a mix of standard and specialized I/O interface cards connected (by cable or bus) to, and acting as the control components for, some prototype subsystem of the test vehicle.
The Rational Statemate model is used to generate code which is compiled and downloaded to the development system. When executed, the prototype code’s features can be observed both in the target hardware and in the Rational Statemate software. When a change needs to be made, the engineer simply changes the Rational Statemate model, regenerates code, compiles and downloads it to the target system. The next test is then ready to begin. This process can be repeated as many times as necessary until the model has been refined to the point where an accurate and complete specification can be finalized.