SNIP_CLASSIC_ECUM_SECTION_8_3_3_4_EcuM_RequestPOST_RUN

8.3.3.4 EcuM_RequestPOST_RUN [SWS_EcuM_04128] Definition of API function EcuM_RequestPOST_RUN Upstream requirements: SRS_ModeMgm_00009 ⌈ Service Name EcuM_RequestPOST_RUN Syntax Std_ReturnType EcuM_RequestPOST_RUN ( EcuM_UserType user ) Service ID [hex] 0x0a Sync/Async Synchronous Reentrancy Reentrant Parameters (in) user ID of the entity requesting the POST RUN state. Parameters (inout) None Parameters (out) None Return value Std_ReturnType E_OK: The request was accepted by EcuM E_NOT_OK: The request was not accepted by EcuM Description Places a request for the POST RUN state. Requests can be placed by every user made known to the state manager at configuration time. Requests for RUN and POST RUN must be tracked independently (in other words: two independent variables). The service is intended for implementing AUTOSAR ports. Available via EcuM.h ⌋ [SWS_EcuM_03025] Upstream requirements: SRS_ModeMgm_00009, , SRS_BSW_00350 ⌈If EcuMDevErrorDetect is enabled and there are multiple requests by the same user detected by EcuM_RequestPOST_RUN the function shall report ECUM_E_MULTIPLE_RUN_REQUESTS to Det.⌋ All requirements of 8.3.3.2 EcuM_RequestRUN apply accordingly to the function Ecu M_RequestPOST_RUN. Configuration of EcuM_RequestPOST_RUN: Refer to EcuM_UserType for more information about user IDs and their generation.