MATLAB: Do I get an error when using the Lookup Table blocks with the GetSet custom storage class in Real-Time Workshop Embedded Coder 5.5 (R2010a)

Embedded Coder

I am using the "Direct Lookup Table (n-D)" and "Lookup Table Dynamic" blocks with the GetSet custom storage class in my model. When I try to generate code from the model, I get the following error:

 Error: Real-Time Workshop Error: Parameter 'Param3' is not addressable because of its custom storage class.

Best Answer

The Lookup Table blocks are currently incompatible with the GetSet custom storage class in Real-Time Workshop Embedded Coder 5.5 (R2010a).

To work around the issue, please follow the workaround suggested in our documentation here:

 <http://www.mathworks.com/help/releases/R2010a/toolbox/ecoder/ug/f29488.html#bsfvvot-1>

Related Solutions

MATLAB: How to specify a different header file name for each Simulink data object when using the ExportToFile custom storage class with a FlatStructure type in Real-Time Workshop Embedded Coder 4.0 (R14)

The ability to specify the header file name as an instance specific parameter is not available when using the ExportToFile custom storage class with a FlatStructure type in Real-Time Workshop Embedded Coder.

To workaround this issue, create a Custom Storage Class with a storage class type of Other and define the storage class using the Target Language Compiler. Note you will need to use the advanced mode of the CSCDESIGNER:

cscdesigner -advanced

Please navigate to the following location within the Real-Time Workshop Embedded Coder documentation for more information:

 Real-Time Workshop Embedded Coder > Custom Storage Classes

MATLAB: Does changing the inline parameters Storage class from SimulinkGlobal (Auto) to ExportedGlobal cause the build process to slow down dramatically using the Real-Time Workshop

This bug has been fixed for Release 14 (R14). For previous releases, please read below for any possible workarounds:

This has been verified as a bug in the Real-Time Workshop 4.1 (R12.1) and later versions in the way that the Real-Time Workshop handles code generation for Global (tunable) parameters that are stored as ExportedGlobal.

There are currently no known workarounds.

Best Answer

Related Solutions

MATLAB: How to specify a different header file name for each Simulink data object when using the ExportToFile custom storage class with a FlatStructure type in Real-Time Workshop Embedded Coder 4.0 (R14)

MATLAB: Does changing the inline parameters Storage class from SimulinkGlobal (Auto) to ExportedGlobal cause the build process to slow down dramatically using the Real-Time Workshop

Related Question