hisl_0071: Configuration Parameters > Hardware Implementation > Inconsistent hardware implementation settings

R2026b

Ensure consistent hardware implementation settings between production and test hardware

Usage: High-Integrity System Modeling

Guideline ID: hisl_0071

Rules

hisl_0071: Configuration Parameters > Hardware Implementation > Inconsistent hardware implementation settings

Inconsistencies or under-specification of hardware attributes can result in incompatible code generation for production hardware. For compatible code generation, these configuration parameters must be the same between production hardware and test hardware:

  • Byte ordering

  • Signed integer division rounds to

Rationale

Efficient code generation

Verification

Check safety-related settings for hardware implementation (Simulink Check)

Tips

  • Simulink® and Simulink Coder™ require two sets of target specifications. The first set describes the final intended production target. The second set describes the currently selected target. If the configuration parameters do not match, the code generator creates extra code to emulate the behavior of the production target.

  • Inconsistent hardware parameters between production hardware and test hardware can be avoided by selecting configuration parameter Test hardware is the same as production hardware.

Industry Standards

  • ISO 26262-6, Table 4 (1a) 'Walk-through of the design'

    ISO 26262-6, Table 4 (1b) 'Inspection of the design'

    ISO 26262-6, Table 7 (1a) 'Walk-through'

    ISO 26262-6, Table 7 (1c) 'Inspection'

    ISO 26262-6, Table 7 (1n) 'Back-to-back comparison test between model and code, if applicable'

    ISO 26262-6, Table 10 (1e) 'Back-to-back comparison test between model and code, if applicable'

  • DO-331 MB.6.3.2.c 'Compatibility with Target Computer'

    DO-331 MB.6.3.3.c 'Compatibility with Target Computer'

Version History

Introduced in R2021a

See Also

(Simulink Coder)