DEENESPTFRRUARHIKOZHNL

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).

主题图

SwCluC

47
<Resource Entry Group><Resource Entry Group>#2SwCluC_BManif_GetConSwClusterId_ResourceEntryGroup_HandleSwCluC_BManif_GetConSwClusterId_ResourceEntryGroup_ResourceEntry_HandleSwCluC_BManif_GetHandle_ResourceEntryGroup_HandleSwCluC_BManif_GetHandle_ResourceEntryGroup_ResourceEntry_HandleSwCluC_BManif_GetValidityMarkerSwCluC_ComProxy_BS_CbkRxAckSwCluC_ComProxy_BS_ComCbkCopyTxDataSwCluC_ComProxy_BS_COMCbkInvSwCluC_ComProxy_BS_ComCbkRxIndicationSwCluC_ComProxy_BS_COMCbkRxTOutSwCluC_ComProxy_BS_COMCbkTAckSwCluC_ComProxy_BS_COMCbkTErrSwCluC_ComProxy_BS_ComCbkTpRxIndicationSwCluC_ComProxy_BS_ComCbkTriggerTransmitSwCluC_ComProxy_BS_ComCbkTxConfirmationSwCluC_ComProxy_BS_COMCbkTxTOutSwCluC_ComProxy_Init_SwCluCComBaseSocketSwCluC_DcmProxy_Init_SwCluCDcmBaseSocketSwCluC_DemProxy_Init_SwCluCDemBaseSocketSwCluC_FiMProxy_Init_SwCluCFiMBaseSocketSwCluC_LdComProxy_BS_LdComCbkCopyRxDataSwCluC_LdComProxy_BS_LdComCbkCopyTxDataSwCluC_LdComProxy_BS_LdComCbkRxIndicationSwCluC_LdComProxy_BS_LdComCbkStartOfReceptionSwCluC_LdComProxy_BS_LdComCbkTpRxIndicationSwCluC_LdComProxy_BS_LdComCbkTpTxConfirmationSwCluC_LdComProxy_BS_LdComCbkTriggerTransmitSwCluC_LdComProxy_BS_LdComCbkTxConfirmationSwCluC_LdComProxy_Init_SwCluCLdComBaseSocketSwCluC_NvMProxy_Init_SwCluCNvMBaseSocketSwCluC_NvMProxy_MultiBlockReadAllJobFinishedSwCluC_OsProxy_Init_SwCluCOsProxyOsBaseSocketSwCluC_Xcc_Init1SwCluC_Xcc_Init2SwCluC_BManif_ConCtrlTypeSwCluC_BManif_GlobalResourceIdTypeSwCluC_BManif_HandleIndexTypeSwCluC_BManif_HeaderTypeSwCluC_BManif_MachineIdTypeSwCluC_BManif_ResourceGuardValueTypeSwCluC_BManif_ResourcePropertiesTypeSwCluC_BManif_ResourceTypeSwCluC_BManif_SwClusterIdTypeSwCluC_BManif_TableIndexTypeSwCluC_BManif_VoidFncPtrType

详细视图

请在大纲中选择一个条目。

Arti

Returns the version information of this module.

void Arti_GetVersionInfo(Std_VersionInfoType* VersionInfoPtr);
Arti_Init 函数

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);
BswM_Init 函数

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);
EcuM_Init 函数

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.

EcuM_Mode 类型

–

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);
HTMSS_Init 函数

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);
WdgM_Init 函数

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);
globalmode 类型

-

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.

WdgM_Mode 类型

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.

集群指南人工智能生成

协调 ECU 生命周期,仲裁运行模式,并确保功能性看门狗监控。
AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: 8ad3210909f6 来源 未决问题(1)
因果锚点:R20-11 自 R20-11 起有效 为此规范版本重新合成。
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

协调 ECU 生命周期,仲裁运行模式,并确保功能性看门狗监控。

