Target Requirements : Describing Signal Mapping to I/O Cards

Describing Signal Mapping to I/O Cards

The embedded rapid prototyping code generator supports mapping of basic data items and conditions, relevant to the current scope, to an open set of user defined I/O locations in the prototyping hardware. There is no support for events, user- defined types, array elements, records and fields in a record (except for enumerated types, which are regarded as integers).

The definition of an I/O card is done using an ASCII file, with the extension “. crd”. This .crd file contains the definition of the I/O card’s configuration, including:

Note:
It is assumed that an I/O card will require initialization in order to set it up for the desired port configuration, control mode, data handling, etc.

The compilation profile editor’s Options menu lists a menu item for I/O Mapping. This menu item invokes the I/O Mapping dialog (see the following figure). This dialog presents a mapping matrix that is used to identify the basic identity and type for each I/O card included in the system. Using a selection mechanism similar to that used in the Simulator, this mapping matrix guides the user in selecting data items relevant to the current scope and saves selected filled lines in the <profile name>.rgenset file. It does this by displaying a drop-down list of available selections when you right-click on the matrix cell for a given row and column.

 

As previously discussed, the mapping matrix dialog contains the following fields:

Displays all of the files named *.crd in the <workarea>/rprt files directory
Note: A single I/O card can have multiple ports. Each should be assigned a meaningful name.

At the bottom left corner of the window is a button labeled Single Polling Rate allows selection of one of two modes:

The definition of the polling rates is done using another menu item, Files >I/O Card Management.