Skip to Content
Last modified by Alexander Schulz-Rosengarten on 2023/09/11 16:17
From version 22.1
edited by cmot
on 2014/02/11 11:11
Change comment: There is no comment for this version
To version 17.1
edited by cmot
on 2014/02/10 21:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,7 +10,7 @@
10 10  
11 11  3. Generate C Code.
12 12  
13 -We will use a simple example here in order to illustrate the process. Please refer to the SCCharts superpage for the [[project status>>doc:SCCharts]] and known limitations.
13 +We will use a simple example here in order to illustrate the process. It should be straightforward to use these instructions in order to compile a more advanced SCChart. Note that there are known minor bugs in the current nightly build that will be fixed in the next release of KIELER 0.10.0. These bugs might in some cases prevent you from compiling more elaborate examples.
14 14  
15 15  
16 16  
... ... @@ -60,8 +60,6 @@
60 60  
61 61  [[image:attach:kieler09.png]]
62 62  
63 -SCT is a textual description language for SCCharts. Due to space limitations SCT is not documented in the PLDI paper, but examples can be found here. Also the code completion functionality of the textual editor for SCT is very helpful. It can be invoked by pressing <Ctrl> + <Space>. It will list all syntactically possible input according to the SCT/SCCharts meta model.
64 -
65 65  The textual SCCharts Xtext based editor (for *.sct files) will automatically be opened:
66 66  
67 67  [[image:attach:kieler10.png]]
... ... @@ -114,42 +114,54 @@
114 114  
115 115  [[image:attach:kieler14.png]]
116 116  
117 -Now generate the Sequentially Constructive Graph (SCG) from the normalized form. You do this also in the context menu of the Project Explorer by selecting the *.normalized.sct and choosing Generate SCG. When selecting the abo.normalized.scg file the SCG diagram will be automatically synthesized (you may also want to re-arrange the KLigD view by dragging in to the right side again).
115 +Now generate the Sequentially Constructive Graph (SCG) from the normalized form. You do this also in the context menu of the Project Explorer by selecting the *.normalized.sct and choosing Generate SCG:
118 118  
119 -[[image:attach:kieler15.png]][[image:attach:kieler16.png]]
117 +[[image:attach:kieler15.png]]
120 120  
121 -
119 +When selecting the abo.normalized.scg file the SCG diagram will be automatically synthesized (you may also want to re-arrange the KLigD view by dragging in to the right side again):
122 122  
123 -You can now populate the SCG automatically with dependency data. Choose Transform SCG -> SCG with Dependency Data from the context menu (left side). This will result in the following SCG (right side).
121 +[[image:attach:kieler16.png]]
124 124  
125 -[[image:attach:kieler17.png]][[image:attach:kieler18.png]]
123 +You can now populate the SCG automatically with dependency data. Choose Transform SCG -> SCG with Dependency Data from the context menu:
126 126  
127 -
125 +[[image:attach:kieler17.png]]
128 128  
129 -Now populate the SCG with basic block information (left side). The SCG with calculated basic blocks will look like this (right side).
127 +This will result in the following SCG:
130 130  
131 -[[image:attach:kieler19.png]][[image:attach:kieler20.png]]
129 +[[image:attach:kieler18.png]]
132 132  
133 -
131 +Now populate the SCG with basic block information:
134 134  
135 -The next step in compilation is the (more fine grained) calculate of scheduling blocks (left side). The populated SCG with scheduling information looks like this (right side).
133 +[[image:attach:kieler19.png]]
136 136  
137 -[[image:attach:kieler21.png]][[image:attach:kieler22.png]]
135 +The SCG with calculated basic blocks will look like this:
138 138  
139 -
137 +[[image:attach:kieler20.png]]
140 140  
141 -The SCG is now ready to be sequentialized. A primitive scheduler currently is included in KIELER but more elaborate ones are already in the pipe line (left side). The sequentialized SCG looks like this (right side).
139 +The next step in compilation is the (more fine grained) calculate of scheduling blocks:
142 142  
143 -[[image:attach:kieler23.png]][[image:attach:kieler24.png]]
141 +[[image:attach:kieler21.png]]
144 144  
145 -
143 +The populated SCG with scheduling information looks like this:
146 146  
147 -From here its only a short hop to C code. Transform the sequentialized SCG into an S Tick Function (left side). When opening the S file (abo.normalized.seq.s) this already is very c like code (right side).
145 +[[image:attach:kieler22.png]]
148 148  
149 -[[image:attach:kieler25.png]][[image:attach:kieler26.png]]
147 +The SCG is now ready to be sequentialized. A primitive scheduler currently is included in KIELER but more elaborate ones are already in the pipe line:
150 150  
151 -
149 +[[image:attach:kieler23.png]]
152 152  
151 +The sequentialized SCG looks like this:
152 +
153 +[[image:attach:kieler24.png]]
154 +
155 +From here its only a short hop to C code. Transform the sequentialized SCG into an S Tick Function:
156 +
157 +[[image:attach:kieler25.png]]
158 +
159 +When opening the S file (abo.normalized.seq.s) this already is very c like code:
160 +
161 +[[image:attach:kieler26.png]]
162 +
153 153  Selecting Generate SC will produce a C file:
154 154  
155 155  [[image:attach:kieler27.png]][[image:attach:kieler28.png]]
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -8651742
1 +8651731
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651742/PLDI'14 Artifact on SCCharts
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651731/PLDI'14 Artifact on SCCharts