System Services 模块集群控制 ECU 从早期启动阶段到 Shutdown 的生命周期,仲裁运行模式,并提供程序执行监控以满足功能安全要求 SafetyConceptStatusReport 第15页。ECU State Manager 汇总模式请求并将状态决策委托给 BSW Mode Manager,而 Watchdog Manager 则监控执行并控制 Watchdog Driver SWS_ECUStateManager 第103页。在发生严重控制流违规时,该集群停止对看门狗的喂狗操作并强制执行安全的硬件复位 [SWS_WdgM_00232]。

模块集群 System Services 控制 ECU 的生命周期,切换运行模式,并根据功能安全要求保障程序执行监控 SafetyConceptStatusReport 第15页。BSW Mode Manager(BswM)充当中央决策实例,而 ECU State Manager(EcuM)协调硬件特定阶段(如 StartPreOS、Sleep 和 Shutdown)并将请求传播给 BswM SWS_ECUStateManager 第103页。程序执行监控由 Watchdog Manager(WdgM)实现,它执行 Alive 监控、Deadline 监控和控制流监控,并通过 Watchdog Driver(Wdg)触发硬件 [SWS_Wdg_00155]。

SystemServicesArch SWC Application Layer (SW-Cs / CDDs) RTE Runtime Environment (RTE) SWC->RTE EcuM ECU State Manager (EcuM) RTE->EcuM RUN / POST_RUN Request WdgM Watchdog Manager (WdgM) RTE->WdgM Checkpoint Reached BswM BSW Mode Manager (BswM) BswM->EcuM State Setting EcuM_SetState BswM->WdgM Mode Change WdgM_SetMode EcuM->BswM Arbitrated State BswM_EcuM_RequestedState OS Operating System & SchM (Os / SchM) EcuM->OS StartOS / SchM_Init Wdg Watchdog Driver (Wdg MCAL) WdgM->Wdg Trigger Condition Wdg_SetTriggerCondition HW Hardware / Peripherals (MCU / Watchdog Timer) Wdg->HW Hardware Servicing / Reset

上下文图:System Services 与 BSW、RTE 及硬件的架构与协作。来源:SWS_ECUStateManager 第34页,AUTOSAR_EXP_ModeManagementGuide 第61页。

在运行过程中,诸如 RUN 或 POST_RUN 的请求汇集在 EcuM 中,后者将其汇总后报告给 BswM [SWS_BswM_91004]。在评估配置的规则后,BswM 通过 EcuM_SetState 设置状态,该状态通过 RTE 通知给各组件 [SWS_EcuM_04116]。在休眠阶段,唤醒事件通过标准化的状态机(NONE、PENDING、VALIDATED、EXPIRED)进行处理,并同步指示给 BswM [SWS_BswM_00131]。

ECU Mode Handling SequenzSW-CRTEEcuMBswMUse Case: Modusanforderung durch Software-KomponenteRte_Call_RequestRUN()EcuM_RequestRUN(User)Arbitrierung aller aktiven BenutzeranforderungenBswM_EcuM_RequestedState(ECUM_STATE_APP_RUN)Use Case: 规则评估与模式切换评估 BswMRules 与 ActionListsEcuM_SetState(ECUM_STATE_APP_RUN)Rte_Switch_currentMode(RUN)向 Runnables 确认模式BswM_EcuM_CurrentState(ECUM_STATE_APP_RUN)

时序图:SW-C、EcuM、BswM 与 RTE 之间的 ECU Mode Handling 交互路径。来源:SWS_ECUStateManager 第103页,ModeManagementGuide 第34页。

若在 WdgM 中发生严重监控错误,监控状态会切换为 WDGM_GLOBAL_STATUS_STOPPED,随后停止看门狗触发,硬件引发系统复位 [SWS_WdgM_00232]。该集群以标准化方式向 Default Error Tracer(Det)报告配置或调用错误 [SWS_EcuM_03026]。

1. 系统架构与模块群集的作用

模块集群 System Services 构成 AUTOSAR Classic Platform 的功能骨干。它包括 BSW Mode Manager(BswM)、ECU State Manager(EcuM)、Watchdog Manager(WdgM)以及底层 Watchdog Driver(Wdg)SWS_ECUStateManager 第35页。这些模块共同控制 ECU 的完整生命周期,协调底层硬件以及应用运行模式,并确保用于保障功能安全的时间和逻辑程序执行监控 SafetyConceptStatusReport 第15页。

