SESAME employs event driven cosimulation to simulate embedded systems. SESAME follows the Y-Chart methodology for embedded system development. Y-Chart recognizes distinct application, architecture and virtual layers with in an embedded system simulation. This means applications are simulated separately from the architecture. Applications generate event traces which describe the actions of the running application. These event traces are mapped on to an architecture. The virtual layer is also some times referred to as the synchronization layer because it synchronizes traces events of different application processes before they reach the architecture. However, it is also responsible for scheduling and trace rewriting. The architecture simulation responds to application events by simulating their timing consequences. When the simulation is finished the user can analyze the measured simulation results and use this information to improved the application simulation, the architecture simulation, the mapping or all three. Thus the user runs through iterations of simulating and refining the simulation models until satisfied with the embedded systems performance.
It allows you to create new SESAME projects, edit the structure of application and architecture simulations and their source code and generates default templates for new application and architecture classes. The YMLEditor also allows you to edit the mapping between the application and architecture, automatically generate the virtual layer based on the supplied mapping and architecture templates and build and run SESAME simulations from the convenience of a single application.
The remainder of this document describes how to use the YMLEditor to accomplish these tasks. Starting from the section entitled Project Management this documentation will follow a simple example co-simulation using the YMLEditor.
|Notes will be displayed in a box such as this one. These notes provide additional information about the usage of the YMLEditor and may explain some of the nuances of the interface. A "Technical Note" is used to explain details not necessary for normal use of the YMLEditor. Technical notes can be safely ignored by most users.|