MATLAB: Does the “Run on Custom Hardware” app not work with the custom target in R2019b and later

extmodefilesftsimulink codersystemtargettlc

We have a custom target (based on grt.tlc or ert.tlc) that we have been using in older versions of MATLAB for a long time. We always place the .tlc file under

<matlabroot>/rtw/c/

where <matlabroot> is usually located at C:\Program Files\MATLAB\RXXXXx\ on Windows OS.

Now, we upgraded to a more recent version that has the Simulink toolstrip (R2019b and newer). The code generation and build works without issue, but we are having trouble with using External Mode, since every time I try to use the "Run on Custom Hardware" app, the system target file switches back to one of the default targets (grt.tlc or ert.tlc). Why is this?

Best Answer

Placing custom files under <matlabroot> is generally not recommended. Up until R2019a, we did not check the location of custom target .tlc files, so they would work fine even if they were located somewhere under <matlabroot>.

However, in R2019b, we introduced the new Simulink Toolstrip. And it was decided that when launching the "Run on custom hardware" app, it checks the location of the .tlc file specified in the model configuration. If the .tlc file is under <matlabroot>, then only certain MathWorks provided targets are supported, but not custom targets. This is why the app prompts you to switch the target back to grt.tlc.

To work around the issue, place your custom .tlc in a different directory outside of <matlabroot>, and place the directory on your MATLAB path using addpath().

Related Solutions

MATLAB: How to install select callback function in STF

The code:

slConfigUISetVal(hDlg, hSrc, 'ModelReferenceCompliant', 'on');
slConfigUISetEnabled(hDlg, hSrc, 'ModelReferenceCompliant', false);
slConfigUISetVal(hDlg, hSrc, 'ParMdlRefBuildCompliant', 'on');
slConfigUISetEnabled(hDlg, hSrc, 'ParMdlRefBuildCompliant', false);

Should be defined in a separate MATLAB file named custom_select_callback_handler.m that should be present on the MATLAB path:

function custom_select_callback_handler(hDlg, hSrc)
slConfigUISetVal(hDlg, hSrc, 'ModelReferenceCompliant', 'on');
slConfigUISetEnabled(hDlg, hSrc, 'ModelReferenceCompliant', false);
slConfigUISetVal(hDlg, hSrc, 'ParMdlRefBuildCompliant', 'on');
slConfigUISetEnabled(hDlg, hSrc, 'ParMdlRefBuildCompliant', false);

MATLAB: How to add non-UI elements in a custom System Target file (STF) and use the build hooks to pass the variables to the makefile in real-Time Workshop Embedded Coder 5.4 (R2010b)

This can be accomplished using the STF hooks. In the STF, you can create the elements of the custom target's UI using the 'rtwoptions' structure. This is used to create both invisible ('non UI') and visible UI components by specifying the type of the component, default value of the component, and etc. When you create a component using this structure, you can add additional fields such as 'tlcvariable' and 'makevariable'. The field 'tlcvariable' allows you to control the name of this variable as available to the Target Language Compiler whereas 'makevariable' allows you to control the name as available in the make file creation.

For example, following code creates a 'non-UI' component that can be accessed from TLC and make file with their names as specified below:

    rtwoptions(oIdx).prompt         = 'myNonUI';
    rtwoptions(oIdx).type           = 'NonUI';
    rtwoptions(oIdx).default        = 'off';
    rtwoptions(oIdx).tlcvariable    = 'myNonUI';
    rtwoptions(oIdx).makevariable   = 'MYNONUI';

These values can be modified using the STF hooks during the BUILD process.

For example, in the 'after_tlc' hook, you can use the following code to modify the variable after generating the code:

case 'after_tlc'
      % Called just after to invoking TLC Compiler (actual code generation.)
      % Valid arguments at this stage are hookMethod, modelName, and
      % buildArgs
      disp('############Executing After TLC Hook##########');
      set_param(gcs,'myNonUI','on')
      disp('###Done changing the non UI parameter myNonUI');

This variable can then be used in the TMF to create corresponding variable in the 'model.mk' file. There is ZIP file attached that illustrates this with an example.

1. Download and extract the files to a location that is in MATLAB path. Please make sure to add the sub-folders to the path as well.

2. Open the model and build it. You will see that the generated 'pk.mk' file in the code generation folder has the value of modified non-UI variable 'myNonUI'.

Best Answer

Related Solutions

MATLAB: How to install select callback function in STF

MATLAB: How to add non-UI elements in a custom System Target file (STF) and use the build hooks to pass the variables to the makefile in real-Time Workshop Embedded Coder 5.4 (R2010b)

Related Question