CLASSIC
Modul: comm
Rolle: constitutive
Konfidenz: 95%
SNIP_CLASSIC_COMM_SECTION_7_4_1_1_Manage_communication_inhibition
Wortlaut
7.4.1.1 Manage communication inhibition
In principle the utilization of communication inhibition is manageable. The execution permission of communication inhibition functionality is controlled via an inhibition status field (bit field). Each bit represents one communication inhibition functionality. The value of the control bit classifies, if the corresponding communication inhibition has the permission to be executed. The inhibition status field is stored non-volatile to survive an ECU reset. ComM restores the inhibition status field at start-up, if the inhibition status field is available in a non-volatile memory. Otherwise ComM uses the configuration of ComMEcuGroupClassification as default. Note: The layout of the inhibition status field is defined in [SWS_ComM_00669]. The following parameters are relevant for communication inhibition and have a relationship to APIs:
• ComMNoCom: "request bit" of mode inhibition (limit to NoCom), can be controlled by ComM_LimitChannelToNoComMode and ComM_LimitECUToNoComMode, only if ComMEcuGroupClassification enables this functionality (see [ECUC_ComM_00563], [SWS_ComM_00163], [SWS_ComM_00124]).
• ComMNoWakeup: "request bit" of mode inhibition (wakeup inhibition), can be controlled by ComM_PreventWakeUp, only if ComMEcuGroupClassification enables this functionality (see [ECUC_ComM_00563], [SWS_ComM_00156]).
• ComMEcuGroupClassification: "mask bits" of mode inhibition behavior, can be controlled by ComM_SetECUGroupClassification, regardless of ComMNoCom and ComMNoWakeup values
[SWS_ComM_01102] Call of ComM_SetECUGroupClassification Upstream requirements: SRS_ModeMgm_09071, SRS_ModeMgm_09157
⌈If ComM_SetECUGroupClassification is called, ComM shall update the internal status field with the values of the given inhibition status (Status).⌋ Note: A change of the internal status field has no impact on a activated inhibition function (see 7.4.1.4.2 “Wake up inhibition - example 2” for an example)
[SWS_ComM_01103] Call of communication inhibition function Upstream requirements: SRS_ModeMgm_09071, SRS_ModeMgm_09157
⌈If a communication inhibition function is called and the corresponding bit in the inhibition status field is set (0b1), then the communication inhibition function shall be executed. Otherwise the function shall ignore the inhibition function request and return with E_NOT_OK.⌋
[SWS_ComM_01104] Non volatile storage of ComMEcuGroupClassification Upstream requirements: SRS_ModeMgm_09071, SRS_ModeMgm_09157
⌈ComMEcuGroupClassification status shall be stored non-volatile, if it was changed during runtime via call of ComM_SetECUGroupClassification and ComMEcuGroupClassificationNvMStorage is set to TRUE.⌋
[SWS_ComM_01105] Default values of ComMEcuGroupClassification Upstream requirements: SRS_ModeMgm_09071, SRS_ModeMgm_09157
⌈The values of ComMEcuGroupClassification configured in the ECUC shall be considered as default values and used, if the ComMEcuGroupClassification status is not available in non-volatile memory.⌋
Versionen & Provenienz · Zugeordnete Anforderungen
Diese Angaben zeigt der Versions-Explorer.
Begründung & Zuweisungs-Evidenz
Cited verbatim in the snippet (deterministic citation).
Dokumenten-Herkunft & Rückverfolgbarkeit
| Spezifikations-Dokument | SWS_COMManager.pdf |
|---|---|
| Dokumentseite | Seite 84 |
| Ziel-Modul | comm (classic) |
| Ziel-Anforderung | SWS_ComM_01105 |
| Semantische Rolle | constitutive |
| Automatisierungs-Konfidenz | 0.95 |