在 AUTOSAR 分层架构中,BswM、EcuM 和 WdgM 位于抽象层和驱动层之上的 System Services 层,而 Watchdog Driver(Wdg)作为 Microcontroller Abstraction Layer(MCAL)的一部分操作看门狗定时器的硬件寄存器 [SWS_Wdg_00106]。其中,EcuM 在灵活形态(EcuM Flex)下充当操作系统启动前或启动后与硬件在早期启动和后期关断序列中的纽带。它不再具有用于应用模式的独立复杂状态机,而是将模式仲裁委托给 BswM SWS_ECUStateManager 第103页。外部诊断标准(如 ISO 14229 的 UDS)和网络管理协议通过定义的 BSW 接口(例如经由 Dcm 的服务 0x28 CommunicationControl)直接接入 BswM 的规则评估中 [SWS_BswM_00048]。

SystemServicesArch SWC Application Layer (SW-Cs / CDDs) RTE Runtime Environment (RTE) SWC->RTE EcuM ECU State Manager (EcuM) RTE->EcuM RUN / POST_RUN Request WdgM Watchdog Manager (WdgM) RTE->WdgM Checkpoint Reached BswM BSW Mode Manager (BswM) BswM->EcuM State Setting EcuM_SetState BswM->WdgM Mode Change WdgM_SetMode EcuM->BswM Arbitrated State BswM_EcuM_RequestedState OS Operating System & SchM (Os / SchM) EcuM->OS StartOS / SchM_Init Wdg Watchdog Driver (Wdg MCAL) WdgM->Wdg Trigger Condition Wdg_SetTriggerCondition HW Hardware / Peripherals (MCU / Watchdog Timer) Wdg->HW Hardware Servicing / Reset

上下文图:System Services 与 BSW、RTE 及硬件的架构与协作。来源:SWS_ECUStateManager 第34页,AUTOSAR_EXP_ModeManagementGuide 第61页。

2. 模块间的相互协作与交互路径

集群内部的交互具有明确划分的控制和报告关系。在 ECU Mode Handling 范围内,EcuM 从软件组件(SW-C)接收诸如 RUN 或 POST_RUN 等状态的请求,并通过 [SWS_BswM_91004] 将汇总的仲裁结果转发给 BswM ModeManagementGuide 第34页。由于 EcuM 本身不做出转换决策,BswM 评估配置的逻辑规则,并通过 EcuM_SetState 同步下发目标状态指令给 [SWS_EcuM_04116]。随后 EcuM 通过 RTE 将该状态反映给应用程序,并通过 BswM_EcuM_CurrentState 向 BswM 确认当前执行状态 [SWS_BswM_91003]。

一条并行的交互路径连接 BswM、WdgM 和 Wdg。软件组件和 BSW 模块将达到已定义检查点的情况报告给 WdgM,后者据此确定局部和全局监控状态 SWS_WatchdogManager 第51页。WdgM 通过提供的模式端口提供局部监控的状态变化 [SWS_WdgM_00148]。BswM 根据上级系统状态通过 WdgM_SetMode 切换看门狗管理器的运行模式 [SWS_WdgM_00154]。随后 WdgM 通过看门狗接口(WdgIf)配置看门狗驱动程序(Wdg),并通过 Wdg_SetTriggerCondition 控制硬件触发 [SWS_Wdg_00155]。

ECU Mode Handling SequenzSW-CRTEEcuMBswMUse Case: Modusanforderung durch Software-KomponenteRte_Call_RequestRUN()EcuM_RequestRUN(User)Arbitrierung aller aktiven BenutzeranforderungenBswM_EcuM_RequestedState(ECUM_STATE_APP_RUN)Use Case: 规则评估与模式切换评估 BswMRules 与 ActionListsEcuM_SetState(ECUM_STATE_APP_RUN)Rte_Switch_currentMode(RUN)向 Runnables 确认模式BswM_EcuM_CurrentState(ECUM_STATE_APP_RUN)

时序图:SW-C、EcuM、BswM 与 RTE 之间的 ECU Mode Handling 交互路径。来源:SWS_ECUStateManager 第103页,ModeManagementGuide 第34页。

