The ARM7 board - Revision history

Donald at 13:50, 14 August 2009

2009-08-14T13:50:02Z

Raphael: /* User Applications */

2009-03-23T16:11:53Z

‎User Applications

Raphael: /* User Applications */

2009-03-23T16:11:34Z

‎User Applications

Raphael: /* User Applications */

2009-03-23T16:10:54Z

‎User Applications

@@ Line 1: / Line 1: @@
 ==Overview==
-One Member of the Concept Car's network is an ARM7 board. Due to its 32 bit architecture and higher frequency it provides a much bigger computational power than the AT90CAN128 boards. Thus it is well suited to do all the computation-intensive tasks.
+One Member of the Concept Car's network is an ARM7 board. Due to its 32 bit architecture and higher frequency it provides a much bigger computational power than the AT90CAN128 boards. Thus it is well suited to do all the computation-intensive tasks, like executing complex simulink models.
 ==Signal Flow==

@@ Line 143: / Line 143: @@
 ====User Applications====
-Actually the primary use of the board is for Simulink models execution. The usual flow is Simulink model design, code generation and deployment on the board. For this reason the basic functionality one find when downloading the source code is a "user" '''main.c''' file already coded with Simulink model logic. In order to use simulink models there is no need to alter the basic code provided. Instead, the user is directed to [[Simulink Execution on the ARM7 target|'Executing a Simulink Model']] where information about running Simulink models on the board are provided.
+Actually the primary use of the board is for Simulink models execution. The usual flow is Simulink model design, code generation and deployment on the board. For this reason the basic functionality one find when downloading the source code is a "user" '''main.c''' file already coded with Simulink model logic. In order to use simulink models there is no need to alter the basic code provided. Instead, the user is directed to [[Simulink Execution on the ARM7 target|'Executing a Simulink Model']] where information about running Simulink models on the board is provided.
 Concerning the case where the user is interested in running applications that are not derived from a Simulink model. There are a few things that should be noted. Since the basic structure of the board user code is designed to run Simulink models, the user must first change the '''main.c''' file, which can be found inside '''src/usr'''. The basic idea is an endless loop. Since the user application should never return, inside the main function in '''main.c''' there should be an endless loop calling the user logic every time it is necessary. From this point on, the user is free to create any logic and divide the code in any number of files. As stated above, the files added to '''src/usr''' are automatically compiled and linked together with the '''main.c''' file. All of the functions provided inside '''src/base''' are available to the user. They provide access to the board functionalities.

@@ Line 143: / Line 143: @@
 ====User Applications====
-Actually the primary use of the board is for Simulink models execution. The usual flow is Simulink model design, code generation and deployment on the board. For this reason the basic functionality one find when downloading the source code is a "user" '''main.c''' file already coded with Simulink model logic. In order to use simulink models there is no need to alter the basic code provided. Instead, the user is directed to [[Simulink Execution on the ARM7 target|execute a simulink model]] where information about running Simulink models on the board are provided.
+Actually the primary use of the board is for Simulink models execution. The usual flow is Simulink model design, code generation and deployment on the board. For this reason the basic functionality one find when downloading the source code is a "user" '''main.c''' file already coded with Simulink model logic. In order to use simulink models there is no need to alter the basic code provided. Instead, the user is directed to [[Simulink Execution on the ARM7 target|'Executing a Simulink Model']] where information about running Simulink models on the board are provided.
 Concerning the case where the user is interested in running applications that are not derived from a Simulink model. There are a few things that should be noted. Since the basic structure of the board user code is designed to run Simulink models, the user must first change the '''main.c''' file, which can be found inside '''src/usr'''. The basic idea is an endless loop. Since the user application should never return, inside the main function in '''main.c''' there should be an endless loop calling the user logic every time it is necessary. From this point on, the user is free to create any logic and divide the code in any number of files. As stated above, the files added to '''src/usr''' are automatically compiled and linked together with the '''main.c''' file. All of the functions provided inside '''src/base''' are available to the user. They provide access to the board functionalities.

@@ Line 143: / Line 143: @@
 ====User Applications====
-Actually the primary use of the board is for Simulink models execution. The usual flow is Simulink model design, code generation and deployment on the board. For this reason the basic functionality one find when downloading the source code is a "user" '''main.c''' file already coded with Simulink model logic. In order to use simulink models there is no need to alter the basic code provided. Instead, the user is directed to [[Simulink Execution on the ARM7 target|execute a simulink model]].
+Actually the primary use of the board is for Simulink models execution. The usual flow is Simulink model design, code generation and deployment on the board. For this reason the basic functionality one find when downloading the source code is a "user" '''main.c''' file already coded with Simulink model logic. In order to use simulink models there is no need to alter the basic code provided. Instead, the user is directed to [[Simulink Execution on the ARM7 target|execute a simulink model]] where information about running Simulink models on the board are provided.
 Concerning the case where the user is interested in running applications that are not derived from a Simulink model. There are a few things that should be noted. Since the basic structure of the board user code is designed to run Simulink models, the user must first change the '''main.c''' file, which can be found inside '''src/usr'''. The basic idea is an endless loop. Since the user application should never return, inside the main function in '''main.c''' there should be an endless loop calling the user logic every time it is necessary. From this point on, the user is free to create any logic and divide the code in any number of files. As stated above, the files added to '''src/usr''' are automatically compiled and linked together with the '''main.c''' file. All of the functions provided inside '''src/base''' are available to the user. They provide access to the board functionalities.