[OBC-SA] Code and Config Generation for PikeOS
First iteration:
- Usage of existing Component Architecture as Software Architecture
- Usage of the existing Partition Architecture (1:1 mapping between CA and PA)
- Usage Simons Technical (dreams) Architecture + adapting the wording
Config generation:
- Temporal Partitioning (= synthesis of a time-triggered schedule) <— might be the least trivial task since Schedule synthesis doesnt seem to work properly at the moment
- Spatial Partitioning (simple 1:1 mapping)
Code generation:
- Code Generator from af3.platform.pikeos will be used
- m2m transformation (af3.platform.pikeos ->af.partition) will be performed in the background
(from redmine: issue id 3181, created on 2017-11-20)
- Relations:
- child #3183 (closed)
- child #3184 (closed)
- child #3185 (closed)
- child #3186 (closed)
- child #3187 (closed)
- Uploads:
- obc-sa-plan.pdf
- Partition Architecture Generation
- Code and Config Generation
- OBCSA-TestProject.af3_23 Project that shows the new functionality