Skip to content
GitLab
Commit c055c416 authored by Sergey Zverlov's avatar Sergey Zverlov
Browse files

New documentation for Efficient Deployment and Manual Deployment 

refs 1364
parent b172a05a
Hide whitespace changes
Inline Side-by-side
org.fortiss.af3.rcp.application/trunk/html/efficient_deployment.html 0 → 100644
View file @ c055c416
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Efficient Deployment in AutoFocus 3</title>
</head>
<body>
<h2><u><font color="#336699">Deployment Synthesis</font></u></h2>
AutoFOCUS 3 supports an approach of generating an efficient deployment of logical components to a plattform architecture
concerning local memory constraints of cores and safety constraints of tasks.
<br><br>
<img src="./pictures/EDeployment.Start.png">
<br><br>
Select the platform architecture (there can be more than one) on which the logical components should be deployed and use the filter to select the logical components which should be included in the deployment. Press the OK button and a scheduling model is created.
<br><br>
<img src="./pictures/EDeployment.Filter.png">
<br><br>
In the Deployment Editor Tab one can select several parameters for the deployment generation:
<ul>
<li>Desired maximum E2E-Latency, so the SMT solver only searches solutions which satisfy this constraint.</li>
<li>Time-out for the SMT Solver (in sec), which represents the time how long the SMT solver is allowed to search for a solution</li>
<li>Optimized Solution, means that the solver searches for several optimized solutions.</li>
<li>Safety Integrity Level, which means that SIL of tasks have to be taken into account.</li>
</ul>
After your are finished setting up the parameters, press Generate Deployment.
<br><br>
<img src="./pictures/EDeployment.Params.png">
<br><br>
After the deployments have been calculated you can examine them in the 3D Editor Tab within a 3-dimensional coordinate system, whereby one can use color as the fourth dimension. On the right side you can do some adjustments, such as defining which parameter is assigned to which axis.
By rolling with the mouse over one of the deployments the data related to the deployment appears. After finding the deployment which suits one the best one can push the the Generate Deployment button. A generated Deployment will be added to your model.
<br><br>
<img src="./pictures/EDeployment.Results.png">
<br><br>
In case the design space of possible deployments is large, one can limit it by using the concept of planes. One can set up planes on the right side of the 3D Editor.
<br><br>
<img src="./pictures/EDeployment.Planes.png">
<br><br>
The generated deployment can be adapted manually afterwards.
</body>
</html>
\ No newline at end of file
org.fortiss.af3.rcp.application/trunk/html/manual_deployment.html 0 → 100644
View file @ c055c416
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Defining a deployment using AutoFOCUS3 (AF3)</title>
</head>
<body>
<h2><u><font color="#336699">Defining a Deployment</font></u></h2>
AutoFOCUS supports deployment of component architectures to platform architectures.
You can add a deployment to your model using the context menu. The deployment is automatically linked to the first component architecture and the first platform architecture found in your model.
<br><br>
<img src="./pictures/MDeployment.Add.png">
<br><br>
The editor for a deployment consists of set of different views:
<ul>
<li>Component-ECU Mapping</li>
<li>Sensor/Actuator-Port Mapping</li>
<li>Tranceiver-Port Mapping</li>
<li>Raw Mappings</li>
<li>Resource Requirements Table</li>
</ul>
<br><br>
<h3><u><font color="#336699">Component-ECU Mapping</font></u></h3>
In the comfortable editor, you can drag and drop the components from the tree on the left-hand side onto the execution units displayed in the right-hand side. You can undeploy the components using the context menu on the left-hand view.
<br><br>
<img src="./pictures/MDeployment.CMP.ECU.png">
<h3><u><font color="#336699">Sensor/Actuator-Port Mapping</font></u></h3>
In this editor one can map the in-/output ports of the logical components to the sensors and actuators of the ECUs.
<br><br>
<img src="./pictures/MDeployment.Sens.Act.png">
<h3><u><font color="#336699">Tranceiver-Port Mapping</font></u></h3>
In this editor one can map the in-/output ports of the logical components to the tranceiver ports which connect the ECUs with the bus. This mapping demonstrates the informations exchange between the ECUs over the bus.
<br><br>
<img src="./pictures/MDeployment.Transceiver.png">
<h3><u><font color="#336699">Raw Mapping</font></u></h3>
In this editor one can map the in/output ports of logical components to any actuators/sensors/tranceivers of the platform architecture.
<br><br>
<img src="./pictures/MDeployment.Raw.png">
<h3><u><font color="#336699">Resource Requirements Table</font></u></h3>
In this editor one can add to each component a WCET and the amount of memory which it consumes.
<br><br>
<img src="./pictures/MDeployment.Resource.png">
</body>
</html>
\ No newline at end of file
org.fortiss.af3.rcp.application/trunk/toc.xml
View file @ c055c416
......@@ -54,9 +54,11 @@
<topic label="Code generation, deployment and scheduling synthesis">
<topic href="html/code_generation.html" label="Code Generation (Component, Deployment)">
</topic>
<topic href="html/deployment.html" label="Deployment">
</topic>
<topic href="html/scheduling.html" label="Scheduling Synthesis">
</topic>
<topic href="html/efficient_deployment.html" label="Efficient Deployment">
</topic>
<topic href="html/manual_deployment.html" label="Manual Deployment">
</topic>
</topic>
<topic label="Testing and formal verification">
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment