DEENESPTFRRUARHIKOZHNL
CLASSIC Modul: fr Rolle: constitutive Konfidenz: 95%

SNIP_CLASSIC_FR_SECTION_8_4_3_Fr_StartCommunication

Quelle: SWS_FlexRayDriver.pdf (Seite 42) • Ziel-Anforderung: SWS_Std_00005

Wortlaut

8.4.3 Fr_StartCommunication [SWS_Fr_00010] Definition of API function Fr_StartCommunication Upstream requirements: SRS_Fr_05109 ⌈ Service Name Fr_StartCommunication Syntax Std_ReturnType Fr_StartCommunication ( uint8 Fr_CtrlIdx ) Service ID [hex] 0x03 Sync/Async Asynchronous Reentrancy Non Reentrant for the same device Parameters (in) Fr_CtrlIdx Index of FlexRay CC within the context of the FlexRay Driver. Parameters (inout) None Parameters (out) None Return value Std_ReturnType E_OK: API call finished successfully. E_NOT_OK: API call aborted due to errors. Description Starts communication. Available via Fr.h ⌋ Note: The Fr module’s environment shall only call the function Fr_StartCommunication() when CC Fr_CtrlIdx is in POCState ’POC:ready’. [SWS_Fr_00177] ⌈The function Fr_StartCommunication() shall perform the following tasks on FlexRay CC Fr_CtrIdx: 1. Invoke the CC CHI command ’RUN’, which initiates the startup procedure within the FlexRay CC. 2. Return E_OK. ⌋ The function call of Fr_StartCommunication() changes the CC POCState to POC:startup which is a transitional state. In the case when communication startup succeeds, the CC wil change the POCState to ’POC:normal active’ or ’POC:normal passive’. It is not guaranteed that the FlexRay CC will reside in the ’POC:normal active’ or ’POC:normal passive’ state after a call of the function Fr_StartCommunication(). [SWS_Fr_00176] ⌈If the function Fr_StartCommunication() is able to and detects a hardware error while performing the requested functionality, then it shall call Dem_SetEventStatus() (FR_E_CTRL_TESTRESULT, DEM_EVENT_STATUS_FAILED) and return E_NOT_OK.⌋ [SWS_Fr_00173] ⌈If development error detection for the Fr module is enabled, and if the function Fr_StartCommunication() is called before successful initialization of the Fr, then the function Fr_StartCommunication() shall raise the development error FR_E_INIT_FAILED.⌋ [SWS_Fr_00174] ⌈If development error detection for the Fr module is enabled, and the function Fr_StartCommunication() shall check the validity of the parameter Fr_CtrlIdx. If Fr_CtrlIdx is invalid, then the function Fr_StartCommunication() shall raise the development error FR_E_INV_CTRL_IDX.⌋ [SWS_Fr_00175] ⌈The function Fr_StartCommunication() shall check whether the CC Fr_CtrlIdx’s POCState is in POC:ready. If the POCState is not POC:ready, then the function Fr_StartCommunication() shall raise the runtime error FR_E_INV_POCSTATE.⌋

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_FlexRayDriver.pdf
Dokumentseite Seite 42
Ziel-Modul fr (classic)
Ziel-Anforderung SWS_Std_00005
Semantische Rolle constitutive
Automatisierungs-Konfidenz 0.95