If I use the VariableClass.TypePrefix property to specify an address qualifier for a variable (e.g., __far), the address qualifier is placed *before* the data type. For example:
__far CAL Vca_DV_tp Vca_DV_fast = {
37 /* 0.145 */ /* P_Ad: LSB: 2^-8 OFF: 0 MIN/MAX: 0 .. 0.99609375 */,
224 /* 7. */ /* P_Kd: LSB: 2^-5 OFF: 0 MIN/MAX: 0 .. 7.96875 */,
72 /* 0.07 */ /* P_Ki: LSB: 2^-10 OFF: 0 MIN/MAX: 0 .. 0.2490234375 */,
192 /* 1.5 */ /* P_Kp: LSB: 2^-7 OFF: 0 MIN/MAX: 0 .. 1.9921875 */
};
However, my compiler does not recognize “__far” at this position as an address qualifier. This is because my compiler expects an address qualifier to be placed *after* the data type, not *before*. For example:
CAL Vca_DV_tp __far Vca_DV_fast = {
37 /* 0.145 */ /* P_Ad: LSB: 2^-8 OFF: 0 MIN/MAX: 0 .. 0.99609375 */,
224 /* 7. */ /* P_Kd: LSB: 2^-5 OFF: 0 MIN/MAX: 0 .. 7.96875 */,
72 /* 0.07 */ /* P_Ki: LSB: 2^-10 OFF: 0 MIN/MAX: 0 .. 0.2490234375 */,
192 /* 1.5 */ /* P_Kp: LSB: 2^-7 OFF: 0 MIN/MAX: 0 .. 1.9921875 */
};
How can I get a type postfix instead of a type prefix?
Date | 2020-06-30 |
Software Type | Production Code Generation Software |
Product | TargetLink |
Information Type | Frequently Asked Questions |
Information Category | Working with |
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 | type prefix, type postfix, address qualifier, __far |
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.