AUTOSAR Classic System Services
Die System Services steuern den gesamten ECU-Lebenszyklus von Power-On über Wakeup, Betriebszustände, Modus-Arbitrierung (BswM) bis zum sicheren Herunterfahren und Programmlauf-Überwachung (WdgM).
Mapa de temas
BswM
35EcuM
65HTMSS
10SwCluC
47WdgM
19No hay datos de elementos para esta versión
Arti
Returns the version information of this module.
void Arti_GetVersionInfo(Std_VersionInfoType* VersionInfoPtr);Service to initialize the ARTI module
void Arti_Init(void);BswM
Function called by the Bsw M when a Bsw MUser Callout is executed. The function name and all function parameters are defined b y the Bsw MUser Callout Function configuration parameter. Any return values are ignored by the Bsw M.
void <BswMUserCalloutFunction> (implementation_specific -);Function called by Restart Task if the partition containing the Bsw M has been restarted.
void BswM_BswMPartitionRestarted (void);Function called by Can SM to indicate its current state. Ava ilable via Bsw M_ Can SM.h
void BswM_CanSM_CurrentState (NetworkHandleType Network, CanSM_BswMCurrentStateType CurrentState);Function called by Com M to indicate the current communication mode of a Com M channel.
void BswM_ComM_CurrentMode (NetworkHandleType Network, ComM_ModeType RequestedMode);Function is called by Com M to indicate the current mode of the PNC. AUTOSAR CP R20 - of Document ID : AUTOSAR_SWS_BSWModeManager
void BswM_ComM_CurrentPNCMode (PNCHandleType PNC, ComM_PncModeType CurrentPncMode);Function is called by Com M to signal a shutdown.
void BswM_ComM_InitiateReset (void);This function is called by the DCM in order to report an updated application.
void BswM_Dcm_ApplicationUpdated (void);Function called by DCM to inform the Bsw M about the current state of the communication mode.
void BswM_Dcm_CommunicationMode_CurrentState (NetworkHandleType Network, Dcm_CommunicationModeType RequestedMode);Deinitializes the BSW Mode Manager.
void BswM_Deinit (void);Function called Ecu M to indicate the current ECU Operation Mode.
void BswM_EcuM_CurrentState (EcuM_StateType CurrentState);Function called by Ecu M to indicate the current state of a wakeup source.
void BswM_EcuM_CurrentWakeup (EcuM_WakeupSourceType source, EcuM_WakeupStatusType state);Function called by Ecu M notify about current Status of the Run Request Protocol.
void BswM_EcuM_RequestedState (EcuM_StateType State, EcuM_RunStatusType CurrentState);Function called by Eth If to indicate the link state change of a certain Ethernet switch port group.
void BswM_EthIf_PortGroupLinkStateChg (EthIf_SwitchPortGroupIdxType PortGroupIdx, EthTrcv_LinkStateType PortGroupState);Function called by Eth SM to indicate its current state.
void BswM_EthSM_CurrentState (NetworkHandleType Network, EthSM_NetworkModeStateType CurrentState);Function called by Fr SM to indicate its current state.
void BswM_FrSM_CurrentState (NetworkHandleType Network, FrSM_BswM_StateType CurrentState);Returns the version information of this module.
void BswM_GetVersionInfo (Std_VersionInfoType* VersionInfo);Initializes the BSW Mode Manager.
void BswM_Init (const BswM_ConfigType* ConfigPtr);This API tells the Bsw M the desired communication status of the available networks. The status will typically be activated via COM I - PDU group switches.
void BswM_J1939DcmBroadcastStatus (uint16 NetworkMask);Notification of current J1939Nm state after state changes. AUTOSAR CP R20 - of Document ID : AUTOSAR_SWS_BSWModeManager
void BswM_J1939Nm_StateChangeNotification (NetworkHandleType Network, uint8 Node, Nm_StateType NmState);Function called by Lin SM to indicate the currently active schedule table for a specific LIN channel.
void BswM_LinSM_CurrentSchedule (NetworkHandleType Network, LinIf_SchHandleType CurrentSchedule);Function called by Lin SM to indicate its current state.
void BswM_LinSM_CurrentState (NetworkHandleType Network, LinSM_ModeType CurrentState);Function called by Lin TP to request a mode for the corresponding LIN channel. The Lin Tp_ Mode correlates to the LIN schedule table that should be used.
void BswM_LinTp_RequestMode (NetworkHandleType Network, LinTp_Mode LinTpRequestedMode);Main function of the Bsw M
void BswM_MainFunction (void);Function called by Nm to indicate a Car Wakeup.
void BswM_Nm_CarWakeUpIndication (NetworkHandleType Network);Notification of current Nm state after state changes.
void BswM_Nm_StateChangeNotification (NetworkHandleType Network, Nm_StateType currentState);Function called by Nv M to indicate the current block mode of an Nv M block.
void BswM_NvM_CurrentBlockMode (NvM_BlockIdType Block, NvM_RequestResultType CurrentBlockMode);Function called by Nv M to inform the Bsw M about the current state of a multi block job.
void BswM_NvM_CurrentJobMode (NvM_MultiBlockRequestType MultiBlockRequest, NvM_RequestResultType CurrentJobMode);Generic function call to request modes. This function shall only be used by other BSW modules that does not have a specific mode request interface.
void BswM_RequestMode (BswM_UserType requesting_user, BswM_ModeType requested_mode);Function called by Service Discovery to indicate current state of the Client Service (available/ down).
void BswM_Sd_ClientServiceCurrentState (uint16 SdClientServiceHandleId, Sd_ClientServiceCurrentStateType CurrentClientState);Function called by Service Discovery to indicate current status of the Consumed Eventgroup (available/ down).
void BswM_Sd_ConsumedEventGroupCurrentState (uint16 SdConsumedEventGroupHandleId, Sd_ConsumedEventGroupCurrentStateType ConsumedEventGroupState);Function called by Service Discovery to indicate current status of the Event Handler (requested/ released).
void BswM_Sd_EventHandlerCurrentState (uint16 SdEventHandlerHandleId, Sd_EventHandlerCurrentStateType EventHandlerStatus);Function called by Wdg M to request a partition reset.
void BswM_WdgM_RequestPartitionReset (ApplicationType Application);This structure contains all post - build configurable parameters of the BSW Mode AUTOSAR CP R20 - of Document ID : AUTOSAR_SWS_BSWModeManager Manager. A pointer to this structure is passed to the BSW Mode Manager initialization function for configuration.
This type identifies the modes that can be requested by Bsw M Users.
This type identifies a Bsw M User that makes mode requests to the Bsw M.
EcuM
Ecum_AbortWakeupAlarm aborts the wakeup alarm previously set by this user. EcuM_Abort WakeupAlarm is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_AbortWakeupAlarm (EcuM_UserType user);This callout shall provide driver initialization and other hardware-related startup activities in case of a power on reset.
void EcuM_AL_DriverInitOne (void);This callout shall provide driver initialization and other hardware-related startup activities for loading the post-build configuration data. Beware: Here only pre-compile and link-time configurable modules may be used.
void EcuM_AL_DriverInitZero (void);This callout shall provide driver initialization and other hardware-related startup activities in the wakeup case.
void EcuM_AL_DriverRestart (void);This callout shall take the code for resetting the ECU.
void EcuM_AL_Reset (EcuM_ResetType reset);If the configuration parameter EcuMSetProgrammableInterrupts is set to true, this callout Ecu M_AL_SetProgrammableInterrupts is executed and shall set the interrupts on ECUs with programmable interrupts.
void EcuM_AL_SetProgrammableInterrupts (void);This callout shall take the code for shutting off the power supply of the ECU. If the ECU cannot unpower itself, a reset may be an adequate reaction.
void EcuM_AL_SwitchOff (void);This callout is intended to provide a RAM integrity test. The goal of this test is to ensure that after a long SLEEP duration, RAM contents is still consistent. The check does not need to be exhaustive since this would consume quite some processing time during wakeups. A well designed check will execute quickly and detect RAM integrity defects with a sufficient probability. This specification does not make any assumption about the algorithm chosen for a particular ECU. The areas of RAM which will be checked have to be chosen carefully. It depends on the check algorithm itself and the task structure. Stack contents of the task executing the RAM check e.g. very likely cannot be checked. It is good practice to have the hash generation and checking in the same task and that this task is not preemptible and that there is only little activity between hash generation and hash check. The RAM check itself is provided by the system designer. In case of applied multi core and existence of Satellite-Ecu M(s): this API will be called by the Master-EcuM only.
uint8 EcuM_CheckRamHash (void);This callout is called by the EcuM to validate a wakeup source. If a valid wakeup has been detected, it shall be reported to EcuM via EcuM_ValidateWakeupEvent().
void EcuM_CheckValidation (EcuM_WakeupSourceType wakeupSource);This callout is called by the EcuM to poll a wakeup source. It shall also be called by the ISR of a wakeup source to set up the PLL and check other wakeup sources that may be connected to the same interrupt.
void EcuM_CheckWakeup (EcuM_WakeupSourceType wakeupSource);Clears wakeup events.
void EcuM_ClearWakeupEvent (EcuM_WakeupSourceType sources);This callout should evaluate some condition, like port pin or NVRAM value, to determine which post-build configuration shall be used in the remainder of the startup process. It shall load this configuration data into a piece of memory that is accessible by all BSW modules and shall return a pointer to the EcuM post-build configuration as a base for all BSW module post-build configrations.
const EcuM_ConfigType* EcuM_DeterminePbConfiguration (void);The ECU Manager Module calls EcuM_DisableWakeupSources to set the wakeup source(s) defined in the wakeupSource bitfield so that they are not able to wake the ECU up.
void EcuM_DisableWakeupSources (EcuM_WakeupSourceType wakeupSource);The ECU Manager Module calls EcuM_EnableWakeupSource to allow the system designer to notify wakeup sources defined in the wakeupSource bitfield that SLEEP will be entered and to adjust their source accordingly.
void EcuM_EnableWakeupSources (EcuM_WakeupSourceType wakeupSource);This API is called by any SW Module whose wakeup source is checked asynchronously (e.g. asynchronous Can Trcv Driver) and the Check of the Wakeup returns a negative Result (no Wakeup by this Source). The API cancels the CheckWakeupTimer for the WakeupSource. If the correponding CheckWakeupTimer is canceled the check of this wakeup source is finished.
void EcuM_EndCheckWakeup (EcuM_WakeupSourceType WakeupSource);The ECU State Manager will call the error hook if the error codes "ECUM_E_RAM_CHECK_ FAILED" or "ECUM_E_CONFIGURATION_DATA_INCONSISTENT" occur. In this situation it is not possible to continue processing and the ECU must be stopped. The integrator may choose the modality how the ECU is stopped, i.e. reset, halt, restart, safe state etc.
void EcuM_ErrorHook (uint16 reason);see EcuM_CheckRamHash
void EcuM_GenerateRamHash (void);EcuM_GetBootTarget returns the current boot target - see EcuM_SelectBootTarget. EcuM_Get BootTarget is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_GetBootTarget (EcuM_BootTargetType* target);EcuM_GetCurrentTime returns the current value of the EcuM clock (i.e. the time since battery connect). EcuM_GetCurrentTime is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_GetCurrentTime (EcuM_TimeType* time);Gets expired wakeup events.
EcuM_WakeupSourceType EcuM_GetExpiredWakeupEvents (void);EcuM_GetLastShutdownTarget returns the shutdown target of the previous shutdown process. EcuM_GetLastShutdownTarget is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_GetLastShutdownTarget (EcuM_ShutdownTargetType* shutdownTarget, EcuM_ShutdownModeType* shutdownMode);Gets pending wakeup events.
EcuM_WakeupSourceType EcuM_GetPendingWakeupEvents (void);EcuM_GetShutdownCause returns the selected shutdown cause as set by EcuM_Select ShutdownCause. EcuM_GetShutdownCause is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_GetShutdownCause (EcuM_ShutdownCauseType* shutdownCause);EcuM_GetShutdownTarget returns the currently selected shutdown target as set by EcuM_ SelectShutdownTarget. EcuM_GetShutdownTarget is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_GetShutdownTarget (EcuM_ShutdownTargetType* shutdownTarget, EcuM_ShutdownModeType* shutdownMode);Gets validated wakeup events.
EcuM_WakeupSourceType EcuM_GetValidatedWakeupEvents (void);Returns the version information of this module.
void EcuM_GetVersionInfo (Std_VersionInfoType* versioninfo);EcuM_GetWakeupTime returns the current value of the master alarm clock (the minimum absolute time of all user alarm clocks). EcuM_GetWakeupTime is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_GetWakeupTime (EcuM_TimeType* time);Instructs the ECU State Manager module to go into a sleep mode, Reset or OFF depending on the previously selected shutdown target.
Std_ReturnType EcuM_GoDownHaltPoll (EcuM_UserType UserID);Initializes the ECU state manager and carries out the startup procedure. The function will never return (it calls StartOS)
void EcuM_Init (void);If the configuration parameter EcuMResetLoopDetection is set to true, this callout EcuM_Loop Detection is called on every startup.
void EcuM_LoopDetection (void);The purpose of this service is to implement all activities of the ECU State Manager while the OS is up and running.
void EcuM_MainFunction (void);This call allows the system designer to notify that the GO OFF I state is about to be entered.
void EcuM_OnGoOffOne (void);This call allows the system designer to notify that the GO OFF II state is about to be entered.
void EcuM_OnGoOffTwo (void);Releases a POST RUN request previously done with a call to EcuM_RequestPOST_RUN. The service is intended for implementing AUTOSAR ports.
Std_ReturnType EcuM_ReleasePOST_RUN (EcuM_UserType user);Releases a RUN request previously done with a call to EcuM_RequestRUN. The service is intended for implementing AUTOSAR ports.
Std_ReturnType EcuM_ReleaseRUN (EcuM_UserType user);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.
Std_ReturnType EcuM_RequestPOST_RUN (EcuM_UserType user);Places a request for the RUN state. Requests can be placed by every user made known to the state manager at configuration time.
Std_ReturnType EcuM_RequestRUN (EcuM_UserType user);EcuM_SelectBootTarget selects a boot target. EcuM_SelectBootTarget is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_SelectBootTarget (EcuM_BootTargetType target);EcuM_SelectShutdownCause elects the cause for a shutdown. EcuM_SelectShutdownCause is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_SelectShutdownCause (EcuM_ShutdownCauseType target);EcuM_SelectShutdownTarget selects the shutdown target. EcuM_SelectShutdownTarget is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_SelectShutdownTarget (EcuM_ShutdownTargetType shutdownTarget, EcuM_ShutdownModeType shutdownMode);EcuM_SetAbsWakeupAlarm sets the user's wakeup alarm to an absolute point in time. EcuM_ SetAbsWakeupAlarm is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_SetAbsWakeupAlarm (EcuM_UserType user, EcuM_TimeType time);EcuM_SetClock sets the EcuM clock time to the provided value. This API is useful for testing the alarm services; Alarms that take days to expire can be tested. EcuM_SetClock is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_SetClock (EcuM_UserType user, EcuM_TimeType time);EcuM_SetRelWakeupAlarm sets a user's wakeup alarm relative to the current point in time. EcuM_SetRelWakeupAlarm is part of the ECU Manager Module port interface.
Std_ReturnType EcuM_SetRelWakeupAlarm (EcuM_UserType user, EcuM_TimeType time);Function called by BswM to notify about State Switch.
void EcuM_SetState (EcuM_StateType state);Sets the wakeup event.
void EcuM_SetWakeupEvent (EcuM_WakeupSourceType sources);Typically called from the shutdown hook, this function takes over execution control and will carry out GO OFF II activities.
void EcuM_Shutdown (void);This callout is invoked periodically in all reduced clock sleep modes. It is explicitely allowed to poll wakeup sources from this callout and to call wakeup notification functions to indicate the end of the sleep state to the ECU State Manager.
void EcuM_SleepActivity (void);This API is called by the ECU Firmware to start the CheckWakeupTimer for the corresponding WakeupSource. If EcuMCheckWakeupTimeout > 0 the CheckWakeupTimer for the Wakeup Source is started. If EcuMCheckWakeupTimeout <= 0 the API call is ignored by the EcuM.
void EcuM_StartCheckWakeup (EcuM_WakeupSourceType WakeupSource);This function implements the STARTUP II state.
void EcuM_StartupTwo (void);The callout shall start the given wakeup source(s) so that they are ready to perform wakeup validation.
void EcuM_StartWakeupSources (EcuM_WakeupSourceType wakeupSource);The callout shall stop the given wakeup source(s) after unsuccessful wakeup validation.
void EcuM_StopWakeupSources (EcuM_WakeupSourceType wakeupSource);After wakeup, the ECU State Manager will stop the process during the WAKEUP VALIDATION state/sequence to wait for validation of the wakeup event.This API service is used to indicate to the ECU Manager module that the wakeup events indicated in the sources parameter have been validated.
void EcuM_ValidateWakeupEvent (EcuM_WakeupSourceType sources);
A pointer to such a structure shall be provided to the ECU State Manager initialization routine for configuration.
This type describes the reset mechanisms supported by the ECU State Manager. It can be extended by configuration.
Result of the Run Request Protocol sent to BswM
This type describes the cause for a shutdown by the ECU State Manager. It can be extended by configuration.
This data type represents the modes of the ECU Manager module.
ECU State Manager states.
This data type represents the time of the ECU Manager module.
Unique value for each user.
EcuM_WakeupSourceType defines a bitfield with 5 pre-defined positions (see Range). The bitfield provides one bit for each wakeup source. In WAKEUP, all bits cleared indicates that no wakeup source is known. In STARTUP, all bits cleared indicates that no reason for restart or reset is known. In this case, ECUM_WKSOURCE_RESET shall be assumed.
The type describes the possible states of a wakeup source.
HTMSS
-
void HTMSS_GetVersionInfo(Std_VersionInfoType* versioninfo);Initializes the HTMSS module
void HTMSS_Init(const HTMSS_TestCfgType* ConfigPtr);The ECU State Manager will call the error hook if the HTMSS provided shutdown test results have a failure. In this situation, the integrator has to control the CPU processing based on the system requirements, i.e. reset, safe state etc...
void HTMSS_ShutdownTestErrorHook(void);Starts the MSTP configured tests
Std_ReturnType HTMSS_StartTest(HTMSS_TestGroupType GrpId);The ECU State Manager will call the error hook if the HTMSS provided startup test results have a failure. In this situation, the integrator has to control the CPU processing based on the system requirements, i.e. reset, safe state etc...
void HTMSS_StartupTestErrorHook(void);Returns current test status on requested test
HTMSS_TestStatusType HTMSS_GetTestStatus(HTMSS_TestGroupType GrpId, HTMSS_TestResultType* RequestTestResultPtr);Configuration data structure of HTMSS module
HTMSS_ Test Group Type describes the test group type Variation --
It describes the current test result Variation --
HTMSS_ Test Status Type describes status of test.
SwCluC
Returns the number of actually used - and thereby connected - handle sets Tags: atp.Status=draft
SwCluC_BManif_HandleIndexType SwCluC_BManif_GetNoOfHandleSets_< Resource Entry Group>_<Resource Entry>(void);Returns the number of actually used - and thereby connected - handle sets. Tags: atp.Status=draft
SwCluC_BManif_HandleIndexType SwCluC_BManif_GetNoOfHandleSets_< Resource Entry Group>(SwCluC_BManif_TableIndexType resIndex);Returns the Id of the connected Software Cluster for a Notifier Handle of a Provide Resource Entry or Provide Handle of a Require Resource Entry Tags: atp.Status=draft
SwCluC_BManif_SwClusterIdType SwCluC_BManif_GetConSwClusterId_< ResourceEntryGroup>_<Handle>(SwCluC_BManif_TableIndexType resIndex, SwCluC_BManif_HandleIndexType notifierSetIndex);Returns the Id of the connected Software Cluster for a Notifier Handle of a Provide Resource Entry or a Provide Handle of a Require Resource Entry Tags: atp.Status=draft
SwCluC_BManif_SwClusterIdType SwCluC_BManif_GetConSwClusterId_< ResourceEntryGroup>_<ResourceEntry>_<Handle>(SwCluC_BManif_HandleIndexType notifierSetIndex);Returns the Id of the connected Software Cluster for a Notifier Handle of a Provide Resource Entry or a Provide Handle of a Require Resource Entry Tags: atp.Status=draft
<handleType> SwCluC_BManif_GetHandle_<ResourceEntryGroup>_<Handle>(SwCluC_BManif_TableIndexType resIndex, SwCluC_BManif_HandleIndexType notifierSetIndex);Returns a handle of a Resource Entry in a Resource Entry Group Tags: atp.Status=draft
<handleType> SwCluC_BManif_GetHandle_<ResourceEntryGroup>_< ResourceEntry>_<Handle>(SwCluC_BManif_HandleIndexType notifierSetIndex);Returns the value of the Subscribed Interface Validity Marker. Tags: atp.Status=draft
uint32 SwCluC_BManif_GetValidityMarker(void);This callback function indicates that the signal of the primitive data item/event is ready for reception. It is an implementation of a <ComUser_CbkRxAck> callback. Tags: atp.Status=draft
void SwCluC_ComProxy_<BS>_CbkRxAck(CbkHandleIdType ComUserCbkHandleId);This function is called to acquire the transmit data of an I-PDU segment (N-PDU). Each call to this function provides the next part of the I-PDU data unless retry->TpDataState is TP_ DATARETRY. In this case the function restarts to copy the data beginning at the offset from the current position indicated by retry->TxTpDataCnt. The size of the remaining data is written to the position indicated by availableDataPtr Tags: atp.Status=draft
BufReq_ReturnType SwCluC_ComProxy_<BS>_ComCbkCopyTxData(CbkHandleIdType ComUserCbkHandleId, const PduInfoType* info, const RetryInfoType* retry, PduLengthType* availableDataPtr);This callback function indicates that COM has received a signal and parsed it as "invalid". It is an implementation of a <ComUser_CbkInv> callback. Tags: atp.Status=draft
void SwCluC_ComProxy_<BS>_COMCbkInv(CbkHandleIdType ComUserCbkHandleId);Indication of a received PDU from a lower layer communication interface module. Tags: atp.Status=draft
void SwCluC_ComProxy_<BS>_ComCbkRxIndication(CbkHandleIdType ComUserCbkHandleId, const PduInfoType* PduInfoPtr);This callback function indicates that the aliveTimeout after the last successful reception of the signal of the data item/event has expired (data element outdated). It is an implementation of a <ComUser_CbkRxTOut> callback. Tags: atp.Status=draft
void SwCluC_ComProxy_<BS>_COMCbkRxTOut(CbkHandleIdType ComUserCbkHandleId);This callback function indicates that the signal of the data item/event is already handed over by COM to the PDU router. It is an implementation of a <ComUser_CbkTxAck> callback. Tags: atp.Status=draft
void SwCluC_ComProxy_<BS>_COMCbkTAck(CbkHandleIdType ComUserCbkHandleId);This callback function indicates that an error occurred when the signal of the data item/event was handed over by COM to the PDU router. It is an implementation of a <ComUser_CbkTx Err> callback. Tags: atp.Status=draft
void SwCluC_ComProxy_<BS>_COMCbkTErr(CbkHandleIdType ComUserCbkHandleId);Called after an I-PDU has been received via the TP API, the result indicates whether the transmission was successful or not. Tags: atp.Status=draft
void SwCluC_ComProxy_<BS>_ComCbkTpRxIndication(CbkHandleIdType ComUserCbkHandleId, Std_ReturnType result);Within this API, the upper layer module (called module) shall check whether the available data fits into the buffer size reported by PduInfoPtr->SduLength. If it fits, it shall copy its data into the buffer provided by PduInfoPtr->SduDataPtr and update the length of the actual copied data in PduInfoPtr->SduLength. If not, it returns E_NOT_OK without changing PduInfoPtr. Tags: atp.Status=draft
Std_ReturnType SwCluC_ComProxy_<BS>_ComCbkTriggerTransmit(CbkHandleIdType ComUserCbkHandleId, PduInfoType* PduInfoPtr);The lower layer communication interface module confirms the transmission of a PDU, or the failure to transmit a PDU. Tags: atp.Status=draft
void SwCluC_ComProxy_<BS>_ComCbkTxConfirmation(CbkHandleIdType ComUserCbkHandleId, Std_ReturnType result);This callback function indicates that the timeout of TransmissionAcknowledgementRequest for sending the signal of the data item/event has expired. It is an implementation of a <ComUser_ CbkTxTOut> callback. Tags: atp.Status=draft
void SwCluC_ComProxy_<BS>_COMCbkTxTOut(CbkHandleIdType ComUserCbkHandleId);SwCluC_ComProxy_Init is intended to allocate and initialize system resources used by the ComProxy linked to this specific socked. Tags: atp.Status=draft
void SwCluC_ComProxy_Init_<SwCluCComBaseSocket>(void);SwCluC_DcmProxy_Init is intended to allocate and initialize system resources used by the DCM Proxy linked to this specific socked. Tags: atp.Status=draft
void SwCluC_DcmProxy_Init_<SwCluCDcmBaseSocket>(void);SwCluC_DemProxy_Init is intended to allocate and initialize system resources used by the DEM Proxy linked to this specific socked. Tags: atp.Status=draft
void SwCluC_DemProxy_Init_<SwCluCDemBaseSocket>(void);SwCluC_FiMProxy_Init is intended to allocate and initialize system resources used by the FiM Proxy linked to this specific socked. Tags: atp.Status=draft
void SwCluC_FiMProxy_Init_<SwCluCFiMBaseSocket>(void);This function is called to provide the received data of an I-PDU segment (N-PDU) to the upper layer. Each call to this function provides the next part of the I-PDU data. The size of the remaining data is written to the position indicated by bufferSizePtr. Tags: atp.Status=draft
BufReq_ReturnType SwCluC_LdComProxy_<BS>_LdComCbkCopyRxData(CbkHandleIdType LdComUserCbkHandleId, const PduInfoType* info, PduLengthType* bufferSizePtr);This function is called to acquire the transmit data of an I-PDU segment (N-PDU). Each call to this function provides the next part of the I-PDU data unless retry->TpDataState is TP_ DATARETRY. In this case the function restarts to copy the data beginning at the offset from the current position indicated by retry->TxTpDataCnt. The size of the remaining data is written to the position indicated by availableDataPtr Tags: atp.Status=draft
BufReq_ReturnType SwCluC_LdComProxy_<BS>_LdComCbkCopyTxData(CbkHandleIdType LdComUserCbkHandleId, const PduInfoType* info, const RetryInfoType* retry, PduLengthType* availableDataPtr);Indication of a received PDU from a lower layer communication interface module. Tags: atp.Status=draft
void SwCluC_LdComProxy_<BS>_LdComCbkRxIndication(CbkHandleIdType LdComUserCbkHandleId, const PduInfoType* PduInfoPtr);This function is called at the start of receiving an N-SDU. The N-SDU might be fragmented into multiple N-PDUs (FF with one or more following CFs) or might consist of a single N-PDU (SF). The service shall provide the currently available maximum buffer size when invoked with TpSdu Length equal to 0. Tags: atp.Status=draft
BufReq_ReturnType SwCluC_LdComProxy_<BS>_LdComCbkStartOfReception(CbkHandleIdType LdComUserCbkHandleId, const PduInfoType* info, PduLengthType TpSduLength, PduLengthType* bufferSizePtr);Called after an I-PDU has been received via the TP API, the result indicates whether the transmission was successful or not. Tags: atp.Status=draft
void SwCluC_LdComProxy_<BS>_LdComCbkTpRxIndication(CbkHandleIdType LdComUserCbkHandleId, Std_ReturnType result);This function is called after a Signal has been transmitted via the TP-API on its network. Tags: atp.Status=draft
void SwCluC_LdComProxy_<BS>_LdComCbkTpTxConfirmation(CbkHandleIdType LdComUserCbkHandleId, Std_ReturnType result);Within this API, the upper layer module (called module) shall check whether the available data fits into the buffer size reported by PduInfoPtr->SduLength. If it fits, it shall copy its data into the buffer provided by PduInfoPtr->SduDataPtr and update the length of the actual copied data in PduInfoPtr->SduLength. If not, it returns E_NOT_OK without changing PduInfoPtr. Tags: atp.Status=draft
Std_ReturnType SwCluC_LdComProxy_<BS>_LdComCbkTriggerTransmit(CbkHandleIdType LdComUserCbkHandleId, PduInfoType* PduInfoPtr);The lower layer communication interface module confirms the transmission of a PDU, or the failure to transmit a PDU. Tags: atp.Status=draft
void SwCluC_LdComProxy_<BS>_LdComCbkTxConfirmation(CbkHandleIdType LdComUserCbkHandleId, Std_ReturnType result);SwCluC_LdComProxy_Init is intended to allocate and initialize system resources used by the LdComProxy linked to this specific socked. Tags: atp.Status=draft
void SwCluC_LdComProxy_Init_<SwCluCLdComBaseSocket>(void);SwCluC_NvMProxy_Init is intended to allocate and initialize system resources used by the Nv MProxy linked to this specific socked. Tags: atp.Status=draft
void SwCluC_NvMProxy_Init_<SwCluCNvMBaseSocket>(void);This function informs the NvM proxy of the SwCluC about the end of the NvM_ReadAll job.
void SwCluC_NvMProxy_MultiBlockReadAllJobFinished(void);SwCluC_OsProxy_Init is intended to allocate and initialize system resources used by the Os Proxy linked to this specific socked Tags: atp.Status=draft
void SwCluC_OsProxy_Init_<SwCluCOsProxyOsBaseSocket>(void);SwCluC_Xcc_Init is intended to allocate and initialize system resources used by the Software Cluster Connection. It initializes interface memory which might be needed to be read by other Software Clusters but it is not allowed to do any read access to memory of any another Software Cluster. Tags: atp.Status=draft
void SwCluC_Xcc_Init1(void);SwCluC_Xcc_Init2 is intended to allocate and initialize system resources used by the Software Cluster Connection. It can execute initializations which require a read access to interface memory of another Software Clusters. Tags: atp.Status=draft
void SwCluC_Xcc_Init2(void);Type to code control flags for the connection process. Bit 0..14 are reserved. Tags: atp.Status=draft
Type for the global ID value of a resource Tags: atp.Status=draft
Index type to address a set of handles in the immutable and modifiable interface table Tags: atp.Status=draft
Tags: atp.Status=draft
Type for the global ID value of a resource Tags: atp.Status=draft
Type for the guard value of a resource Tags: atp.Status=draft
Type to code the properties of a resource. Bit 0..5 are reserved. Tags: atp.Status=draft
Type to code the type of a resource Tags: atp.Status=draft
Type of the Software Cluster's ID value Tags: atp.Status=draft
Index type to address the immutable and modifiable interface table Tags: atp.Status=draft
Generic function pointer type according C default type for functions Tags: atp.Status=draft
WdgM
Indicates to the Watchdog Manager that a Checkpoint within a Supervised Entity has been reached.
Std_ReturnType WdgM_CheckpointReached (WdgM_SupervisedEntityIdType SEID, WdgM_CheckpointIdType CheckpointID);De - initializes the Watchdog Manager.
void WdgM_DeInit (void);Returns SEID that first reached the stat e WDGM_ LOCAL_ STATUS_ EXPIRED.
Std_ReturnType WdgM_GetFirstExpiredSEID (WdgM_SupervisedEntityIdType* SEID);Returns the global supervision status of the Watchdog Manager.
Std_ReturnType WdgM_GetGlobalStatus (WdgM_GlobalStatusType* Status);Returns the supervision status of an individual Supervised Entity.
Std_ReturnType WdgM_GetLocalStatus (WdgM_SupervisedEntityIdType SEID, WdgM_LocalStatusType* Status);Returns the current mode of the Watchdog Manager.
Std_ReturnType WdgM_GetMode (WdgM_ModeType* Mode);Returns the version information of this module.
void WdgM_GetVersionInfo (Std_VersionInfoType* VersionInfo);Initializes the Watchdog Manager.
void WdgM_Init (const WdgM_ConfigType* ConfigPtr);Performs the processing of the cyclic Watchdog Manager jobs.
void WdgM_MainFunction (void);Instructs the Watchdog Manager to cause a watchdog reset.
void WdgM_PerformReset (void);Sets the current mode of Watchdog Manager.
Std_ReturnType WdgM_SetMode (WdgM_ModeType Mode);-
This type identifies a Checkpoint in the context of a Supervised Entity for the Watchdog Manager. Note that an individual Checkpoint can only be identified by the pair of Supervised Entity ID and Checkpoint ID.
This structure contains all post - build configurable parameters of the Watchdog Manager. A pointer to this structure is passed to the Watchdog Manager initialization function for configuration. AUTOSAR CP R20 - of D ocument ID : AUTOSAR_SWS_WatchdogManager
This type shall be used for variables that represent the global supervision status of the Watchdog Manager module.
This type shall be used for variables that represent the current status of supervision for individual Supervised Entitie s.
The category of Mode Declaration Group Wdg M_ Mode is EXPLICIT_ ORDER, The attribute value for the Mode Declaration are set as following: "SUPERVISION_ OK" = 0 "SUPERVISION_ FAILED" = 1 "SUPERVISION_ EXPIRED" = 2 "SUPERVISION_ STOPPED" = 3 "SUP ERVISION_ DEACTIVATED" = 4 The on Transition Value is defined as 255
This type distinguishes the different modes that were configured for the Watchdog Manager.
This type identifies an individual Supervised Entity for the Watchdog Manager.
Guía del clústerGENERADO POR IA
Coordina los ciclos de vida de las ECU, arbitra modos de funcionamiento y garantiza la supervisión funcional por watchdog.
Coordina los ciclos de vida de las ECU, arbitra modos de funcionamiento y garantiza la supervisión funcional por watchdog.
El clúster de módulos System Services controla el ciclo de vida de la ECU desde las fases tempranas de arranque hasta el apagado, arbitra modos de funcionamiento y asegura la supervisión de la ejecución del programa para cumplir los requisitos de seguridad funcional SafetyConceptStatusReport p. 15. El ECU State Manager agrupa las solicitudes de modo y delega las decisiones de estado en el BSW Mode Manager, mientras que el Watchdog Manager monitoriza la ejecución y comanda el Watchdog Driver SWS_ECUStateManager p. 103. En caso de violaciones graves del flujo de control, el clúster detiene el servicio al watchdog y fuerza un reinicio de hardware seguro [SWS_WdgM_00232].
El clúster de módulos System Services controla el ciclo de vida de la ECU, conmuta modos de funcionamiento y asegura la supervisión de la ejecución del programa conforme a los requisitos de seguridad funcional SafetyConceptStatusReport p. 15. El BSW Mode Manager (BswM) actúa como instancia de decisión central, mientras que el ECU State Manager (EcuM) coordina fases específicas de hardware como StartPreOS, Sleep y Shutdown y propaga solicitudes al BswM SWS_ECUStateManager p. 103. La supervisión de la ejecución del programa se implementa mediante el Watchdog Manager (WdgM), que realiza supervisiones Alive, Deadline y de flujo de control, y dispara el hardware a través del Watchdog Driver (Wdg) [SWS_Wdg_00155].
Diagrama de contexto: arquitectura y colaboración de los System Services con BSW, RTE y hardware. Fuentes: SWS_ECUStateManager p. 34, AUTOSAR_EXP_ModeManagementGuide p. 61.
Durante el funcionamiento continuo, solicitudes como RUN o POST_RUN se recopilan en el EcuM, el cual las notifica de forma agregada al BswM [SWS_BswM_91004]. Tras evaluar las reglas configuradas, el BswM establece el estado mediante EcuM_SetState, lo cual se notifica a los componentes a través de la RTE [SWS_EcuM_04116]. En las fases de reposo, los eventos de despertar se procesan mediante una máquina de estados estandarizada (NONE, PENDING, VALIDATED, EXPIRED) y se señalan sincrónicamente al BswM [SWS_BswM_00131].
Diagrama de secuencias: ruta de interacción de ECU Mode Handling entre SW-C, EcuM, BswM y RTE. Fuentes: SWS_ECUStateManager p. 103, ModeManagementGuide p. 34.
Si se produce un error crítico de supervisión en el WdgM, el estado de supervisión cambia a WDGM_GLOBAL_STATUS_STOPPED, tras lo cual se detiene el disparo del watchdog y el hardware provoca un reinicio del sistema [SWS_WdgM_00232]. El clúster notifica los errores de configuración o de invocación de forma estandarizada al Default Error Tracer (Det) [SWS_EcuM_03026].
1. Arquitectura del sistema y rol del clúster de módulos
El clúster de módulos System Services constituye la columna vertebral funcional de la AUTOSAR Classic Platform. Comprende el BSW Mode Manager (BswM), el ECU State Manager (EcuM), el Watchdog Manager (WdgM) y el hardware cercano Watchdog Driver (Wdg) SWS_ECUStateManager p. 35. Conjuntamente, estos módulos controlan el ciclo de vida integral de la ECU, coordinan los modos de funcionamiento cercanos al hardware y aplicativos, y garantizan la supervisión temporal y lógica de la ejecución del programa para asegurar la seguridad funcional SafetyConceptStatusReport p. 15.
En la arquitectura en capas de AUTOSAR, BswM, EcuM y WdgM se ubican en la capa de System Services por encima de las capas de abstracción y controladores, mientras que el Watchdog Driver (Wdg), como parte del Microcontroller Abstraction Layer (MCAL), atiende los registros de hardware del temporizador de watchdog [SWS_Wdg_00106]. El EcuM actúa en su variante flexible (EcuM Flex) como nexo con el hardware para secuencias tempranas de arranque y tardías de desconexión antes o después del inicio del sistema operativo. Ya no posee una máquina de estados compleja propia para modos de aplicación, sino que delega el arbitraje de modos en el BswM SWS_ECUStateManager p. 103. Estándares externos de diagnóstico como UDS (ISO 14229) y protocolos de Network Management se acoplan directamente a la evaluación de reglas del BswM a través de interfaces BSW definidas (como el servicio 0x28 CommunicationControl mediante Dcm) [SWS_BswM_00048].
Diagrama de contexto: arquitectura y colaboración de los System Services con BSW, RTE y hardware. Fuentes: SWS_ECUStateManager p. 34, AUTOSAR_EXP_ModeManagementGuide p. 61.
2. Interacción y rutas de comunicación entre los módulos
La interacción dentro del clúster se caracteriza por relaciones de control y notificación claramente delimitadas. En el marco del ECU Mode Handling, el EcuM recibe solicitudes para estados como RUN o POST_RUN procedentes de componentes de software (SW-Cs) y reenvía el resultado de arbitraje agregado mediante [SWS_BswM_91004] al BswM ModeManagementGuide p. 34. Dado que el EcuM no toma decisiones de transición propias, el BswM evalúa reglas lógicas configuradas e instruye el estado de destino sincrónicamente mediante EcuM_SetState [SWS_EcuM_04116]. A continuación, el EcuM refleja este estado a la aplicación a través de la RTE y confirma al BswM el estado de ejecución actual mediante BswM_EcuM_CurrentState [SWS_BswM_91003].
Una ruta de interacción paralela conecta BswM, WdgM y Wdg. Componentes de software y módulos BSW notifican la llegada a puntos de control definidos al WdgM, el cual determina a partir de ello el estado de supervisión local y global SWS_WatchdogManager p. 51. El WdgM pone a disposición las modificaciones de estado de la supervisión local a través de puertos de modo proporcionados [SWS_WdgM_00148]. En función del estado del sistema de orden superior, el BswM cambia el modo de funcionamiento del Watchdog Manager mediante WdgM_SetMode [SWS_WdgM_00154]. Acto seguido, el WdgM configura el Watchdog Driver (Wdg) a través de la Watchdog Interface (WdgIf) y controla el disparo del hardware mediante Wdg_SetTriggerCondition [SWS_Wdg_00155].
Diagrama de secuencias: ruta de interacción de ECU Mode Handling entre SW-C, EcuM, BswM y RTE. Fuentes: SWS_ECUStateManager p. 103, ModeManagementGuide p. 34.
3. Sincronización, reentrancia y contextos de tareas
La ejecución de los System Services se distribuye de forma determinista entre niveles de tareas periódicas, retrollamadas asíncronas y contextos de interrupción. La carga periódica principal de la gestión de modos la soporta BswM_MainFunction, que se invoca en el contexto de una tarea del sistema operativo mediante el BSW Scheduler (SchM) y procesa todas las reglas cuya evaluación deba diferirse [SWS_BswM_00053]. Si se producen eventos con evaluación inmediata de reglas, estos se procesan sincrónicamente de forma directa en el contexto de la indicación BSW o de la API de la SW-C invocadora ModemanagementGuide p. 31.
En sistemas multinúcleo, la normalización exige una asignación estricta de recursos. BswM_Init está diseñado de forma condicionalmente reentrante para permitir instanciaciones separadas por partición o núcleo de procesador [SWS_BswM_00002]. Durante las fases de reposo y retención, el EcuM reserva recursos del sistema operativo propios del núcleo (RES_AUTOSAR_ECUM_<core#>) para asegurar la sincronización entre núcleos maestro y esclavo [SWS_EcuM_03010]. La inicialización de controladores mediante EcuM_AL_DriverInitZero y EcuM_AL_DriverInitOne se invoca por separado en cada núcleo e inicializa exclusivamente módulos MCAL locales del núcleo [SWS_EcuM_04145]. El borrado de eventos de despertar mediante EcuM_ClearWakeupEvent es explícitamente no interrumpible y puede realizarse tanto desde contextos de tarea como de interrupción [SWS_EcuM_02807].
4. Ciclos de vida típicos y modos de funcionamiento
El ciclo de vida de una ECU se divide normativamente en las fases STARTUP, UP, SHUTDOWN y SLEEP [SWS_EcuM_91005]. La fase STARTUP comienza antes del inicio del sistema operativo en la secuencia StartPreOS con la invocación de EcuM_Init, la evaluación de la causa del reinicio y la carga de la configuración post-build mediante EcuM_DeterminePbConfiguration AUTOSAR_SWS_ECUStateManager p. 38. Tras transferir el control al sistema operativo mediante StartOS, el EcuM inicializa en StartPostOS el SchM y el BswM [SWS_EcuM_02934]. A continuación, el BswM asume el control e inicia los módulos BSW restantes así como la aplicación.
Durante el funcionamiento continuo (fase UP), EcuM y BswM gestionan los modos RUN y POST_RUN, así como el servicio opcional Alarm Clock SWS_ECUStateManager p. 75. Al cambiar al estado de reposo (SLEEP), el clúster distingue estructuralmente entre HALT (detiene la CPU) y POLL (frecuencia de reloj de CPU reducida) SWS_ECUStateManager p. 54. Previamente, la invocación WdgM_DeInit desinicializa el Watchdog Manager y adapta los tiempos de espera de disparo para evitar reinicios no deseados durante el apagado [SWS_WdgM_00261]. En la secuencia de sondeo, el EcuM se bloquea en un bucle de comprobación con llamadas periódicas de EcuM_SleepActivity y EcuM_CheckWakeupHook hasta que se detecta un evento de despertar [SWS_EcuM_03020].
Los eventos de despertar detectados pasan por una estricta gestión de estados desde ECUM_WKSTATUS_NONE a través de PENDING hasta VALIDATED o EXPIRED [SWS_EcuM_04091]. El EcuM señala sincrónicamente cada cambio de estado mediante BswM_EcuM_CurrentWakeup al BswM [SWS_BswM_00131]. La validación de despertar protege frente a perturbaciones transitorias del bus y monitoriza la ventana temporal mediante temporizadores de validación configurables [SWS_EcuM_04004]. Si el ciclo de vida concluye en SHUTDOWN, OffPreOS desactiva el BswM y SchM antes de que OffPostOS reinicie la ECU o la desenergice mediante callouts de integración como EcuM_AL_Reset o EcuM_AL_SwitchOff AUTOSAR_SWS_ECUStateManager p. 49.
Diagrama de estados: máquina de estados de fuentes de despertar del EcuM con notificación al BswM. Fuentes: AUTOSAR_SWS_ECUStateManager p. 60, [SWS_EcuM_04091].
5. Tratamiento de errores, rastreo de DET y degradación
Para la detección de errores de tiempo de ejecución y configuración, el clúster integra mecanismos de notificación estandarizados al Default Error Tracer (Det). Si una entidad intenta emitir una liberación mediante EcuM_ReleasePOST_RUN sin una solicitud previa, el EcuM notifica el error de desarrollo ECUM_E_MISMATCHED_RUN_RELEASE al Det [SWS_EcuM_03026]. Las solicitudes múltiples de un mismo usuario se registran con ECUM_E_MULTIPLE_RUN_REQUESTS [SWS_EcuM_03025]. Asimismo, el WdgM monitoriza las llamadas a la API en estado no inicializado y notifica WDGM_E_UNINIT en caso de que se invoquen servicios antes de completar la inicialización [SWS_WdgM_00288].
La supervisión de seguridad se fundamenta en el control funcional de tres etapas del WdgM (Alive Supervision, Deadline Supervision y supervisión lógica del flujo de control) SafetyConceptStatusReport p. 47. Si un fallo de supervisión provoca la superación de las tolerancias de error, el estado de supervisión global cambia de WDGM_GLOBAL_STATUS_OK a través de FAILED hacia WDGM_GLOBAL_STATUS_EXPIRED y, finalmente, STOPPED [SWS_WdgM_00387]. En este estado, el WdgM establece la condición de disparo en 0 para todos los controladores de watchdog, con lo que el watchdog de hardware reinicia de inmediato el microcontrolador [SWS_WdgM_00232]. Para reinicios de emergencia controlados, el WdgM proporciona el servicio WdgM_PerformReset, que detiene el redisparo continuo y fuerza el reinicio de hardware [SWS_WdgM_00264]. Para la protección tras fases de reposo prolongadas, el EcuM comprueba además mediante EcuM_CheckRamHash la consistencia de la memoria volátil para interceptar reinicios erróneos en caso de corrupción de la RAM [SWS_EcuM_02921].
Esta guía se basa en las especificaciones de AUTOSAR Classic Platform R20-11 y resume la arquitectura y los mecanismos del clúster de módulos System Services.
Module im Cluster
AUTOSAR Run-Time Interface (Arti)
AUTOSAR Classic System Services-Modul AUTOSAR Run-Time Interface (Arti, Spezifikation: AUTOSAR_CP_SWS_ARTI.pdf, AUTOSAR_SWS_ClassicPlatformARTI.pdf).
BSW Mode Manager (BswM)
Arbitrates mode requests and executes action lists to control system state transitions.
ECU State Manager (EcuM)
Controls ECU lifecycle states: Startup, Run, PostRun, Sleep, and Shutdown.
HW Test Manager on Startup and Shutdown (HTMSS)
AUTOSAR Classic System Services-Modul HW Test Manager on Startup and Shutdown (HTMSS, Spezifikation: AUTOSAR_CP_SWS_HWTestManager.pdf, AUTOSAR_SWS_HWTestManager.pdf).
BSW Scheduler Module (SchM)
AUTOSAR Classic System Services-Modul BSW Scheduler Module (SchM, Spezifikation: AUTOSAR_SWS_BSW_Scheduler.pdf).
Software Cluster Connection (SwCluC)
AUTOSAR Classic System Services-Modul Software Cluster Connection (SwCluC, Spezifikation: AUTOSAR_CP_SWS_SoftwareClusterConnection.pdf, AUTOSAR_SWS_SoftwareClusterConnection.pdf).
Watchdog Manager (WdgM)
Performs alive supervision, deadline supervision, and logical program flow monitoring.
gemini-3.8-flash-low· 2026-10-13 · Original en alemán