Project

General

Profile

Bug #1745

Corrections dans SDD pour relivraison DATAPACK R3++ updated

Added by bruno katra almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
07/07/2017
Due date:
% Done:

0%

Estimated time:
revision:
r0

Description

Ci-dessous l'ensemble des bugs à corriger dans le SDD pour DP R3++ updated attendu pour fin Aout 2017:

- https://jira-lesia.obspm.fr/browse/RPWSWR-150 : SDD to be updated with additional information on dynamic architecture (tasks priorities, periods, deadlines, etc). Voir le détail demandé dans JIRA. Priorité des taches ajouté au SDD + JIRA commenté avec les explications de Paul (mail + téléphone 28/09/2017)

- https://jira-lesia.obspm.fr/browse/RPWSWR-615 :

1) I cannot find the memory map in SDD. Can you please clarify?
Please note that, as mentioned in section 4.4 of SUM 1.4: "Physical mapping of SW onto subsystem HW is described in SDD 1.3". > Bruno le fera, lié à https://jira-lesia.obspm.fr/browse/RPWSWR-671 --> FAIT dans SUM 1.5

2) Additional remark: once the memory map is added, please update chapter 5.1 of RPW-MEB-LFR-RPT-00095 issue 2.3 * > Bruno le fera, lié à https://jira-lesia.obspm.fr/browse/RPWSWR-671* --> FAIT

3) SDD to be updated with CPU and Memory margins for V3.2.0.15 FAIT dans SDD 1.4

4) Watchdog requirements are to be written (currently they are empty in SDD) FAIT DANS SDD 1.4

5) Typo: the title (in blue colour) of one of the SDD requirements is repeated. Please correct --> FAIT + nombreuses corrections sur les numéros de req SRS

NON DEMANDE :

- SDD : Mettre les refs vers RFD + SVerR pour les reqs EDAC : Bruno FAIT

History

#1 Updated by bruno katra almost 4 years ago

  • Description updated (diff)

#2 Updated by bruno katra almost 4 years ago

  • Description updated (diff)

#3 Updated by bruno katra almost 4 years ago

  • Description updated (diff)

#4 Updated by bruno katra almost 4 years ago

  • Description updated (diff)

#5 Updated by bruno katra almost 4 years ago

  • Description updated (diff)

#6 Updated by bruno katra almost 4 years ago

  • Project changed from Solar Orbiter LFR to LFR-FSW

#7 Updated by bruno katra almost 4 years ago

  • File RPW-MEB-LFR-SDD-00039-1-4_LFR_Software_Design_Document.odt added
  • Description updated (diff)
  • Status changed from New to In Progress
  • Priority changed from High to Urgent

Je joins la version 1.4 du SDD, il s'agit du SDD livré par Paul (1.3) mis à jour avec les points 4 + 5 et une partie du point 3 + corrections d'erreurs de numérotations entre SDD et SRS.
Paul, il faudrait partir de cette version pour ajouter tes modifs demandés par https://jira-lesia.obspm.fr/browse/RPWSWR-150 et https://jira-lesia.obspm.fr/browse/RPWSWR-615.

#8 Updated by bruno katra almost 4 years ago

  • Description updated (diff)

#9 Updated by bruno katra almost 4 years ago

  • Description updated (diff)

#10 Updated by bruno katra over 3 years ago

  • Description updated (diff)

#11 Updated by bruno katra over 3 years ago

  • Description updated (diff)

#12 Updated by bruno katra over 3 years ago

  • File deleted (RPW-MEB-LFR-SDD-00039-1-4_LFR_Software_Design_Document.odt)

#14 Updated by paul leroy over 3 years ago

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.

#15 Updated by paul leroy over 3 years ago

  • Assignee changed from paul leroy to bruno katra

#16 Updated by paul leroy over 3 years ago

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

#17 Updated by bruno katra over 3 years ago

  • Description updated (diff)

#18 Updated by bruno katra over 3 years ago

  • Status changed from In Progress to Closed

Tout a été pris en compte dans datapack R3++ et JIRAs commentés

Also available in: Atom PDF