Target Requirements : Data Types Introduced to the Intrinsics Library : Report Elements for Input Mapping

Report Elements for Input Mapping

If there are model elements that require input mapping, Rational Statemate generates the tree-like structure of input mapping functions that is similar to the tree of init() functions in the model. Each such function calls to the in_func() field of those report elements that belong to the current scope.

There are three fields of report element that control the input mapping mechanism:

elem_value - The pointer to the actual value of the element. It is used in the input mapping if the model element that corresponds to this report element is dynamically double buffered and the set*() function must be called.
new_value - The double buffering information. If this pointer is ZNIL, the model element is dynamically double buffered. Otherwise, the value received from the card is directly assigned to the variable in the code referenced by this pointer.
received_val - The buffer where the data read from the card is stored until it is assigned to the model element. This field is part of API between user-written card driver and generated code. The card driver should put there the value that it reads from the card.