FAQ 277: Unsuitable Embedded Hardware Options

Question

The build process of a model fails with the following error message:
------------------------------------------------------------
RTI Build Error
You have specified options for Embedded hardware on the Hardware
Implementation page of the Configuration Parameters dialog which
are not suitable for RTI<XXXX>:
Option: "Device type"
Current value: Generic->Custom
Requested value: Custom
------------------------------------------------------------
*** RTI Build detected errors in model configuration.
*** Stopped RTI build procedure for model: <modelname>.
or a similar error message.

Actually the setting on the Configuration Parameter’s page Hardware Implementation does not match
the requested value as stated in the text of the error message.

Why does the RTI build process report this error message? How can the problem be solved?

Answer

Tags
Date 2018-05-25
Software Type Implementation Software
Product RTI (Real-Time Interface)
Information Type Frequently Asked Questions
Information Category Troubleshooting
dSPACE Release 2023-A, 2022-B, 2022-A, 2021-B, 2021-A, 2020-B, 2020-A, 2019-B, 2019-A, 2018-B, 2018-A, 2017-B , 2017-A, 2016-B, 2016-A, 2015-B, 2015-A, 2014-B, 2014-A, 2013-B, 2013-A, Prior to 2013-A
Keywords hardware implementation, embedded hardware, device vendor, device type, byte ordering, set_rti, system target file

Drive innovation forward. Always on the pulse of technology development.

Subscribe to our expert knowledge. Learn from our successful project examples. Keep up to date on simulation and validation. Subscribe to/manage dSPACE direct and aerospace & defense now.

Enable form call

At this point, an input form from Click Dimensions is integrated. This enables us to process your newsletter subscription. The form is currently hidden due to your privacy settings for our website.

External input form

By activating the input form, you consent to personal data being transmitted to Click Dimensions within the EU, in the USA, Canada or Australia. More on this in our privacy policy.