wiki:features
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
wiki:features [2012/10/22 19:56] – pmueller | wiki:features [2022/12/22 08:06] – webmin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Features ====== | + | ~~NOTOC~~ |
- | ===== Overview | + | ====== Features |
- | A statechart | + | A state machine diagram |
- | {{: | + | {{: |
- | An important aspect of statecharts | + | An important aspect of state diagrams |
- | SinelaboreRT was built especially for embedded real-time developers. It focuses on just one task: code generation from state-chart | + | SinelaboreRT was built especially for embedded real-time developers. It focuses on just one task: code generation from state diagrams. A command line tool and a configuration file is all what is needed. |
The generated code is based on nested switch/case and if/ | The generated code is based on nested switch/case and if/ | ||
Line 15: | Line 15: | ||
SinelaboreRT does not force you in any way on how you design your system. Therefore it is no problem to use the generated code in the context of a real-time operating system or within an interrupt service routine or in a foreground / background system. The generation process can be influenced to meet specific needs. | SinelaboreRT does not force you in any way on how you design your system. Therefore it is no problem to use the generated code in the context of a real-time operating system or within an interrupt service routine or in a foreground / background system. The generation process can be influenced to meet specific needs. | ||
- | How does SinelaboreRT work? From a state-chart design file created with the Cadifra UML editor, Enterprise Architect, UModel or Magic Draw the code-generator generates the complete statemachine implementation. For an example design file called oven.cdd the command line looks like java -jar codegen.jar -p CADIFRA -o oven.cdd. As an result files will be generated: | + | How does SinelaboreRT work? From a state-chart design file created with the Cadifra UML editor, Enterprise Architect, UModel or Magic Draw the code-generator generates the complete statemachine implementation. For an example design file called oven.cdd the command line looks like |
+ | |||
+ | <code bash> | ||
+ | java -cp " | ||
+ | </ | ||
+ | |||
+ | As an result files will be generated: | ||
* oven.c implements the state-machine as graphically specified in the oven.cdd file | * oven.c implements the state-machine as graphically specified in the oven.cdd file | ||
Line 25: | Line 32: | ||
- | ===== Supported State Chart Elements ===== | + | ===== Supported State Diagram Design |
- | **Hierarchical state definition**: | + | **Hierarchical state definition**: |
+ | |||
+ | ** Regions **: Regions allow to model parallel behavior within the same state machine diagram. The benefit | ||
**Transitions**: | **Transitions**: | ||
Line 37: | Line 46: | ||
**History States**: | **History States**: | ||
- | **Interactive Test and Simulation**: | + | **Interactive Test and Simulation**: |
+ | |||
+ | {{: | ||
- | {{: | ||
**Debugging / Trace Support**: In the *_dbg.h file two helper functions are provided that are useful for debugging state machines. The function *_GetNameByState(id) returns the name of the state the function *_GetNameByEvent(id) returns the name of an event each identified by its id. Trace statements can be automatically added to the machine. This allows to follow the flow of events. | **Debugging / Trace Support**: In the *_dbg.h file two helper functions are provided that are useful for debugging state machines. The function *_GetNameByState(id) returns the name of the state the function *_GetNameByEvent(id) returns the name of an event each identified by its id. Trace statements can be automatically added to the machine. This allows to follow the flow of events. | ||
- | **Integrated State-Diagram Editor**: Using the command line flag ‘-E’ brings up the integrated state diagram editor. It provides an efficient tree based entry method. The graphical representation is created automatically. So you can fully focus on the modeling task. | + | **Integrated State-Diagram Editor**: Using the command line flag '' |
- | [[wiki: | + | [[wiki: |
wiki/features.txt · Last modified: 2023/03/08 10:14 by webmin