• MISRA-C: 2004 5.6

• DO-178B, Section 6.3.2b 'Accuracy and Consistency of Low-Level Requirements'

• IEC 61508–3, Table A.3 (3) 'Language subset'
  IEC 61508–3, Table A.4 (5) 'Design and coding standards'

• ISO/DIS 26262-6, Table 1 (b) 'Use of language subsets'
  ISO/DIS 26262-6, Table 1 (e) 'Use of established design principles'
  ISO/DIS 26262-6, Table 1 (h) 'Use of naming conventions'

The identifier IntCounter is defined for two states, Scope_1 and Scope_2.

Not Recommended

To clarify the model, create unique identifiers—for example,IntCounter_S1 and IntCounter_S2—or define IntCounter at the parent level.

Recommended

For data with a global scope used in a function

• IEC 61508–3, Table A.3 (3) 'Language subset'
  IEC 61508–3, Table A.4 (4) 'Modular approach'
  IEC 61508–3, A.4 (5) 'Design and coding standards'

• ISO/DIS 26262-6, Table 1 (b) 'Use of language subsets'
  ISO/DIS 26262-6, Table 1 (f) 'Use of unambiguous graphical representation'
  ISO/DIS 26262-6, Table 1 (h) 'Use of naming conventions'

• DO-178B, Section 6.3.4f 'Accuracy and Consistency of Source Code'

• MISRA-C: 2004 12.2
  MISRA-C: 2004 12.4

The basic expression is

Y = f(U) + G

where in the function G is assigned a value. This modeling pattern is realized:

static real_T GlobalOperator_1(real_T U_1)
{
  real_T Y_1;

  /* Rreturns Y and modifies the global G_1 */
  Y_1 = sin(U_1);
  DWork.G_1 = -Y_1;
  return Y_1;
}

static real_T GlobalOperator_2(real_T U_2)
{
  real_T Y_2;

  /* Returns Y and modifies the global G */
  Y_2 =sin(U_2);
  DWork.G_2 = -Y_2;
  return Y_2;
}

Limit the length of data object names to 31 characters or fewer.

• MISRA-C:2004 Rule 5.1

• Simulink.AliasType

• Simulink.NumericType

• Simulink.Variant

• Simulink.Bus

• Simulink.BusElement

• Simulink.IntEnumType

• MISRA-C:2004 Rule 5.1

• Exported global

• Imported Extern

• Imported Extern Pointer

• Custom storage class

• MISRA-C:2004 Rule 5.1

Simulink Coder checks models for standard C language key words. Expand the list of reserved identifiers to include project specific identifiers. Examples include target-specific clashes, standard and custom library clashes, and other identified clashes.

• Simulation Target Pane: Symbols in the Simulink documentation

• Reserved Keywords in the Simulink Coder documentation

• Reserved names in the Simulink Coder documentation

MISRA-C:2004, Rule 20.2

To improve MISRA-C:2004 compliance of generated code, insert a data type conversion block when using signals of type single (real32_T) as inputs to the following blocks:

• Math

• Trigonometry

• Sqrt

The data type conversion block to changes the data type to double (real_T)

The function prototypes for many math functions require an input of type double. To accommodate the function prototype, you can add a data type conversion block. As an alternative to the data type conversion block, you could define a new function interface using the Target Function Library (TFL).

• MISRA-C: 2004 Rule 10.2

Not Recommended