Project

General

Profile

Actions

Bug #629

closed

Lost TM_LFR_HK with timegen

Added by Veronique bouzid about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
16/02/2016
Due date:
% Done:

0%

Estimated time:
revision:
r0

Description

Je viens d'ecrire un petit test (/opt/VALIDATION_R3/my_test_mode.py qui ne dure que 6 secondes pour verifier si je peux reproduire la perte de HK. C'est le cas.

1- Lancement du script Timegen + set_time
2 on envoie une TC enter-mode en standby
3- on envoie une TC entre-mode en normal
4 on attend 5s (utilisation de la fct soc.wait(5)

les logs montrent la perte de JK
2016 2 16 09:59:50:426 TM_LFR_TC_EXE_NOT_EXECUTABLE time = 0x 1e55af94 3774
2016 2 16 09:59:50:429 TM_LFR_TC_EXE_SUCCESS time = 0x 1e55af94 3dbd
2016 2 16 09:59:50:570 TM_LFR_HK time = 0x 1e55af94 629a
2016 2 16 09:59:51:571 TM_LFR_HK time = 0x 1e55af95 629a
2016 2 16 09:59:52:571 TM_LFR_HK time = 0x 1e55af97 629a
2016 2 16 09:59:53:570 TM_LFR_HK time = 0x 1e55af98 6299
2016 2 16 09:59:54:570 TM_LFR_HK time = 0x 1e55af99 6299
2016 2 16 09:59:55:232 TM_LFR_SCIENCE_NORMAL_BP1_F0 time = 0x 1e55af95 1
2016 2 16 09:59:55:256 TM_LFR_SCIENCE_NORMAL_BP1_F1 time = 0x 1e55af95 1
2016 2 16 09:59:55:268 TM_LFR_SCIENCE_NORMAL_BP1_F2 time = 0x 1e55af95 e6

J'ai enregistré le format CSW qui me permet de verifier le sequence_cnt des HK
2016 2 16 09:59:50:426, 32, 2, 0, 0, 12, 193, 192, 0, 0, 19, 16, 1, 8, 254, 30, 85, 175, 148, 55, 116, 28, 204, 0, 0, 164, 16, 181, 41, 13, 81
2016 2 16 09:59:50:429, 32, 2, 0, 0, 12, 193, 192, 1, 0, 13, 16, 1, 7, 254, 30, 85, 175, 148, 61, 189, 28, 204, 0, 0

--> 3 25 indique TM_LFR_HK et le SEQUENCE_CNT est en gras et correct
2016 2 16 09:59:50:570, 32, 2, 0, 0, 12, 196, 192, 7, 0, 129, 16, 3, 25, 0, 30, 85, 175, 148, 98, 154, 1, 29, 81, 3, 0, 0, 22, 1, 1, 89, ....
2016 2 16 09:59:51:571, 32, 2, 0, 0, 12, 196, 192, 8, 0, 129, 16, 3, 25, 0, 30, 85, 175, 149, 98, 154, 1, 29, 81, 3, 0, 0, 22, 1, 1, 89, ....
2016 2 16 09:59:52:571, 32, 2, 0, 0, 12, 196, 192, 9, 0, 129, 16, 3, 25, 0, 30, 85, 175, 151, 98, 154, 1, 29, 81, 3, 0, 0, 22, 1, 1, 89,
2016 2 16 09:59:53:570, 32, 2, 0, 0, 12, 196, 192, 10, 0, 129, 16, 3, 25, 0, 30, 85, 175, 152, 98, 153, 1, 29, 81, 3, 0, 0, 22, 1, 1, 89,

--> Il n'y a pas de perte de HK si on se fit au SEQUENCE_CNT mais plutot une erreur de datation.

Les fichiers (2016_02_16_09_59_50*) sont dans /home/validation.

Contexte du test
---------------------
FSW 3.0.0.22
VHDL 1.1.89
EM AVEC Timegen
SocExplorerEngine.getSocExplorer: Version = 0.6.2, Branch = default, Changeset = 819d0376d481
StarDundee


Files

test_mode_SBMx_12h.py (3.41 KB) test_mode_SBMx_12h.py Veronique bouzid, 17/02/2016 12:19 PM
test_mode_SBMx_12h.py (3.41 KB) test_mode_SBMx_12h.py Veronique bouzid, 17/02/2016 12:20 PM

Related issues

Related to Support #626: Lost TM_LFR_HK in 3.0.0.22 Closedbruno katra13/02/2016

Actions
Actions

Also available in: Atom PDF