LPP » INSTRU » Solar Orbiter LFR » LFR-FSW

Je reprends l'énoncé de l'issue JIRA RPWSWR-150:

Where and how the different SW modes have an impact on the SW definition and execution? (for example, which tasks change their behavior and what are the impacts on the SW dynamics when the mode changes from "NORMAL" to "SBM1"?).

Pour moi tout est décrit dans les paragraphes 5-2 à 5-9 du SDD.

Some explanation should be given on this point. It is also noted that the deadlines of the different task could change from a mode to another, in which case, the schedulability analysis should be performed for all the modes.

Il y a des explications dans le SDD et je pense qu'elles sont suffisantes. J'ai décrit le fonctionnement du mode le plus demandeur, SBM1, avec des chiffres à l'appui au niveau de la charge CPU et des péridoes d'exécution. Je ne vois pas ce que je pourrais ajouter sans devoir y repasser plusieurs jours, ce qui serait très exégaré vu l'enjeu.

Dans fsw_params.h

#define TASK_PRIORITY_SPIQ 5
#define TASK_PRIORITY_LINK 20
#define TASK_PRIORITY_AVGV 25
#define TASK_PRIORITY_HOUS 30
#define TASK_PRIORITY_CWF1 35   // CWF1 and CWF2 are never running together
#define TASK_PRIORITY_CWF2 35   //
#define TASK_PRIORITY_SWBD 37   // SWBD has a lower priority than WFRM, this is to extract the snapshot before sending it
#define TASK_PRIORITY_WFRM 40
#define TASK_PRIORITY_CWF3 40   // there is a printf in this function, be careful with its priority wrt CWF1
#define TASK_PRIORITY_SEND 45
#define TASK_PRIORITY_RECV 50
#define TASK_PRIORITY_ACTN 50
#define TASK_PRIORITY_AVF0 60
#define TASK_PRIORITY_AVF1 70
#define TASK_PRIORITY_PRC0 100
#define TASK_PRIORITY_PRC1 100
#define TASK_PRIORITY_AVF2 110
#define TASK_PRIORITY_PRC2 110
#define TASK_PRIORITY_LOAD 190
#define TASK_PRIORITY_DUMB 200