Difference between revisions of "Simulink2ARM7"
(→Load the RTW generated code) |
(→Select the base stub code used) |
||
Line 46: | Line 46: | ||
==Select the base stub code used== | ==Select the base stub code used== | ||
+ | |||
+ | The stub code contains both the base system functionality and the main system loop. The main system loop is responsible for the execution of the model. The main loop execution is described in [[Simulink Execution on the ARM7 target]]. | ||
[[image:simulinktarget06.jpg]] | [[image:simulinktarget06.jpg]] | ||
+ | |||
+ | |||
+ | The screenshot above presents the user two options. One of them is to use the code provided with the SimulinkTarget tool. In this case the code used is related to a specific SVN release and will contain a version number. The user must be sure to use compatible combinations of software, that is, bootloader version should be the same as the stub code used with the SimulinkTarget. | ||
+ | |||
+ | In case the user has a copy of a newer code that either does not match the version provided by the tool or that is not yet a release, it is possible to select the second option. If this option is chosen, the user must provide the address of the folder containing the code. | ||
[[image:simulinktarget07.jpg]] | [[image:simulinktarget07.jpg]] |
Revision as of 13:18, 15 April 2009
Contents
Overview
This page describes the user interaction with the SimulinkTarget tool. Every step needed in order to get from Simulink Model to the Executable file is described in this page. The first step before getting the model to run in the ARM7 Board is to generate the code that implements the Simulink Model. This process is described here Simulink settings for generating code.
Create (or load) a project configuration file
The SimulinkTarget tool creates a configuration file where all the decisions made during the conversion process are saved. Doing so enables the user to load the configuration file and avoids the overhead of going through all of the steps every time new code is generated. The first step is to either load or create a configuration file.
After loading/creating a configuration file, new tabs are enabled and the user may proceed to the next steps.
As the user can easily note, the tab Simulink Model has been enabled and is intuitively the next step to be taken.
Load the simulink model
The tool needs to load a Simulink Model in order to obtain model specific information, such as port names, model name, etc. After parsing the model necessary information is collected and the tool can go further. The first image shows the select model screen.
The user then selects the MDL file that contains the model that will be executed on the ARM7 platform.
Once again after completing the required steps inside the tab, new tabs are enabled and the user can continue to enter information required to achieve the final executable file.
Load the RTW generated code
In order to complete this step, the user must first execute the Simulink settings for generating code and generate code with the Matlab Simulink Real-Time Workshop.
After the folder containing the RTW generated code is specified, the tool will merge the model code together with the base system code. The base system code is selected in the next step.
Select the base stub code used
The stub code contains both the base system functionality and the main system loop. The main system loop is responsible for the execution of the model. The main loop execution is described in Simulink Execution on the ARM7 target.
The screenshot above presents the user two options. One of them is to use the code provided with the SimulinkTarget tool. In this case the code used is related to a specific SVN release and will contain a version number. The user must be sure to use compatible combinations of software, that is, bootloader version should be the same as the stub code used with the SimulinkTarget.
In case the user has a copy of a newer code that either does not match the version provided by the tool or that is not yet a release, it is possible to select the second option. If this option is chosen, the user must provide the address of the folder containing the code.