INSTRU: Issues
https://hephaistos.lpp.polytechnique.fr/redmine/
https://hephaistos.lpp.polytechnique.fr/redmine/redmine/favicon.ico?1508097601
2017-04-18T08:42:12Z
Redmine
Redmine
LFR-FSW - Bug #1066 (Closed): "Failure on LFR booting process" après TC_LFR_RESET
https://hephaistos.lpp.polytechnique.fr/redmine/issues/1066
2017-04-18T08:42:12Z
bruno katra
<p>J'ai été mis au courant il y a 10 jours de ce problème : issue JIRA <a class="external" href="https://jira-lesia.obspm.fr/browse/RPWMEB-599">https://jira-lesia.obspm.fr/browse/RPWMEB-599</a><br />De mémoire, après un TC_LFR_RESET( exit(0) ), P.Plasson avait dit qu'il détectait le fait que le soft était arrêté et qu'ils étaient capables de redémarrer LFR. Apparemment cela ne fonctionnait pas sur l'EM2.<br />Voici le contenu résumé de l'issue JIRA :</p>
<pre>
During the preparation of the RPW Short Functional Test v3.1 on MEB EM2, a problem during LFR reset has been observed.
La carte LFR semble ne plus répondre à la fin de l'étape de configuration du processeur (première étape du boot RMAP) suite à la TC_LFR_RESET.
Les testlogs sont également disponibles en attaché dans "Failure on LFR booting process - Testlogs.7z".
L'historique de la conversation es disponible en attaché sur le fichier "Failure on LFR booting process.msg". Voici le dernière échange de cette conversation:
Le DAS génère bien un événement TX_TIMEOUT juste avant de générer les erreurs MISSING RMAP réponses : cela signifie que le DAS a bien initié la transmission du paquet SpaceWire RMAP vers LFR, mais que cette transmission ne se termine pas car LFR ne répond plus.
Quand le DAS détecte le timeout, il force un reset de l'interface SpaceWire : la connexion devrait se refaire automatiquement, mais ce n'est pas le cas : LFR ne répond plus et le DAS génère cette fois-ci une erreur de timeout sur la connexion SpaceWire.
Conclusion : je ne vois pas de dysfonctionnement avéré du DAS mais plutôt une carte LFR qui ne semble plus répondre à la fin de l'étape de configuration du processeur (première étape du boot RMAP). Je pense qu'il va falloir essayer de reproduire le problème avec la MEB PFM.
</pre>
LFR-FSW - Bug #813 (Closed): Analyse Logiscope LFR_3.1.0.4 : metric Cyclomatic number
https://hephaistos.lpp.polytechnique.fr/redmine/issues/813
2016-10-19T13:36:39Z
William Recart
william.recart@lpp.polytechnique.fr
<p>La métrique Cyclomatic number doit etre inférieure à 20.</p>
<p>Le métrique est non respectée dans 1.19% des cas :<br />start_all_tasks (void) => 34<br />actn_task (rtems_task_argument) => 21<br />tc_check_length (unsignedchar, unsignedint) => 33</p>
LFR-FSW - Bug #812 (Closed): Analyse Logiscope LFR_3.1.0.4 : metric Maximum nesting level
https://hephaistos.lpp.polytechnique.fr/redmine/issues/812
2016-10-19T13:30:46Z
William Recart
william.recart@lpp.polytechnique.fr
<p>La métrique Maximum nesting level doit etre inférieure à 4.</p>
<p>Le métrique est non respectée dans 1.58% des cas :<br />cwf2_task (rtems_task_argument) => 5<br />lfr_rtems_cpu_usage_report (void) => 6<br />recv_task (rtems_task_argument) => 6<br />send_task (rtems_task_argument) => 10</p>
LFR-FSW - Bug #811 (Closed): Analyse Logiscope LFR_3.1.0.4 : metric Comment frequency
https://hephaistos.lpp.polytechnique.fr/redmine/issues/811
2016-10-19T13:26:12Z
William Recart
william.recart@lpp.polytechnique.fr
<p>Le taux de commentaire doit être > 15% par fonction</p>
<p>Le métrique "Comment frequency" est non respectée dans 17.39% des cas :<br />ASM_reorganize_and_divide (float*, float*, float)<br />get_message_queue_id_send (rtems_id*)<br />get_message_queue_id_recv (rtems_id*)<br />get_message_queue_id_prc0 (rtems_id*)<br />get_message_queue_id_prc1 (rtems_id*)<br />get_message_queue_id_prc2 (rtems_id*)<br />update_queue_max_count (rtems_id, unsignedchar*)<br />init_k_coefficients_prc2 (void)<br />reset_nb_sm_f1 (unsignedchar)<br />init_k_coefficients_prc1 (void)<br />reset_nb_sm_f0 (unsignedchar)<br />init_k_coefficients_prc0 (void)<br />getRingNodeToSendSWF (unsignedchar)<br />reset_extractSWF (void)<br />waveforms_isr_burst (void)<br />WFP_reset_current_ring_nodes (void)<br />compute_acquisition_time (unsignedint, unsignedint, unsignedint, unsignedchar, unsignedchar*)<br />applyCorrection (double)<br />set_wfp_delta_f0_f0_2 (void)<br />check_update_info_hk_tds_mode (unsignedchar)<br />check_update_info_hk_thr_mode (unsignedchar)<br />build_sy_lfr_rw_masks (void)<br />merge_fbins_masks (void)<br />copyFloatByChar (unsignedchar*, unsignedchar*)<br />floatToChar (float, unsignedchar*)<br />init_kcoefficients_dump (void)<br />restart_asm_activities (unsignedchar)<br />launch_spectral_matrix (void)<br />setCalibrationData (void)<br />setCalibrationDataInterleaved (void)<br />setCalibration (bool)<br />reset_lfr (void)<br />tc_check_length (unsignedchar, unsignedint)<br />update_hk_lfr_last_er_fields (unsignedint, unsignedchar)<br />check_timecode_and_internal_time_coherency (unsignedchar, unsignedchar)<br />init_header_asm (Header_TM_LFR_SCIENCE_ASM_t*)<br />getRingNodeForAveraging (unsignedchar)<br />ASM_generic_init_ring (ring_node_asm*, unsignedchar)<br />SM_reset_current_ring_nodes (void)<br />set_time (unsignedchar*, unsignedchar*)<br />extractReImVectors (float*, float*, unsignedint)<br />copyReVectors (float*, float*, unsignedint)<br />getFBinMask (int, unsignedchar)<br />init_kcoeff_sbm_from_kcoeff_norm (float*, float*, unsignedchar)<br />send_dumb_hk (void)<br />get_v_e1_e2_f3 (unsignedchar*)</p>
LFR-FSW - Bug #808 (Closed): Analyse Logiscope LFR_3.1.0.4 : Don_Separee Severity is Medium
https://hephaistos.lpp.polytechnique.fr/redmine/issues/808
2016-10-19T12:37:54Z
William Recart
william.recart@lpp.polytechnique.fr
<p>Rappel de la règle :<br />Don_Separee<br />Definition:<br />-----------<br />Variable declarations have the following formalism: type variable_name. <br />It is forbidden to have more than one variable for the same type declarator.</p>
<p>Example:<br />--------</p>
<p>// write<br />int width;<br />int length;</p>
<p>// do not write<br />int width, length;</p>
<p>La règle n'est pas respectée dans 1 cas d'après Logiscope:<br />Fichier lfr_cpu_usage_report.c : ligne 21</p>
LFR-FSW - Bug #807 (Closed): Analyse Logiscope LFR_3.1.0.4 : Don_Enumeration Severity is Medium
https://hephaistos.lpp.polytechnique.fr/redmine/issues/807
2016-10-19T12:36:33Z
William Recart
william.recart@lpp.polytechnique.fr
<p>Rappel de la règle :<br />Don_Enumeration<br />Definition:<br />-----------<br />Numbers, characters and strings have to be declared as constants instead of being <br />used as literals inside a program. The user can list the allowed literal <br />constants.</p>
<p>Parameters:<br />-----------<br />A list of character strings representing the allowed literal constants.</p>
<p>Note: In the case of constants used in initializing lists <br />(concerning array and struct structures), only the first five violations are shown.</p>
<p>Justification:<br />--------------<br />Makes maintenance easier by avoiding the scattering of constants among the code, <br />often with the same value.</p>
<p>Example:<br />--------</p>
<p>// do not write</p>
<p>char tab<sup><a href="#fn100">100</a></sup>;<br />int i;</p>
<p>La règle n'est pas respectée dans 1435 cas d'après Logiscope:<br />Fichier avf0_prc0.c : lignes 27, 46, 83, 90, 172, 376, 377, 378, 378, 379, 380, 381, 382, 383, 384<br />Fichier avf1_prc1.c : lignes 28, 84, 91, 173, 368, 369, 370, 370, 371, 372, 373, 374<br />Fichier avf2_prc2.c : lignes 26, 72, 76, 123, 256, 269, 282<br />Fichier ccsds_types.h : lignes 303, 304, 305, 311, 313, 314, 323, 324, 325, 331, 333, 334, 335, 348, 349, 350, 356, 358, 359, 360, 363, 372, 373, 374, 380, 382, 383, 384, 395, 396, 397, 403, 405, 406, 407, 418, 419, 420, 426, 428, 429, 430, 433, 434, 435, 436, 444, 445, 446, 452, 460, 461, 469, 470, 471, 477, 483, 484, 492, 493, 494, 500, 508, 509, 517, 518, 519, 525, 531, 533, 541, 542, 543, 549, 555, 556, 564, 565, 566, 572, 580, 581, 582, 587, 592, 593, 594, 610, 611, 612, 613, 614, 615, 616, 617, 618, 619, 620, 621, 623, 624, 625, 626, 628, 635, 636, 640, 642, 643, 644, 646, 647, 648, 687, 688, 689, 695, 705, 706, 707, 729, 730, 731, 732, 734, 735, 736, 737, 739, 740, 741, 742, 748, 750, 751, 754, 755, 756, 757, 758, 759, 760, 761, 762, 763, 764, 765, 776, 777, 778, 784, 792<br />Fichier fsw_config.c : lignes 7, 7, 8, 8, 9, 9<br />Fichier fsw_globals.c : lignes 26, 27, 28, 98<br />Fichier fsw_init.c : lignes 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 322, 323, 325, 326, 327, 332, 345, 345, 345, 345, 346, 346, 346, 346, 347, 347, 347, 347, 348, 348, 348, 348, 349, 349, 349, 349, 350, 350, 350, 350, 351, 351, 351, 351, 352, 352, 352, 352, 353, 353, 353, 353, 354, 354, 354, 354, 355, 355, 355, 355, 356, 356, 356, 356, 357, 357, 357, 357, 358, 358, 358, 358, 359, 359, 359, 359, 360, 360, 360, 360, 361, 361, 361, 361, 362, 362, 362, 362, 363, 363, 363, 363, 366, 366, 366, 366, 368, 368, 368, 368, 369, 369, 369, 369, 370, 370, 370, 370, 371, 371, 371, 371, 372, 372, 372, 372, 374, 374, 374, 374, 406, 449, 465, 481, 831, 831, 831, 831, 843, 843, 843, 843, 855, 855, 855, 855, 867, 867, 867, 867, 879, 879, 879, 879, 916, 917, 918, 919<br />Fichier fsw_init.h : lignes 19, 20<br />Fichier fsw_misc.c : lignes 28, 48, 49, 50, 51, 52, 64, 65, 66, 130, 144, 145, 146, 147, 193, 193, 193, 193, 213, 220, 264, 264, 272, 287, 291, 292, 293, 293, 294, 295, 295, 296, 354, 354, 355, 356, 357, 358, 380, 382, 386, 390, 394, 422, 429, 433, 447, 448, 452, 453, 453, 473, 474, 494, 495, 496, 496, 497, 498, 498, 499, 509, 509, 526, 530, 536, 537, 538, 538, 539, 540, 540, 541, 545, 546, 550, 551, 553, 555, 556, 556, 560, 562, 586, 587, 588, 588, 589, 589, 590, 590, 591, 591, 604, 605, 606, 606, 607, 607, 608, 608, 609, 609, 628, 640, 644, 652, 656, 664, 668, 676, 680, 686, 689, 705, 706, 707, 740, 740, 741, 743, 743, 744, 746, 746, 747, 757, 757, 811<br />Fichier fsw_params.h : lignes 276, 277, 278<br />Fichier fsw_processing.c : lignes 51, 70, 76, 78, 98, 100, 117, 128, 128, 134, 136, 156, 158, 175, 185, 185, 191, 193, 202, 208, 214, 236, 236, 238, 243, 273, 273, 279, 279, 285, 285, 360, 362, 365, 366, 369, 373, 374, 375, 375, 376, 376, 377, 377, 378, 378, 381, 382, 383, 384, 385, 386, 386, 387, 387, 388, 388, 389, 389, 390, 400, 402, 405, 406, 409, 415, 416, 417, 418, 419, 420, 421, 422, 423, 424, 425, 480, 514, 521, 521, 522, 522, 523, 523, 524, 524, 530, 531, 531, 532, 533, 533, 534, 534, 535, 535, 536, 584, 585, 605, 606, 607, 608, 609, 610, 611, 612, 613, 616, 617, 618, 619, 669, 669, 692, 699, 700, 702, 719, 723, 728, 731, 732, 733, 782, 783<br />Fichier fsw_processing.h : lignes 27, 28, 29, 35, 41, 42, 44, 53, 54, 55, 61, 67, 69, 71, 102, 103, 176, 184, 204, 205, 206, 206, 206, 207, 207, 207, 208, 208, 208, 209, 209, 209, 210, 210, 210, 211, 211, 211, 287, 287, 344<br />Fichier fsw_processing_globals.c : ligne 46<br />Fichier fsw_spacewire.c : lignes 60, 67, 125, 126, 162, 163, 194, 263, 263, 264, 264, 349, 351, 479, 539, 542, 561, 565, 768, 768, 769, 773, 773, 774, 774, 775, 775, 776, 776, 783, 785, 810, 810, 812, 820, 851, 1010, 1011, 1017, 1018, 1019, 1020, 1021, 1022, 1024, 1026, 1027, 1036, 1040, 1047, 1048, 1049, 1050, 1051, 1052, 1054, 1057, 1058, 1068, 1072, 1073, 1079, 1080, 1081, 1082, 1083, 1084, 1086, 1087, 1088, 1089, 1090, 1091, 1128, 1132, 1153, 1153, 1154, 1154, 1155, 1155, 1156, 1156, 1161, 1166, 1216, 1225, 1228, 1230, 1236, 1238, 1247, 1247, 1248, 1248, 1249, 1249, 1250, 1250, 1302, 1306, 1329, 1329, 1330, 1330, 1331, 1331, 1332, 1332, 1335, 1368, 1378, 1389, 1399, 1402, 1406, 1407, 1408, 1408, 1409, 1410, 1410, 1411, 1415, 1415, 1416, 1416, 1417, 1417, 1418, 1418, 1448, 1458, 1469, 1479, 1482, 1486, 1487, 1488, 1488, 1489, 1490, 1490, 1491, 1495, 1495, 1496, 1496, 1497, 1497, 1498, 1498, 1528, 1537, 1546, 1549, 1553, 1554, 1555, 1555, 1556, 1557, 1557, 1558, 1562, 1562, 1563, 1563, 1564, 1564, 1565, 1565, 1586, 1598<br />Fichier lfr_cpu_usage_report.c : lignes 95, 103, 104, 110<br />Fichier tc_acceptance.c : lignes 13, 28, 28, 28, 28, 42, 46, 48, 49, 51, 52, 54, 55, 57, 58, 60, 61, 63, 64, 66, 67, 87, 91, 92, 128, 128, 128, 128, 129, 130, 458, 460<br />Fichier tc_handler.c : lignes 35, 180, 265, 269, 269, 274, 279, 282, 293, 295, 360, 361, 362, 362, 363, 365, 368, 489, 502, 905, 922, 923, 928, 929, 934, 935, 940, 941, 946, 947, 952, 953, 958, 959, 964, 965, 971, 971, 972, 972, 973, 973, 974, 974, 996, 1013, 1014, 1019, 1020, 1025, 1026, 1031, 1032, 1038, 1038, 1039, 1039, 1322, 1326, 1334, 1338, 1367, 1368, 1369, 1370, 1371, 1371, 1373, 1376, 1378, 1379, 1380, 1381, 1392, 1395, 1396, 1397, 1398, 1400, 1403, 1405, 1406, 1407, 1407, 1411, 1413, 1413, 1414, 1414, 1415, 1415, 1416, 1416, 1417, 1417, 1425, 1429, 1438, 1442, 1451, 1455, 1482, 1488, 1508, 1510, 1514, 1514, 1515, 1515, 1516, 1516, 1517, 1517, 1519, 1521, 1538, 1540, 1544, 1544, 1545, 1545, 1546, 1546, 1547, 1547, 1549, 1551, 1618, 1618, 1626, 1630<br />Fichier tc_load_dump_parameters.c : lignes 108, 117, 130, 175, 184, 192, 192, 195, 240, 249, 262, 334, 334, 335, 335, 339, 339, 340, 340, 343, 343, 344, 344, 350, 408, 422, 428, 436, 441, 442, 443, 443, 444, 445, 445, 446, 460, 462, 463, 467, 472, 473, 474, 474, 475, 476, 476, 477, 511, 512, 513, 513, 514, 515, 515, 516, 551, 555, 559, 570, 572, 578, 580, 589, 598, 608, 617, 627, 988, 996, 999, 1000, 1023, 1028, 1033, 1034, 1045, 1053, 1056, 1059, 1063, 1064, 1065, 1065, 1073, 1081, 1087, 1091, 1093, 1095, 1101, 1103, 1107, 1107, 1110, 1110, 1113, 1113, 1116, 1116, 1119, 1119, 1122, 1122, 1125, 1128, 1133, 1144, 1167, 1215, 1216, 1217, 1222, 1247, 1247, 1249, 1255, 1255, 1258, 1258, 1266, 1268, 1275, 1275, 1278, 1278, 1317, 1364, 1365, 1383, 1383, 1384, 1384, 1394, 1395, 1413, 1417, 1424, 1425, 1426, 1426, 1427, 1428, 1428, 1429, 1439, 1441, 1443, 1468, 1472, 1473, 1483, 1489, 1490, 1490, 1495, 1496, 1498, 1503, 1504, 1506, 1514, 1514, 1520, 1524, 1531, 1532, 1533, 1533, 1534, 1534, 1535, 1535, 1536, 1536, 1539, 1546, 1548, 1611, 1612, 1616<br />Fichier tm_lfr_tc_exe.c : lignes 44, 47, 54, 55, 56, 56, 57, 58, 58, 59, 109, 112, 119, 120, 121, 121, 122, 123, 123, 124, 126, 177, 180, 187, 188, 189, 189, 190, 191, 191, 192, 194, 245, 248, 255, 256, 257, 257, 258, 259, 259, 260, 262, 311, 314, 321, 322, 323, 323, 324, 325, 325, 326, 328, 379, 380, 388, 391, 398, 399, 400, 400, 401, 402, 402, 403, 405, 497, 498, 502<br />Fichier wf_handler.c : lignes 64, 67, 89, 118, 118, 121, 121, 125, 127, 127, 131, 145, 145, 160, 162, 172, 185, 185, 191, 191, 197, 199, 199, 204, 212, 212, 216, 216, 221, 223, 223, 228, 236, 236, 241, 241, 246, 248, 248, 253, 286, 286, 288, 288, 400, 401, 405, 416, 417, 417, 455, 470, 490, 578, 679, 679, 680, 680, 681, 681, 682, 682, 698, 701, 703, 704, 705, 705, 706, 707, 707, 708, 710, 711, 712, 712, 713, 713, 714, 714, 715, 720, 720, 724, 724, 728, 728, 732, 732, 736, 736, 740, 740, 744, 744, 748, 748, 753, 759, 760, 761, 761, 762, 762, 763, 763, 764, 791, 792, 793, 794, 807, 808, 810, 813, 814, 818, 819, 838, 850, 850, 850, 851, 851, 851, 854, 855, 856, 856, 856, 857, 857, 857, 861, 898, 899, 900, 905, 905, 906, 906, 914, 914, 919, 919, 931, 933, 933, 939, 944, 944, 950, 967, 1018, 1029, 1094, 1095, 1096, 1100, 1120, 1120, 1121, 1121, 1122, 1123, 1124, 1124, 1125, 1125, 1144, 1145, 1148, 1149, 1152, 1170, 1173, 1184, 1185, 1185, 1185, 1185, 1185, 1185, 1188, 1208, 1209, 1209, 1209, 1209, 1209, 1209, 1231, 1233, 1292, 1293, 1297<br />Fichier wf_handler.h : ligne 33</p>
LFR-FSW - Bug #801 (Closed): Analyse Logiscope LFR_3.1.0.4 : Don_Initialisation_P2 Severity is High
https://hephaistos.lpp.polytechnique.fr/redmine/issues/801
2016-10-19T12:13:09Z
William Recart
william.recart@lpp.polytechnique.fr
<p>Rappel de la règle :<br />Don_Initialisation_P2 :<br />Definition:<br />-----------<br />All variables must be initialized before they are used, without aking into account<br />on the default value attributed by the compiler.<br />Global variables, parameters of a function in the function body, and data fields <br />of a class in its methods are considered to be initialized.</p>
<p>Justification:<br />--------------<br />Not all compilers give the same default values. Unexpected behaviour can be <br />avoided with better control over variable values.</p>
<p>Limitations:<br />------------<br />This rule is not violated in the following cases: <br />If an array, a struct or a class are used, they will be consided initialized as <br />soon as a part of them has been initialized.<br />For example: <br /> int a<sup><a href="#fn2">2</a></sup>;<br /> int b<sup><a href="#fn2">2</a></sup> = {6, 7};<br /> int h;</p>
<pre><code>a[0] = b[0]; // ok<br /> h = a[1]; // ok</code></pre>
<pre><code>struct
{<br /> int i;<br /> int j;<br /> } e, f;</code></pre>
<pre><code>e.i = 0;<br /> g = e; // ok</code></pre>
<p>This rule is violated in the following cases where initialization is uncertain:</p>
<p>Using a variable in a function call is considered as "being used": if it is not <br />initialized, the rule will be violated. <br />This will occur whatever the use of the function, even initializing the variable.</p>
<p>In cases including a conditional initialization, the rule is violated even though <br />the variable may well be initialized. </p>
<pre><code>int i, j, k;<br /> j = func();<br /> if (j)<br /> i = 0;<br /> k = i; // violation</code></pre>
<p>This applies even when there is an else branch, for example in<br /> int i, j, k;<br /> j = func();<br /> if (j)<br /> i = 0;<br /> else <br /> i = 5;<br /> k = i; // violation <br />where initialization is certain.</p>
<p>In the case of a loop, for example<br />int j, k;<br />for (int i=0; i<glob; i++)
{<br /> j=func(i);<br /> }<br />k = j; // violation <br />where glob is a global variable, depending on the value of glob, j will have been <br />initialized or not: the rule is violated, even if the loop condition occurs or not.</p>
<p>La règle n'est pas respectée dans 352 cas d'après Logiscope:<br />Fichier avf0_prc0.c : lignes 70, 77, 174, 207, 210, 218, 221, 227, 230, 236, 239, 248, 253, 262, 262, 287, 289, 290, 293, 300, 302, 303, 306, 325, 327, 328, 331, 337, 339, 340, 343, 357, 360, 366<br />Fichier avf1_prc1.c : lignes 71, 78, 175, 208, 211, 219, 222, 228, 231, 240, 245, 254, 254, 279, 281, 282, 285, 292, 294, 295, 298, 317, 319, 320, 323, 329, 331, 332, 335, 349, 352, 358<br />Fichier avf2_prc2.c : lignes 59, 66, 125, 156, 159, 163, 168, 177, 177, 202, 204, 205, 208, 216, 218, 219, 222, 238, 244<br />Fichier fsw_init.c : lignes 274, 278, 743, 752, 761, 770, 779, 805, 891, 893<br />Fichier fsw_misc.c : lignes 30, 195, 210, 235, 260, 262, 270, 323, 378, 379, 565, 567, 802, 802, 803, 803, 805, 806, 807, 808<br />Fichier fsw_processing.c : ligne 574<br />Fichier fsw_spacewire.c : lignes 45, 59, 60, 66, 67, 136, 142, 152, 166, 173, 173, 175, 175, 184, 186, 186, 188, 193, 193, 199, 240, 250, 250, 259, 314, 329, 346, 348, 349, 352, 406, 522, 588, 611, 613, 615, 617, 619, 621, 623, 625, 627, 629, 631, 649, 674, 674, 681, 681, 688, 688, 695, 695, 702, 702, 709, 709, 716, 716, 723, 723, 730, 730, 737, 737, 744, 744, 754, 754, 757, 1122, 1124, 1125, 1208, 1209, 1211, 1296, 1298, 1299, 1360, 1362, 1363, 1440, 1442, 1443, 1520, 1522, 1523, 1586, 1586<br />Fichier lfr_cpu_usage_report.c : ligne 110<br />Fichier tc_acceptance.c : lignes 130, 130, 204, 287, 470<br />Fichier tc_handler.c : lignes 39, 45, 58, 58, 58, 67, 71, 71, 72, 72, 75, 76, 76, 79, 79, 80, 80, 83, 83, 84, 84, 87, 87, 88, 88, 91, 91, 92, 92, 95, 95, 96, 96, 99, 99, 100, 100, 103, 103, 104, 104, 107, 107, 108, 108, 111, 111, 112, 112, 115, 115, 116, 116, 119, 119, 120, 120, 123, 123, 124, 124, 127, 127, 128, 128, 131, 132, 132, 393<br />Fichier tc_load_dump_parameters.c : lignes 878, 897, 914, 1021, 1043, 1044, 1045<br />Fichier tm_lfr_tc_exe.c : lignes 379, 379<br />Fichier wf_handler.c : lignes 145, 185, 191, 197, 197, 199, 204, 204, 212, 216, 221, 221, 223, 228, 228, 236, 241, 246, 246, 248, 253, 253, 343, 354, 356, 362, 363, 364, 366, 390, 412, 421, 426, 457, 469, 471, 473, 475, 482, 523, 534, 542, 585, 586, 838, 843, 924, 953, 1183, 1207, 1230, 1264, 1290, 1293, 1293, 1295, 1301, 1303, 1303, 1307, 1313, 1313<br />Fichier : lignes</p>
SciQLOP - Bug #641 (Closed): amda PAD download
https://hephaistos.lpp.polytechnique.fr/redmine/issues/641
2016-03-03T10:29:32Z
Anonymous
<p>is amda PAD download possible</p>
LFR-FSW - Bug #567 (Closed): Analyse Logiscope FSW 3.0.0.10 : Several coding rules violations to ...
https://hephaistos.lpp.polytechnique.fr/redmine/issues/567
2015-11-30T15:48:38Z
bruno katra
<p>William a relevé plusieurs accrocs aux règles de codage dans le code du fsw 3.0.0.10. Certains datent déjà du FSW R2 (<a class="issue tracker-1 status-5 priority-2 priority-default closed" title="Bug: répondre à l'analyse Logiscope effectuée par William sur les sources du logiciel de vol (Closed)" href="https://hephaistos.lpp.polytechnique.fr/redmine/issues/243">#243</a>) et concerneraient les morceaux de code de Thomas (bp) qui est en watcher de cet issue.<br />En PJ se trouve le rapport complet de William, le résumé des problèmes à corriger est au "§6. Action Plan" :</p>
<p>AI-1 Comment frequency to be increase<br />AI-2 Don.Enumeration rule violation to be corrected: a lot of integer value used in the source code shall be replaced by constant or enumerated values.<br />AI-3 Don.Initialisation_P1 rule results to be analysed then justified or corrected.<br />AI-4 Don.Initialisation_P2 rule results to be analysed then justified or corrected.<br />AI-5 Don.Separee rule violation to be corrected<br />AI-6 Tr.Accolades rule violation on files fsw_misc.c and lfr_cpu_usage_report.c to be corrected<br />AI-7 Tr.BoucleSortie rule violation to be corrected, use of continue and break instruction forbidden.<br />AI-8 Tr.OrdreChoix rule violation to be corrected, default case to be added<br />AI-9 Tr.Parenthèses rule violation to be corrected</p>
<p>-------------------------<br />Tracké dans :<br /><a class="external" href="https://jira-lesia.obspm.fr/browse/RPWSWR-446">https://jira-lesia.obspm.fr/browse/RPWSWR-446</a><br /><a class="external" href="https://jira-lesia.obspm.fr/browse/RPWSWR-574">https://jira-lesia.obspm.fr/browse/RPWSWR-574</a></p>
LFR-FSW - Bug #560 (Closed): activer la vérification du cache du Leon3FT
https://hephaistos.lpp.polytechnique.fr/redmine/issues/560
2015-11-04T04:43:52Z
Veronique bouzid
<p>Lors de la vérification de l'activation du cache Alexis a posé la question suivante à Paul:</p>
<p>"J'ai trouvée ça dans la doc(grip p822 70.11.4 Cache control register) pour le cache: 20:19 FT scheme (FT) - “00” = no FT, “01” = 4-bit checking implemented. Tu l'actives?"</p>
<p>La réponse de Paul<br /> Ma réponse était non. Il faudra que je le fasse pour une utilisation dans le cadre FT.</p>
<p>Il faut donc implemeter cette fonctionalité et mettre à jour la SRS en conséquence.<br />Il reste à déterminer comment valider la mise en place de cette fonctionalité (Alexis et Véronique!!)</p>
LFR-FSW - Bug #508 (Closed): Field DESTINATION_ID into TM_LFR_KCOEFFICIENTS_DUMP non compliant
https://hephaistos.lpp.polytechnique.fr/redmine/issues/508
2015-09-24T14:08:47Z
Veronique bouzid
<p>Le champ DESTINATION_ID = le champ SOURCE_ID de la TC_LFR envoyée<br />Ce n'est pas le cas, DESTINATION_ID = 0</p>
<p>14:50:23.011819, <strong>TC_LFR_DUMP_KCOEFFICIENTS</strong>, CCSDS_VERSION_NUMBER = 0, PACKET_TYPE: TC_PACKET = 1, DATA_FIELD_HEADER_FLAG: WITH_HEADER = 1, PROCESS_ID: RPW_PID_2 = 76, PACKET_CATEGORY: PRIVATE_SCIENCE_OR_TELECOMMAND = 12, (PACKET_ID=0x1ccc), SEGMENTATION_GROUPING_FLAG: STANDALONE_PACKET = 3, SEQUENCE_CNT=11420, (PACKET_SEQUENCE_CONTROL=0xec9c), PACKET_LENGTH=5, CCSDS_SECONDARY_HEADER_FLAG=0, PUS_VERSION = 1, ACK_EXECUTION_COMPLETION=1, ACK_EXECUTION_PROGRESS=0, ACK_EXECUTION_START=0, ACK_ACCEPTANCE=1, SERVICE_TYPE: EQ_CONFIGURATION = 181, SERVICE_SUBTYPE: DUMP_KCOEFFICIENTS = 95, <strong>SOURCE_ID: AOCS = 11</strong>, CRC = 0x19af</p>
<p>14:50:23.045264, <strong>TM_LFR_KCOEFFICIENTS_DUMP</strong>, CCSDS_VERSION_NUMBER = 0, PACKET_TYPE: TM_PACKET = 0, DATA_FIELD_HEADER_FLAG: WITH_HEADER = 1, PROCESS_ID: RPW_PID_2 = 76, PACKET_CATEGORY: FUNCTIONAL_NON_CYCLIC = 6, (PACKET_ID=0xcc6), SEGMENTATION_GROUPING_FLAG: STANDALONE_PACKET = 3, SEQUENCE_CNT=11, (PACKET_SEQUENCE_CONTROL=0xc00b), PACKET_LENGTH=3913, SPARE_1=0, PUS_VERSION = 1, SPARE_2=0, SERVICE_TYPE: EQ_CONFIGURATION = 181, SERVICE_SUBTYPE: KCOEFFICIENTS_DUMP = 96, <strong>DESTINATION_ID: GROUND = 0</strong>, TIME=0x8000037bec96, PA_LFR_HK_SID: LFR_KCOEFF_SID = 11, PA_LFR_KCOEFF_PKT_CNT: 2, PA_LFR_KCOEFF_PKT_NR: 1 , PA_LFR_KCOEFF_BLK_NR: 30 , SY_LFR_KCOEFF_FREQUENCY: 0 , SY_LFR_KCOEFF_1:1065353216 , SY_LFR_KCOEFF_2:1065353216 , SY_LFR_KCOEFF_3:1065353216 , SY_LFR_KCOEFF_4:1065353216 , SY_LFR_KCOEFF_5:1065353216 , SY_LFR_KCOEFF_6:1065353216 , SY_LFR_KCOEFF_7:1065353216 , SY_LFR_KCOEFF_8:1065353216 , ...</p>
<p>le script joué est /opt/VALIDATION_R3/lfrverif/LFR_SVS/SVS-0018/source_id_loop_step1.py<br />le fichier detail /home/validation/data/R3/3.0.0.8/1.1.89/SVS-0018/2015_09_23-14_51_13-Detail.txt</p>
<p>Contexte du test<br />----------------<br />----------------<br />FSW 3.0.0.8<br />VHDL 1.1.89<br />EM sans Timegen<br />SocExplorerEngine.getSocExplorer: Version = 0.6.2, Branch = default, Changeset = 819d0376d481<br />StarDundee</p>
LFR-FSW - Bug #241 (Closed): 2 petits pb avec le SGSE
https://hephaistos.lpp.polytechnique.fr/redmine/issues/241
2014-09-19T05:39:48Z
paul leroy
<p>Juste pour mémoire:<br />- la calibration de la FFT affichée sous le SGSE ne me semble pas correcte : ~ 68.6 dB au dessus de ce qui est calculé par les ASM ...?<br />- l'enregistrement des ASM_F1 et ASM_F2 ne semble jamais s'arrêter lorsqu'ils ont été sélectionnés une première fois ...</p>
LFR-FSW - Bug #179 (Closed): ACQUISITION_TIME a une valeur erronée sur certains produits au bout ...
https://hephaistos.lpp.polytechnique.fr/redmine/issues/179
2014-06-26T15:49:01Z
bruno katra
<p>Problème observé sur un test de 12 heures en Normal Mode sur l'EM:</p>
<p>Au bout de 8 heures de tests :</p>
<p>03:04:02.892263, TM_LFR_SCIENCE_NORMAL_BP1_F0, CCSDS_VERSION_NUMBER = 0, PACKET_TYPE: TM_PACKET = 0, DATA_FIELD_HEADER_FLAG: WITH_HEADER = 1, PROCESS_ID: RPW_PID_2 = 76, PACKET_CATEGORY: PRIVATE_SCIENCE_OR_TELECOMMAND = 12, (PACKET_ID=0xccc), SEGMENTATION_GROUPING_FLAG: STANDALONE_PACKET = 3, SEQUENCE_CNT=16220, (PACKET_SEQUENCE_CONTROL=0xff5c), PACKET_LENGTH=119, SPARE_1=0, PUS_VERSION = 1, SPARE_2=0, SERVICE_TYPE: SCIENCE_DATA_TRANSFER = 21, SERVICE_SUBTYPE: SCIENCE_REPORT = 3, DESTINATION_ID: GROUND = 0, TIME=0x80007ffca29c, PA_LFR_SID_PKT: SC_N_BP1_F0 = 14, PA_BIA_MODE_MUX_SET: SET_0 = 0, PA_BIA_MODE_HV_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS1_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS2_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS3_ENABLED: DISABLED = 0, PA_BIA_ON_OFF: OFF = 0, <strong>PA_LFR_ACQUISITION_TIME=0x80007ffca29c</strong></p>
<p>le BP1_F0 suivant devrait être à environ : 0x80008000a29c<br />OR</p>
<p>03:04:06.892236, TM_LFR_SCIENCE_NORMAL_BP1_F0, CCSDS_VERSION_NUMBER = 0, PACKET_TYPE: TM_PACKET = 0, DATA_FIELD_HEADER_FLAG: WITH_HEADER = 1, PROCESS_ID: RPW_PID_2 = 76, PACKET_CATEGORY: PRIVATE_SCIENCE_OR_TELECOMMAND = 12, (PACKET_ID=0xccc), SEGMENTATION_GROUPING_FLAG: STANDALONE_PACKET = 3, SEQUENCE_CNT=16223, (PACKET_SEQUENCE_CONTROL=0xff5f), PACKET_LENGTH=119, SPARE_1=0, PUS_VERSION = 1, SPARE_2=0, SERVICE_TYPE: SCIENCE_DATA_TRANSFER = 21, SERVICE_SUBTYPE: SCIENCE_REPORT = 3, DESTINATION_ID: GROUND = 0, TIME=0xffff8000a29c, PA_LFR_SID_PKT: SC_N_BP1_F0 = 14, PA_BIA_MODE_MUX_SET: SET_0 = 0, PA_BIA_MODE_HV_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS1_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS2_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS3_ENABLED: DISABLED = 0, PA_BIA_ON_OFF: OFF = 0, <strong>PA_LFR_ACQUISITION_TIME=0xffff8000a29c</strong>,</p>
<p><strong>On retrouve bien la partie 8000a29c mais un talon 0xffff est apparu et reste jusqu'à la fin du test</strong></p>
<p><strong><ins>LE BUG TOUCHE LES PRODUITS SUIVANTS AUSSI : CWF_F3, SWF_F0/1/2 ET BP1/2_F0/1 AVEC LE TALON 0x7fff</ins></strong></p>
<p>03:12:52.805511, TM_LFR_SCIENCE_NORMAL_CWF_F3, CCSDS_VERSION_NUMBER = 0, PACKET_TYPE: TM_PACKET = 0, DATA_FIELD_HEADER_FLAG: WITH_HEADER = 1, PROCESS_ID: RPW_PID_2 = 76, PACKET_CATEGORY: PRIVATE_SCIENCE_OR_TELECOMMAND = 12, (PACKET_ID=0xccc), SEGMENTATION_GROUPING_FLAG: STANDALONE_PACKET = 3, SEQUENCE_CNT=348, (PACKET_SEQUENCE_CONTROL=0xc15c), PACKET_LENGTH=4051, SPARE_1=0, PUS_VERSION = 1, SPARE_2=0, SERVICE_TYPE: SCIENCE_DATA_TRANSFER = 21, SERVICE_SUBTYPE: SCIENCE_REPORT = 3, DESTINATION_ID: GROUND = 0, TIME=0x7fff81c6aea7, PA_LFR_SID_PKT: SC_N_CWF_F3 = 1, PA_BIA_MODE_MUX_SET: SET_0 = 0, PA_BIA_MODE_HV_ENABLED: ENABLED = 1, PA_BIA_MODE_BIAS1_ENABLED: ENABLED = 1, PA_BIA_MODE_BIAS2_ENABLED: ENABLED = 1, PA_BIA_MODE_BIAS3_ENABLED: ENABLED = 1, PA_BIA_ON_OFF: OFF = 0, <strong>PA_LFR_ACQUISITION_TIME=0x7fff81c6aea7</strong></p>
<p><strong><ins>NE SONT PAS CONCERNÉS : BP1/2_F2 ET ASM_F0/1/2</ins></strong></p>
<p>--------------------------<br /><ins><strong>Contexte :</strong></ins></p>
<p>LPPMON: Version=0.2.2 Branch=default Changeset=835955994d5f<br />EM 2<br />Vhdl: mini-lfr_1.1.23<br />Brique GRESB<br />Soft:1.0.0.12 (variante sur carte finale)</p>
<p>Test case : SVS-0043</p>
LFR-FSW - Bug #113 (Closed): Affectation des champs de TM_LFR_HK en fin de boot du LFR
https://hephaistos.lpp.polytechnique.fr/redmine/issues/113
2014-04-02T12:02:09Z
Gerald Saule
<p>Les HK de début d'execution sont en</p>
<blockquote>
<p>11:26:59.425762, TM_LFR_HK, CCSDS_VERSION_NUMBER = 0, PACKET_TYPE: TM_PACKET = 0, DATA_FIELD_HEADER_FLAG: WITH_HEADER = 1, PROCESS_ID: RPW_PID_2 = 76, PACKET_CATEGORY: HK_ROUTINE = 4, (PACKET_ID=0xcc4), SEGMENTATION_GROUPING_FLAG: STANDALONE_PACKET = 3, SEQUENCE_CNT=1, (PACKET_SEQUENCE_CONTROL=0xc001), PACKET_LENGTH=117, SPARE_1=0, PUS_VERSION = 1, SPARE_2=0, SERVICE_TYPE: HOUSEKEEPING_AND_DIAGNOSTIC_DATA_REPORTING = 3, SERVICE_SUBTYPE: HK_PARAMETER_REPORT = 25, DESTINATION_ID: GROUND = 0, TIME=0x800001a1d101, PA_LFR_HK_REPORT_SID: LFR_HK_SID = 1, HK_LFR_MODE: STANDBY = 0, HK_LFR_DPU_SPW_ENABLED: ENABLED = 1, HK_LFR_DPU_SPW_LINK_STATE: RUN = 5, SPARE=0x0, SY_LFR_WATCHDOG_ENABLED: DISABLED = 0, HK_LFR_CALIB_ENABLED: DISABLED = 0, HK_LFR_RESET_CAUSE: UNKNOWN_CAUSE = 0, SY_LFR_SW_VERSION_N1=1, SY_LFR_SW_VERSION_N2=0, SY_LFR_SW_VERSION_N3=0, SY_LFR_SW_VERSION_N4=4, SY_LFR_FPGA_VERSION_N1=0, SY_LFR_FPGA_VERSION_N2=2, SY_LFR_FPGA_VERSION_N3=255, HK_LFR_CPU_LOAD=0.0, HK_LFR_CPU_LOAD_MAX=0.0, HK_LFR_CPU_LOAD_AVE=0.0, HK_LFR_UPDATE_INFO_TC_CNT=0, HK_LFR_UPDATE_TIME_TC_CNT=0, HK_LFR_EXE_TC_CNT=0, HK_LFR_REJ_TC_CNT=0, HK_LFR_LAST_EXE_TC_ID=0x0, HK_LFR_LAST_EXE_TC_TYPE=0, HK_LFR_LAST_EXE_TC_SUBTYPE=0, HK_LFR_LAST_EXE_TC_TIME=0x000000000000, HK_LFR_LAST_REJ_TC_ID=0x0, HK_LFR_LAST_REJ_TC_TYPE=0, HK_LFR_LAST_REJ_TC_SUBTYPE=0, HK_LFR_LAST_REJ_TC_TIME=0x000000000000, HK_LFR_LE_CNT=0, HK_LFR_ME_CNT=0, HK_LFR_HE_CNT=0, HK_LFR_LAST_ER_RID: NO_ERROR = 0, HK_LFR_LAST_ER_CODE: NO_ERROR = 0, HK_LFR_LAST_ER_TIME=0x000000000000, HK_LFR_VHDL_AA=0, HK_LFR_VHDL_SM=0, HK_LFR_VHDL_FFT=0, HK_LFR_VHDL_SR=0, HK_LFR_VHDL_CIC=0, HK_LFR_VHDL_HK=0, HK_LFR_VHDL_IIR=0, HK_LFR_VHDL_CAL=0, HK_LFR_DPU_SPW_PKT_RCV_CNT=0, HK_LFR_DPU_SPW_PKT_SENT_CNT=0, HK_LFR_DPU_SPW_TICK_OUT_CNT=0, HK_LFR_DPU_SPW_LAST_TIMC=0, HK_LFR_LAST_FAIL_ADDR=0x0, HK_LFR_TEMP_SCM=0degC, HK_LFR_TEMP_PCB=0degC, HK_LFR_TEMP_FPGA=0degC, HK_LFR_SC_V_F3=0, HK_LFR_SC_E1_F3=0, HK_LFR_SC_E2_F3=0, HK_LFR_DPU_SPW_PARITY=0, HK_LFR_DPU_SPW_DISCONNECT=0, HK_LFR_DPU_SPW_ESCAPE=0, HK_LFR_DPU_SPW_CREDIT=0, HK_LFR_DPU_SPW_WRITE_SYNC=0, HK_LFR_DPU_SPW_RX_AHB=0, HK_LFR_DPU_SPW_TX_AHB=0, HK_LFR_DPU_SPW_EARLY_EOP=0, HK_LFR_DPU_SPW_INVALID_ADDR=0, HK_LFR_DPU_SPW_EEP=0, HK_LFR_DPU_SPW_RX_TOO_BIG=0, HK_LFR_TIMECODE_ERRONEOUS=0, HK_LFR_TIMECODE_MISSING=0, HK_LFR_TIMECODE_INVALID=0, HK_LFR_TIME_TIMECODE_IT=0, HK_LFR_TIME_NOT_SYNCHRO=0, HK_LFR_TIME_TIMECODE_CTR=0, HK_LFR_BUFFER_DPU_TC_FIFO=0, HK_LFR_BUFFER_DPU_TM_FIFO=0, HK_LFR_AHB_CORRECTABLE=0, HK_LFR_AHB_UNCORRECTABLE=0, SPARE=0x0</p>
<p>11:26:59.427046, TM_LFR_HK, CCSDS_VERSION_NUMBER = 0, PACKET_TYPE: TM_PACKET = 0, DATA_FIELD_HEADER_FLAG: WITH_HEADER = 1, PROCESS_ID: RPW_PID_2 = 76, PACKET_CATEGORY: HK_ROUTINE = 4, (PACKET_ID=0xcc4), SEGMENTATION_GROUPING_FLAG: STANDALONE_PACKET = 3, SEQUENCE_CNT=0, (PACKET_SEQUENCE_CONTROL=0xc000), PACKET_LENGTH=117, SPARE_1=0, PUS_VERSION = 1, SPARE_2=0, SERVICE_TYPE: HOUSEKEEPING_AND_DIAGNOSTIC_DATA_REPORTING = 3, SERVICE_SUBTYPE: HK_PARAMETER_REPORT = 25, DESTINATION_ID: GROUND = 0, <strong>TIME=0x940040134f90</strong>, PA_LFR_HK_REPORT_SID: LFR_HK_SID = 1, /!\HK_LFR_MODE: 15, HK_LFR_DPU_SPW_ENABLED: ENABLED = 1, /!\HK_LFR_DPU_SPW_LINK_STATE: 7, /!\SPARE=0x7, SY_LFR_WATCHDOG_ENABLED: ENABLED = 1, HK_LFR_CALIB_ENABLED: ENABLED = 1, /!\HK_LFR_RESET_CAUSE: 7, SY_LFR_SW_VERSION_N1=1, SY_LFR_SW_VERSION_N2=0, SY_LFR_SW_VERSION_N3=0, SY_LFR_SW_VERSION_N4=4, SY_LFR_FPGA_VERSION_N1=0, SY_LFR_FPGA_VERSION_N2=2, SY_LFR_FPGA_VERSION_N3=255, HK_LFR_CPU_LOAD=100.0, HK_LFR_CPU_LOAD_MAX=100.0, HK_LFR_CPU_LOAD_AVE=100.0, HK_LFR_UPDATE_INFO_TC_CNT=65535, HK_LFR_UPDATE_TIME_TC_CNT=65535, HK_LFR_EXE_TC_CNT=65535, HK_LFR_REJ_TC_CNT=65535, HK_LFR_LAST_EXE_TC_ID=0xffff, HK_LFR_LAST_EXE_TC_TYPE=65535, HK_LFR_LAST_EXE_TC_SUBTYPE=65535, HK_LFR_LAST_EXE_TC_TIME=0xffffffffffff, HK_LFR_LAST_REJ_TC_ID=0xffff, HK_LFR_LAST_REJ_TC_TYPE=65535, HK_LFR_LAST_REJ_TC_SUBTYPE=65535, HK_LFR_LAST_REJ_TC_TIME=0xffffffffffff, HK_LFR_LE_CNT=65535, HK_LFR_ME_CNT=65535, HK_LFR_HE_CNT=65535, /!\HK_LFR_LAST_ER_RID: 65535, /!\HK_LFR_LAST_ER_CODE: 255, HK_LFR_LAST_ER_TIME=0xffffffffffff, HK_LFR_VHDL_AA=15, HK_LFR_VHDL_SM=15, HK_LFR_VHDL_FFT=15, HK_LFR_VHDL_SR=15, HK_LFR_VHDL_CIC=15, HK_LFR_VHDL_HK=15, HK_LFR_VHDL_IIR=15, HK_LFR_VHDL_CAL=15, HK_LFR_DPU_SPW_PKT_RCV_CNT=65535, HK_LFR_DPU_SPW_PKT_SENT_CNT=65535, HK_LFR_DPU_SPW_TICK_OUT_CNT=255, HK_LFR_DPU_SPW_LAST_TIMC=255, HK_LFR_LAST_FAIL_ADDR=0xffffffff, HK_LFR_TEMP_SCM=65535degC, HK_LFR_TEMP_PCB=65535degC, HK_LFR_TEMP_FPGA=65535degC, HK_LFR_SC_V_F3=65535, HK_LFR_SC_E1_F3=65535, HK_LFR_SC_E2_F3=65535, HK_LFR_DPU_SPW_PARITY=255, HK_LFR_DPU_SPW_DISCONNECT=255, HK_LFR_DPU_SPW_ESCAPE=255, HK_LFR_DPU_SPW_CREDIT=255, HK_LFR_DPU_SPW_WRITE_SYNC=255, HK_LFR_DPU_SPW_RX_AHB=255, HK_LFR_DPU_SPW_TX_AHB=255, HK_LFR_DPU_SPW_EARLY_EOP=255, HK_LFR_DPU_SPW_INVALID_ADDR=255, HK_LFR_DPU_SPW_EEP=255, HK_LFR_DPU_SPW_RX_TOO_BIG=255, HK_LFR_TIMECODE_ERRONEOUS=255, HK_LFR_TIMECODE_MISSING=255, HK_LFR_TIMECODE_INVALID=255, HK_LFR_TIME_TIMECODE_IT=255, HK_LFR_TIME_NOT_SYNCHRO=255, HK_LFR_TIME_TIMECODE_CTR=255, HK_LFR_BUFFER_DPU_TC_FIFO=255, HK_LFR_BUFFER_DPU_TM_FIFO=255, HK_LFR_AHB_CORRECTABLE=255, HK_LFR_AHB_UNCORRECTABLE=255, /!\SPARE=0xff</p>
</blockquote>
<p>Pour le premier HK, les valeurs ne sont pas toutes reproductibles. Il est prévu d'avoir des octets à ff.<br />Pour le deuxième octet, le champ TIME devrait être à 0xffffffffffff.</p>
<p>Contexte:<br />LPPMON: Version=0.2.2 Branch=default Changeset=835955994d5f<br />Carte mini-LFR: LFR-172200 dev V1.0; No série III (sans connecteurs sub-click)<br />Vhdl: mini-lfr_0.2.255<br />Brique Star-Dundee S/N <illisible>.<br />Soft:1.0.0.4 (variante sur carte finale)</p>
<p>TEST CASE = SVS-0011<br />Req = SSS-CP-FS-360</p>
<p>RPW-SYS-IDB-00067-LES_Issue2_Rev2<br />RPW-SYS-MEB-LFR-ICD-00097 Issue2_Rev2<br />RPW-SYS-SSS-00013-LES + Annex_Release_Definition Issue2_rev2</p>
LFR-FSW - Bug #65 (Closed): TC_LFR_LOAD_NORMAL_PAR: pas de vérif sur SY_LFR_N_ASM_P, S_LFR_N_BP_...
https://hephaistos.lpp.polytechnique.fr/redmine/issues/65
2014-02-24T14:13:06Z
Gerald Saule
<p>Cette issue reprend l'issue Bug <a class="issue tracker-4 status-5 priority-3 priority-high3 closed" title="Task: Delivery 3.1.0.5 (Closed)" href="https://hephaistos.lpp.polytechnique.fr/redmine/issues/905">#905</a> (TC_LFR_LOAD_NORMAL_PAR: pas de vérif sur SY_LFR_N_ASM_P, S_LFR_N_BP_P0, SY_LFR_N_BP_P1).</p>
<p>Pour TC_LFR_LOAD_NORMAL_PAR, les champs SY_LFR_N_ASM_P, S_LFR_N_BP_P0, SY_LFR_N_BP_P1 ne sont pas controlés.<br />La valeur 0 devrait être un moyen simple d'obtenir un rejet (il s'agit de périodes).<br />LFR retourne TM_LFR_TC_EXE_SUCCESS.</p>
<p>Contexte:<br />LPPMON: Version=0.2.2 Branch=default Changeset=835955994d5f<br />Carte mini-LFR: LFR-172200 dev V1.0; No série III (sans connecteurs sub-click)<br />Vhdl: mini-lfr_0.0.0.15<br />Brique Star-Dundee S/N 46120065.<br />Soft:1.0.0.1 (variante sur carte finale)</p>
<p>TEST CASE = SVS_0008</p>
<p>RPW-SYS-MEB-LFR-ICD-00097 Issue2_Rev0<br />RPW-SYS-SSS-00013-LES + Annex_Release_Definition Issue2_rev1</p>