3. 同步、可重入性与任务上下文

System Services 的执行确定性地分布在周期性任务级别、异步回调和中断上下文中。模式管理的主要周期性负载由 BswM_MainFunction 承担,它在 OS 任务上下文中由 BSW Scheduler(SchM)调用,并处理所有需要延迟评估的规则 [SWS_BswM_00053]。若出现需立即评估规则的事件,则直接在调用方 BSW 指示或 SW-C API 上下文中同步处理 ModemanagementGuide 第31页。

在多核系统中,规范要求对资源进行严格分配。BswM_Init 被设计为条件可重入,以支持每个分区或处理器内核的独立实例化 [SWS_BswM_00002]。在休眠和保持阶段,EcuM 保留核独占的 OS 资源(RES_AUTOSAR_ECUM_<core#>),以确保主核与从核之间的同步 [SWS_EcuM_03010]。通过 EcuM_AL_DriverInitZero 和 EcuM_AL_DriverInitOne 进行的驱动程序初始化在每个核上分别调用,且仅初始化核本地的 MCAL 模块 [SWS_EcuM_04145]。通过 EcuM_ClearWakeupEvent 清除唤醒事件显式为不可中断的,且允许从任务上下文和中断上下文发起 [SWS_EcuM_02807]。

4. 典型生命周期与运行模式

ECU 的生命周期在规范上划分为 STARTUP、UP、SHUTDOWN 和 SLEEP 阶段 [SWS_EcuM_91005]。STARTUP 阶段在操作系统启动前于序列 StartPreOS 中开始,伴随 EcuM_Init 的调用、复位原因评估以及通过 EcuM_DeterminePbConfiguration 加载 Post-Build 配置 AUTOSAR_SWS_ECUStateManager 第38页。通过 StartOS 将控制权移交给操作系统后,EcuM 在 StartPostOS 中初始化 SchM 以及 BswM [SWS_EcuM_02934]。随后 BswM 接管控制权并启动其余的 BSW 模块以及应用程序。

在运行状态(UP 阶段)下,EcuM 和 BswM 管理模式 RUN 和 POST_RUN 以及可选的 Alarm Clock 服务 SWS_ECUStateManager 第75页。在切换至休眠状态(SLEEP)时,集群在结构上区分 HALT(停止 CPU)和 POLL(降低 CPU 时钟)SWS_ECUStateManager 第54页。在此之前,调用 WdgM_DeInit 会去初始化 Watchdog Manager 并调整触发超时,以防止在关机过程中发生意外复位 [SWS_WdgM_00261]。在轮询序列中,EcuM 会阻塞在带有周期性调用 EcuM_SleepActivity 和 EcuM_CheckWakeupHook 的检查循环中,直到检测到唤醒事件 [SWS_EcuM_03020]。

检测到的唤醒事件经历从 ECUM_WKSTATUS_NONE 到 PENDING,再到 VALIDATED 或 EXPIRED 的严格状态管理 [SWS_EcuM_04091]。EcuM 通过 BswM_EcuM_CurrentWakeup 将每次状态变更同步指示给 BswM [SWS_BswM_00131]。唤醒验证可防止瞬态总线干扰,并通过可配置的验证定时器监控时间窗口 [SWS_EcuM_04004]。若生命周期在 SHUTDOWN 中结束,OffPreOS 会停用 BswM 和 SchM,随后 OffPostOS 通过诸如 EcuM_AL_Reset 或 EcuM_AL_SwitchOff 等集成标注(callout)复位 ECU 或切断电源 AUTOSAR_SWS_ECUStateManager 第49页。

WakeupSourceStates Init NONE ECUM_WKSTATUS_NONE entry / BswM_EcuM_CurrentWakeup(NONE) Init->NONE Power On PENDING ECUM_WKSTATUS_PENDING entry / BswM_EcuM_CurrentWakeup(PENDING) entry / EcuM_StartWakeupSources() NONE->PENDING EcuM_SetWakeupEvent [Validierung erforderlich] VALIDATED ECUM_WKSTATUS_VALIDATED entry / BswM_EcuM_CurrentWakeup(VALIDATED) entry / ComM_EcuM_WakeUpIndication() NONE->VALIDATED EcuM_SetWakeupEvent [无验证] PENDING->VALIDATED EcuM_ValidateWakeupEvent EXPIRED ECUM_WKSTATUS_EXPIRED entry / BswM_EcuM_CurrentWakeup(EXPIRED) entry / EcuM_StopWakeupSources() PENDING->EXPIRED Validierungs-Timeout abgelaufen VALIDATED->NONE EcuM_ClearWakeupEvent EXPIRED->NONE EcuM_ClearWakeupEvent

状态图:EcuM 的唤醒源状态机及向 BswM 的通知。来源:AUTOSAR_SWS_ECUStateManager 第60页,[SWS_EcuM_04091]。

5. 错误处理、DET 跟踪与降级

为了检测运行时和配置错误,该集群集成了向 Default Error Tracer(Det)的标准报告机制。若某个实体尝试通过 EcuM_ReleasePOST_RUN 发起未经事先请求的释放,EcuM 会向 Det 报告开发错误 ECUM_E_MISMATCHED_RUN_RELEASE [SWS_EcuM_03026]。同一用户的重复请求由 ECUM_E_MULTIPLE_RUN_REQUESTS 捕获 [SWS_EcuM_03025]。同样,WdgM 监控未初始化状态下的 API 调用,并在初始化完成前调用服务时报告 WDGM_E_UNINIT [SWS_WdgM_00288]。

安全监控基于 WdgM 的三级功能检查(Alive Supervision、Deadline Supervision 和逻辑控制流监控)SafetyConceptStatusReport 第47页。如果监控错误导致违反容错限制,全局监控状态会从 WDGM_GLOBAL_STATUS_OK 经由 FAILED 变为 WDGM_GLOBAL_STATUS_EXPIRED,最终变为 STOPPED [SWS_WdgM_00387]。在此状态下,WdgM 将所有看门狗驱动程序的触发条件设置为 0,从而使硬件看门狗立即复位微控制器 [SWS_WdgM_00232]。对于受控的紧急复位,WdgM 提供服务 WdgM_PerformReset,该服务停止持续补喂看门狗并强制执行硬件复位 [SWS_WdgM_00264]。为了在较长的休眠阶段后提供安全防护,EcuM 还通过 EcuM_CheckRamHash 检查易失性存储器的一致性,以拦截在 RAM 损坏时的异常重启 [SWS_EcuM_02921]。

本指南基于 AUTOSAR Classic Platform R20-11 规范,总结了 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 ID 5 2 APIs (2 Funktionen, 0 Typen) #include "Arti.h"

BSW Mode Manager (BswM)

Arbitrates mode requests and executes action lists to control system state transitions.

BSW ID 42 35 APIs (32 Funktionen, 3 Typen) #include "BswM.h"

ECU State Manager (EcuM)

Controls ECU lifecycle states: Startup, Run, PostRun, Sleep, and Shutdown.

BSW ID 10 65 APIs (52 Funktionen, 13 Typen) #include "EcuM.h"

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 ID 17 6 APIs (6 Funktionen, 0 Typen) #include "HTMSS.h"

BSW Scheduler Module (SchM)

AUTOSAR Classic System Services-Modul BSW Scheduler Module (SchM, Spezifikation: AUTOSAR_SWS_BSW_Scheduler.pdf).

BSW ID 130 Keine C-API · 0 Records #include "SchM.h"

Software Cluster Connection (SwCluC)

AUTOSAR Classic System Services-Modul Software Cluster Connection (SwCluC, Spezifikation: AUTOSAR_CP_SWS_SoftwareClusterConnection.pdf, AUTOSAR_SWS_SoftwareClusterConnection.pdf).

BSW ID 16 36 APIs (36 Funktionen, 0 Typen) #include "SwCluC.h"

Watchdog Manager (WdgM)

Performs alive supervision, deadline supervision, and logical program flow monitoring.

BSW ID 13 19 APIs (11 Funktionen, 8 Typen) #include "WdgM.h"