Simulink Execution on the ARM7 target - Revision history

Raphael at 08:53, 15 April 2009

2009-04-15T08:53:24Z

2009-04-15T08:49:37Z

2009-03-18T21:13:53Z

2009-03-18T21:08:29Z

2009-03-18T21:06:41Z

@@ Line 38: / Line 38: @@
 ===SimulinkTarget's Work-flow===
-SimulinkTarget takes a simulink model and generates code that only needs very limited user interference (basically the user must provide the information specified above). Not all code needs to be generated, some source files can be copied. The link below leads to a description of the complete tool workflow.
+SimulinkTarget takes a simulink model and generates code that only needs very limited user interference (basically the user must provide the information specified above). Not all code needs to be generated, some source files can be copied.
-[[Simulink2ARM7‎]]
+# Create (or load) a project configuration file
-# Copy simulink model code (generated by Embedded Coder) to target location
+A detailed description of the complete tool workflow is available in [[Simulink2ARM7‎]].
-# Copy non model-specific source files to target location
-# Generate glue code
-# ''(From here on user interferes)'' Edit some files to bind the model to the platform
-# Cross-compile code with arm-elf-toolchain
-# Transfer code to the target
 ===Preconditions for Successful Code Generations===

@@ Line 38: / Line 38: @@
 ===SimulinkTarget's Work-flow===
-SimulinkTarget takes a simulink model and generates code that only needs very limited user interference (basically the user must provide the information specified above). Not all code needs to be generated, some source files can be copied.
+SimulinkTarget takes a simulink model and generates code that only needs very limited user interference (basically the user must provide the information specified above). Not all code needs to be generated, some source files can be copied. The link below leads to a description of the complete tool workflow.
 # Copy simulink model code (generated by Embedded Coder) to target location

@@ Line 27: / Line 27: @@
 ==Automated Model Execution==
-SimulinkTarget is a tool that provides semi-automatic support for running a simulink model on the ARM7 board. Basically it generates code that can be cross-compiled and stored on a SD card to be loaded and launched by the ARM7 bootloader. Since the simulink model does not (and can not) provide all information needed for its execution on a specific target in a specific environment (it is a platform independent model, '''PIM'''), some information needs to be given by the user to make it a platform specific model ('''PSM''').
+SimulinkTarget is a tool that provides semi-automatic support for running a simulink model on the [[The ARM7 board|ARM7 board]]. Basically it generates code that can be cross-compiled and stored on a SD card to be loaded and launched by the ARM7 bootloader. Since the simulink model does not (and can not) provide all information needed for its execution on a specific target in a specific environment (it is a platform independent model, '''PIM'''), some information needs to be given by the user to make it a platform specific model ('''PSM''').
 * Model-inherent information:
 ** The names of the two functions (step & initialize)

@@ Line 44: / Line 44: @@
 # Generate glue code
 # ''(From here on user interferes)'' Edit some files to bind the model to the platform
-# Compile code
+# Cross-compile code with arm-elf-toolchain
 # Transfer code to the target

@@ Line 8: / Line 8: @@
 The Embedded Coder produces code whose execution is triggered by 2 functions:
-. an initialization function, called once before model execution
+# an initialization function, called once before model execution
-. a step function, called in a regular interval to update the model
+# a step function, called in a regular interval to update the model
 Interaction with the environment is done via the model's ports. The coder maps these to two structs, one for the inports and one for the outports.