Real-Time Workshop Release Notes

Upgrading from an Earlier Release

This section describes the upgrade issues involved in moving from the Real-Time Workshop 3.0 (Release 11.0) to the Real-Time Workshop 4.0.

Column-Major Matrix Ordering

The Real-Time Workshop now uses column-major ordering for two-dimensional signal and parameter data. In previous releases, the ordering was row-major.

If your hand-written code interfaces to such signals or parameters via ExportedGlobal, ImportedExtern, or ImportedExternPointer declarations, make sure to review any code that relies on row-major ordering, and make appropriate revisions.

Including Generated Files

Filename extensions for certain generated files have changed. If your application code uses #include statements to include the Real-Time Workshop generated files (such as model.prm), you may need to modify these statements. See Filename Extensions for Generated Files.

Updating Release 11 Custom Targets

If you have created custom targets for the Real-Time Workshop under Release 11, you must update your custom system target files and template makefiles to create and utilize the build directory. See matlabroot/rtw/c/grt for examples.

To update a Release 11 target:

1. Add the following to your system target file.

• /%
  BEGIN_RTW_OPTIONS
  ...
  rtwgensettings.BuildDirSuffix = '_grt_rtw';
  END_RTW_OPTIONS 
  %/ 
  

2. Add ".." to the INCLUDES rule in your template makefile. The following example is from grt_lcc.tmf.

• INCLUDES = -I. -I.. $(MATLAB_INCLUDES) $(USER_INCLUDES)
  

1. The first -I. gets files from the build directory, and the second -I.. gets files (e.g., user written S-functions) from the current working directory.

   Conceptually, think of the current directory and the build directory as the same (as it was in Release 11). The current working directory contains items like user written S-functions. The reason ".." must be added to the INCLUDES rule is that make is invoked in the build directory (i.e., the current directory was temporarily moved).

3. Place the generated executable in your current working directory. The following example is from grt_lcc.tmf.

• PROGRAM = ../$(MODEL).exe
  $(PROGRAM) : $(OBJS) $(RTWLIB)
      $(LD) $(LDFLAGS) -o $@ $(LINK_OBJS) $(RTWLIB) $(LIBS)
  

hilite_system Replaces locate_system

If you use the locate_system command, in MATLAB programs for tracing the Real-Time Workshop system/block identification tags, you should use hilite_system instead. See hilite_system and Code Tracing.

TLC Compatibility Issues

In bringing Target Language Compiler files from Release 11 to Release 12, the following changes may affect your TLC code base:

• Nested evaluations are no longer supported. Expressions such as

• %<LibBlockParameterValue(%<myVariable>,"", "", "")>
  

• are no longer supported. You will have to convert these expressions into equivalent non-nested expressions.

• Aliases are no longer automatically created for Parameter blocks while reading in the Real-Time Workshop files.
• You cannot change the contents of a "Default" record after it has been created. In the previous TLC, you could change a "Default" record and see the change in all the records that inherited from that default record.
• The %codeblock and %endcodeblock constructs are no longer supported.
• %defines and macro constructs are no longer supported.
• Use of line continuation characters (... and \) are not allowed inside of strings. Also, to place a double quote (") character inside a string, you must use \". Previously, the Target Language Compiler allowed you to use """ to get a double quote in a string.
• Semantics have been formalized to %include files in different contexts (e.g., from generate files, inside of %with blocks, etc.) %include statements are now treated as if they were read in from the global scope.
• The previous the Target Language Compiler had the ability to split function definitions (and other directives) across include file boundaries (e.g., you could start a %function in one file and %include a file that had the %endfunction). This no longer works.
• Nested functions are no longer allowed. For example,

• %function foo ()
    %function bar ()
    %endfunction
  %endfunction
  

• Built-in functions cannot be undefined via %undef. It is possible to undefine built in values, but this practice is not encouraged.
• Recursive records are no longer allowed. For example,

• Record1     {
    Val 2
    RefRecord2
  }
  Record2     {
    Val3
    RefRecord1
  }
  

• Semantics of the EXISTS function have changed. In the previous release of TLC, EXISTS(var) would check if the variable represented by the string value in var existed. In the current release of TLC, EXISTS(var) checks to see if var exists or not.

• To emulate the behavior of EXISTS in the previous release, replace

  • EXISTS(var) 
    

with

• EXISTS("%<var>")
  

Real-Time Workshop 4.0 Release Notes

Known Software and Documentation Problems