User manual MATLAB REAL-TIME WORKSHOP RELEASE NOTES

[. . . ] Real-Time Workshop® Release Notes How to Contact The MathWorks Web Newsgroup www. mathworks. com/contact_TS. html Technical Support www. mathworks. com comp. soft-sys. matlab suggest@mathworks. com bugs@mathworks. com doc@mathworks. com service@mathworks. com info@mathworks. com Product enhancement suggestions Bug reports Documentation error reports Order status, license renewals, passcodes Sales, pricing, and general information 508-647-7000 (Phone) 508-647-7001 (Fax) The MathWorks, Inc. 3 Apple Hill Drive Natick, MA 01760-2098 For contact information about worldwide offices, see the MathWorks Web site. Real-Time Workshop® Release Notes © COPYRIGHT 2000­2010 by The MathWorks, Inc. The software described in this document is furnished under a license agreement. The software may be used or copied only under the terms of the license agreement. [. . . ] When you open a preexisting model that has not been saved using the current version of Simulink, and select the Hardware Implementation pane of the Configuration Parameters dialog box, the following set of controls appears: 135 Real-Time Workshop® Release Notes All but one of the parameters below the Device type menu are grayed out. This is because these characteristics have been preset for the default target (32-bit Generic), as well as for several dozen known target processors that you can select from that menu. The Real-Time Workshop build process only reads existing hook files when a model created by the V5. 0 (R13) Real-Time Workshop software is built for the first time in V6. 0 (R14) without your having first specified characteristics of the Current code generation execution hardware device on the Hardware Implementation pane. If you build a model in this underspecified state, the Real-Time Workshop software scans the current directory, then the MATLAB path, for an existing hook file with the name target_rtw_info_hook. m. If the file is found, its instructions override the defaults in that section. You can subsequently specify any characteristic freely. If at any point prior to building the target code you specify Current code generation execution hardware device, the Real-Time Workshop build process ignores hook files , as hardware characteristics are now configured. When you open a preexisting (before V6. 0) model, the Hardware Implementationpane displays a Configure current execution hardware device button. This button disappears after you press it once. When code is generated (Ctrl+B) for the target the model specifies, · If the target has a hook file, and the Configure current execution hardware device button has not yet been pressed, 136 Version 6. 0 (R14) Real-Time Workshop® Software - The hook file is executed and configures the fields specifying current code generation execution hardware device. A warning is issued to the user that the hook file was used. The Configure current execution hardware device button on the Hardware configuration dialog box is permanently removed for that model (assuming that you save the model). · If the target has a hook file and the Configure current execution hardware device button has been pressed (removing it), - Code is generated for the target using the hardware characteristics for the current code generation execution hardware device (which can default to those of the final embedded hardware device). The hook file for the target is ignored, and is from now on. A warning is issued that a hook file exists but was not used. · If the target has no hook file, no message to that effect is issued, and the current code generation execution hardware device, if left unspecified, defaults to MATLAB host computer for target device information. A message is displayed during code generation to indicate this default. This second group of Hardware Implementation pane controls governs how hardware characteristics are handled in generated code. They do not appear unless the Real-Time Workshop product is installed. Their appearance varies depending on whether hardware configuration characteristics were previously specified for the model or not. If they were not, you see a button (as illustrated in the first of the two preceding figures) labeled Configure current execution hardware device. This button never again appears for this model once code has been generated and the model has been saved. When you click the Configure current execution hardware device button, it is replaced by a check box labeled None. This box is selected by default, as shown in the following figure. 137 Real-Time Workshop® Release Notes If you deselect this box, controls appear for that section that are identical to the controls for the Embedded Hardware section above, as shown in the next figure. [. . . ] · 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. [. . . ]