AUTOSAR Classic CAN
Das CAN-Cluster (Controller Area Network) stellt hardwarenahe Treiber, standardisierte Hardware-Abstraktion (CanIf), State-Management und ISO 15765-2 Transportprotokolle (CanTp) für klassische CAN-, CAN FD- und CAN XL-Netzwerke bereit.
Mapa de temas
Can
27CanIf
50CanNm
29CanSM
24CanTp
12CanTrcv
23Ttcan
26TtcanIf
36Não há dados de elementos para esta versão
Can
-
boolean <LPDU_CalloutName> (uint8 Hrh, Can_IdType CanId, uint8 CanDataLegth, const uint8* CanSduPtr);This function checks if a wakeup has occurred for the given controller.
Std_ReturnType Can_CheckWakeup (uint8 Controller);This function de - initializes the module.
void Can_DeInit (void);This function disables all interrupts for this CAN controller.
void Can_DisableControllerInterrupts (uint8 Controller);This function enables all allowed interrupts.
void Can_EnableControllerInterrupts (uint8 Controller);This service obtains the error state of the CAN controller.
Std_ReturnType Can_GetControllerErrorState (uint8 ControllerId, Can_ErrorStateType* ErrorStatePtr);This service reports about the current status of the requested CAN controller.
Std_ReturnType Can_GetControllerMode (uint8 Controller, Can_ControllerStateType* ControllerModePtr);Returns the Rx error counter for a CAN controller. This value might not be available for all CAN controllers, in which cas e E_ NOT_ OK would be returned. Please note that the value of the counter might not be correct at the moment the API returns it, because the Rx counter is handled asynchronously in hardware. Applications should not trust this value for any assumption about the current bus state.
Std_ReturnType Can_GetControllerRxErrorCounter (uint8 ControllerId, uint8* RxErrorCounterPtr);Returns the Tx error counter for a CAN controller. This value might not be available for all CAN controllers, in which case E_ NOT_ OK would be returned. Please note that the value of the counter might not be correct at the moment the API returns it, because the Tx counter is handled asynchronously in hardware. Applications should not trust this value for any assumption about the current bus state.
Std_ReturnType Can_GetControllerTxErrorCounter (uint8 ControllerId, uint8* TxErrorCounterPtr);This function returns the version information of this module.
void Can_GetVersionInfo (Std_VersionInfoType* versioninfo);This function initializes the module.
void Can_Init (const Can_ConfigType* Config);This function performs the polling of bus - off events that are configured statically as 'to be polled'.
void Can_MainFunction_BusOff (void);This function performs the polling of CAN controller mode transitions.
void Can_MainFunction_Mode (void);This function performs the polling of RX indications when CAN_ RX_ PROCESSING is set to POLLING.
void Can_MainFunction_Read (void);This function performs the polling of wake - up events that are configured statically as 'to be polled'.
void Can_MainFunction_Wakeup (void);This function performs the polling of TX confirmation when CAN_ TX_ PROCESSING is set to POLLING.
void Can_MainFunction_Write (void);This service shall set the baud rate configuration of the CAN controller. Depending on necessary baud rate modifications the controller might have to reset.
Std_ReturnType Can_SetBaudrate (uint8 Controller, uint16 BaudRateConfig ID); ⚠️This function performs software triggered state transitions of the CAN controller State machine.
Std_ReturnType Can_SetControllerMode (uint8 Controller, Can_ControllerStateType Transition);This function is called by Can If to pass a CAN message to Can Drv for transmission.
Std_ReturnType Can_Write (Can_HwHandleType Hth, const Can_PduType* PduInfo);This is the type of the external data structure containing the overall initialization data for the CAN driver and SFR settings affecting all controllers. Furthermore it contains pointers to controller configuration structures. The contents of the initializ ation data structure are CAN hardware specific.
States that are used by the several Controller Mode functions.
Error states of a CAN controller.
The enumeration represents a superset of CAN Error Types which typical CAN HW is able to report. That means not all CAN HW will be able to support the complete set.
Represents the hardware object handles of a CAN hardware unit. For CAN hardware units with more than 255 HW objects use extended range.
This type defines a data structure which clearly provides an Hardware Object Handle including its corresponding CAN Controller and therefore Can Drv as well as the specific Can Id.
Represents the Identifier of an L - PDU. The two most significant bits specify the frame type: 00 CAN message with Standard CAN ID 01 CAN FD frame with Standard CAN ID 10 CAN message with Extended CAN ID 11 CAN FD frame with Extended CAN ID
This type unites Pdu Id (sw Pdu Handle), Sdu Length (length), Sdu Data (sdu), and Can Id (id) for any CAN L - SDU.
CanIf
This service indicates that the wake up flag in the CAN transceiver is set. This function is called in CanIf_CheckTrcvWakeFlagIndication.
void <User_CheckTrcvWakeFlagIndication> (uint8 TransceiverId);This service indicates that the CAN transceiver has cleared the WufFlag. This function is called in CanIf_ClearTrcvWufFlagIndication.
void <User_ClearTrcvWufFlagIndication> (uint8 TransceiverId);This service indicates that the CAN transceiver is running in PN communication mode.
void <User_ConfirmPnAvailability> (uint8 TransceiverId);This service indicates a bus-off event to the corresponding upper layer module (mainly the CAN State Manager module).
void <User_ControllerBusOff> (uint8 ControllerId);This service indicates a CAN controller state transition to the corresponding upper layer module (mainly the CAN State Manager module).
void <User_ControllerModeIndication> (uint8 ControllerId, Can_ControllerStateType ControllerMode);Indication of a received PDU from a lower layer communication interface module.
void <User_RxIndication> (PduIdType RxPduId, const PduInfoType* PduInfoPtr);This service indicates a CAN transceiver state transition to the corresponding upper layer module (mainly the CAN State Manager module).
void <User_TrcvModeIndication> (uint8 TransceiverId, CanTrcv_TrcvModeType TransceiverMode);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.
Std_ReturnType <User_TriggerTransmit> (PduIdType TxPduId, PduInfoType* PduInfoPtr);The lower layer communication interface module confirms the transmission of a PDU, or the failure to transmit a PDU.
void <User_TxConfirmation> (PduIdType TxPduId, Std_ReturnType result);This service indicates if a wake up event initiated from the wake up source (CAN controller or transceiver) after a former request to the CAN Driver or CAN Transceiver Driver module is valid.
void <User_ValidateWakeupEvent> (EcuM_WakeupSourceType sources);Requests the CanIf module to check the Wake flag of the designated CAN transceiver.
Std_ReturnType CanIf_CheckTrcvWakeFlag (uint8 TransceiverId);This service indicates that the check of the transceiver's wake-up flag has been finished by the corresponding CAN transceiver with the abstract CanIf TransceiverId. This indication is used to cope with the asynchronous transceiver communication.
void CanIf_CheckTrcvWakeFlagIndication (uint8 TransceiverId);This service is performed to validate a previous wakeup event.
Std_ReturnType CanIf_CheckValidation (EcuM_WakeupSourceType WakeupSource);This service checks, whether an underlying CAN driver or a CAN transceiver driver already signals a wakeup event.
Std_ReturnType CanIf_CheckWakeup (EcuM_WakeupSourceType WakeupSource);Requests the CanIf module to clear the WUF flag of the designated CAN transceiver.
Std_ReturnType CanIf_ClearTrcvWufFlag (uint8 TransceiverId);This service indicates that the transceiver has cleared the WufFlag referring to the corresponding CAN transceiver with the abstract CanIf TransceiverId.
void CanIf_ClearTrcvWufFlagIndication (uint8 TransceiverId);This service indicates that the transceiver is running in PN communication mode referring to the corresponding CAN transceiver with the abstract CanIf TransceiverId.
void CanIf_ConfirmPnAvailability (uint8 TransceiverId);This service indicates a Controller BusOff event referring to the corresponding CAN Controller with the abstract CanIf ControllerId.
void CanIf_ControllerBusOff (uint8 ControllerId);The function derives the ErrorCounterTreshold from RxErrorCounter/ TxErrorCounter values and reports it to the IdsM as security event CANIF_SEV_ERRORSTATE_PASSIVE to the IdsM. It also prepares the context data for the respective security event.
This service indicates a controller state transition referring to the corresponding CAN controller with the abstract CanIf ControllerId.
void CanIf_ControllerModeIndication (uint8 ControllerId, Can_ControllerStateType ControllerMode);De-initializes the CanIf module.
void CanIf_DeInit (void);Enables or disables mirroring for a CAN controller.
Std_ReturnType CanIf_EnableBusMirroring (uint8 ControllerId, boolean MirroringActive);The function shall derive the bus error source rx or tx from the parameter CanError and report the bus error as security event CANIF_SEV_TX_ERROR_DETECTED or CANIF_SEV_RX_ ERROR_DETECTED. It also prepares the context data for the respective security event.
void CanIf_ErrorNotification (uint8 ControllerId, Can_ErrorType Can_ErrorType);This service calls the corresponding CAN Driver service for obtaining the error state of the CAN controller.
Std_ReturnType CanIf_GetControllerErrorState (uint8 ControllerId, Can_ErrorStateType* ErrorStatePtr);This service calls the corresponding CAN Driver service for obtaining the current status of the CAN controller.
Std_ReturnType CanIf_GetControllerMode (uint8 ControllerId, Can_ControllerStateType* ControllerModePtr);This service calls the corresponding CAN Driver service for obtaining the Rx error counter of the CAN controller.
Std_ReturnType CanIf_GetControllerRxErrorCounter (uint8 ControllerId, uint8* RxErrorCounterPtr);This service calls the corresponding CAN Driver service for obtaining the Tx error counter of the CAN controller.
Std_ReturnType CanIf_GetControllerTxErrorCounter (uint8 ControllerId, uint8* TxErrorCounterPtr);This service reports the current mode of a requested PDU channel.
Std_ReturnType CanIf_GetPduMode (uint8 ControllerId, CanIf_PduModeType* PduModePtr);This function invokes CanTrcv_GetOpMode and updates the parameter TransceiverModePtr with the value OpMode provided by CanTrcv.
Std_ReturnType CanIf_GetTrcvMode (uint8 TransceiverId, CanTrcv_TrcvModeType* TransceiverModePtr);This service returns the reason for the wake up of the transceiver TransceiverId, via calling the corresponding CAN Transceiver Driver service.
Std_ReturnType CanIf_GetTrcvWakeupReason (uint8 TransceiverId, CanTrcv_TrcvWakeupReasonType* TrcvWuReasonPtr);This service reports, if any TX confirmation has been done for the whole CAN controller since the last CAN controller start.
CanIf_NotifStatusType CanIf_GetTxConfirmationState (uint8 ControllerId);This service returns the version information of the called CAN Interface module.
void CanIf_GetVersionInfo (Std_VersionInfoType* VersionInfo);This service Initializes internal and external interfaces of the CAN Interface for the further processing.
void CanIf_Init (const CanIf_ConfigType* ConfigPtr);This service returns the indication status (indication occurred or not) of a specific CAN Rx L-PDU, requested by the CanIfRxSduId.
CanIf_NotifStatusType CanIf_ReadRxNotifStatus (PduIdType CanIfRxSduId);This service provides the Data Length and the received data of the requested CanIfRxSduId to the calling upper layer.
Std_ReturnType CanIf_ReadRxPduData (PduIdType CanIfRxSduId, PduInfoType* CanIfRxInfoPtr);This service returns the confirmation status (confirmation occurred or not) of a specific static or dynamic CAN Tx L-PDU, requested by the CanIfTxSduId.
CanIf_NotifStatusType CanIf_ReadTxNotifStatus (PduIdType CanIfTxSduId);This service indicates a successful reception of a received CAN Rx L-PDU to the CanIf after passing all filters and validation checks.
void CanIf_RxIndication (const Can_HwType* Mailbox, const PduInfoType* PduInfoPtr);This service shall set the baud rate configuration of the CAN controller. Depending on necessary baud rate modifications the controller might have to reset.
Std_ReturnType CanIf_SetBaudrate (uint8 ControllerId, uint16 BaudRateConfigID);This service calls the corresponding CAN Driver service for changing of the CAN controller mode.
Std_ReturnType CanIf_SetControllerMode (uint8 ControllerId, Can_ControllerStateType ControllerMode);This service reconfigures the corresponding CAN identifier of the requested CAN L-PDU.
void CanIf_SetDynamicTxId (PduIdType CanIfTxSduId, Can_IdType CanId);This service sets the requested mode at the L-PDUs of a predefined logical PDU channel.
Std_ReturnType CanIf_SetPduMode (uint8 ControllerId, CanIf_PduModeType PduModeRequest);This service changes the operation mode of the tansceiver TransceiverId, via calling the corresponding CAN Transceiver Driver service.
Std_ReturnType CanIf_SetTrcvMode (uint8 TransceiverId, CanTrcv_TrcvModeType TransceiverMode);This function shall call CanTrcv_SetTrcvWakeupMode.
Std_ReturnType CanIf_SetTrcvWakeupMode (uint8 TransceiverId, CanTrcv_TrcvWakeupModeType TrcvWakeupMode);Requests transmission of a PDU.
Std_ReturnType CanIf_Transmit (PduIdType TxPduId, const PduInfoType* PduInfoPtr);This service indicates a transceiver state transition referring to the corresponding CAN transceiver with the abstract CanIf TransceiverId.
void CanIf_TrcvModeIndication (uint8 TransceiverId, CanTrcv_TrcvModeType TransceiverMode);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.
Std_ReturnType CanIf_TriggerTransmit (PduIdType TxPduId, PduInfoType* PduInfoPtr);This service confirms a previously successfully processed transmission of a CAN TxPDU.
void CanIf_TxConfirmation (PduIdType CanTxPduId);This type defines a data structure for the post build parameters of the CAN interface for all underlying CAN drivers. At initialization the CanIf gets a pointer to a structure of this type to get access to its configuration data, which is necessary for initialization.
Type CanIf_NotifStatusType.
The PduMode of a channel defines its transmit or receive activity. Communication direction (transmission and/or reception) of the channel can be controlled separately or together by upper layers.
CanNm
NM indicate to activate the transmission of PN shutdown messages on the given NM - Channel. This results in transmission of a NM - PD U with PNSR bit set to 1 (PN shutdown message).
Std_ReturnType CanNm_ActivateTxPnShutdownMsg(NetworkHandleType nmChannelHandle);Check if remote sleep indication takes place or not.
Std_ReturnType CanNm_CheckRemoteSleepIndication(NetworkHandleType nmChannelHandle, boolean* nmRemoteSleepIndPtr);Enables the PN filter functionality on the indicated NM channel. Availability: The API is only available if Can Nm Global Pn Support is TRUE.
void CanNm_ConfirmPnAvailability(NetworkHandleType nmChannelHandle);NM indicate to deactive the transmission of PN shutdown messages on the given NM - Channel. This result in transmission of a usual NM - PDUs with PNSR bit set to 0.
Std_ReturnType CanNm_DeactivateTxPnShutdownMsg(NetworkHandleType nmChannelHandle);De - initializes the Can Nm module.
void CanNm_DeInit(void);Disable the NM PDU transmission ability due to a ISO14229 Communication Control (28hex) service
Std_ReturnType CanNm_DisableCommunication(NetworkHandleType nmChannelHandle);Enable the NM PDU transmission ability due to a ISO14229 Communication Control (28hex) service
Std_ReturnType CanNm_EnableCommunication(NetworkHandleType nmChannelHandle);Get node identifier configured for the local node.
Std_ReturnType CanNm_GetLocalNodeIdentifier(NetworkHandleType nmChannelHandle, uint8* nmNodeIdPtr);Get node identifier out of the most recently received N M PDU.
Std_ReturnType CanNm_GetNodeIdentifier(NetworkHandleType nmChannelHandle, uint8* nmNodeIdPtr);Get the whole PDU data out of the most recently received NM PDU.
Std_ReturnType CanNm_GetPduData(NetworkHandleType nmChannelHandle, uint8* nmPduDataPtr);Returns the state and the mode of the network management.
Std_ReturnType CanNm_GetState(NetworkHandleType nmChannelHandle, Nm_StateType* nmStatePtr, Nm_ModeType* nmModePtr);Get user data out of the most recently received NM PDU.
Std_ReturnType CanNm_GetUserData(NetworkHandleType nmChannelHandle, uint8* nmUserDataPtr);This service returns the version information of this module.
void CanNm_GetVersionInfo(Std_VersionInfoType* versioninfo);Initialize the Can Nm module.
void CanNm_Init(const CanNm_ConfigType* cannmConfigPtr);Main function of the Can Nm which processes the algorithm describes in that document.
void CanNm_MainFunction(void);Release the network, since ECU doesn't have to communicate on the bus.
Std_ReturnType CanNm_NetworkRelease(NetworkHandleType nmChannelHandle);Request the network, since ECU needs to communicate on the bus.
Std_ReturnType CanNm_NetworkRequest(NetworkHandleType nmChannelHandle);Passive startup of the AUTOSAR CAN NM. It triggers the transition from Bus - Sleep Mode or Prepare Bus Sleep Mode to the Network Mode in Repeat Message State. Caveats: Can Nm is initia lized correctly.
Std_ReturnType CanNm_PassiveStartUp(NetworkHandleType nmChannelHandle);Set Repeat Message Request Bit and Partial Network Learning Bit for NM messages transmitted next on the bus. This will force all nodes to enter the PNC Learning Phase. This is needed for the optional Dynamic PNC - to - channel - mapping feature.
Std_ReturnType CanNm_PnLearningRequest(NetworkHandleType nmChannelHandle);Set Repeat Message Request Bit for NM PDUs transmitted next on the bus.
Std_ReturnType CanNm_RepeatMessageRequest(NetworkHandleType nmChannelHandle);Request bus synchronization.
Std_ReturnType CanNm_RequestBusSynchronization(NetworkHandleType nmChannelHandle);Requests transmission of a NM - PDU with PNSR bit set to 1 (PN shutdown message) Tags: atp.Status=draft
Std_ReturnType CanNm_RequestSynchronizedPncShutdown(NetworkHandleType nmChannelHandle, PNCHandleType pncId);Indication of a receive d PDU from a lower layer communication interface module.
void CanNm_RxIndication(PduIdType RxPduId, const PduInfoType* PduInfoPtr);Set the NM Coordinator S leep Ready bit in the Control Bit Vector
Std_ReturnType CanNm_SetSleepReadyBit(NetworkHandleType nmChannelHandle, boolean nmSleepReadyBit);Set user data for NM PDUs transmitted next on the bus.
Std_ReturnType CanNm_SetUserData(NetworkHandleType nmChannelHandle, const uint8* nmUserDataPtr);Requests transmission of a PDU.
Std_ReturnType CanNm_Transmit(PduIdType TxPduId, const PduInfoType* PduInfoPtr);Within this API, the upper layer module (called module) shall check whether the available data fits into the buffer size reported by Pdu Info Ptr - >Sdu Length. If it fits, it shall copy its data into the buffer provided by Pdu Info Ptr - >Sdu Data Ptr and update the length of the actual copied data in Pdu Info Ptr - >Sdu Length. If not, it returns E_ NOT_ OK without changing Pdu Info Ptr.
Std_ReturnType CanNm_TriggerTransmit(PduIdType TxPduId, PduInfoType* PduInfoPtr);The lower layer communication interface module confirms the transmission of a PDU, or the failure to transmit a PDU.
void CanNm_TxConfirmation(PduIdType TxPduId, Std_ReturnType result);This type shall contain at least all parameters that are post - build able according to chapter 10.
CanSM
This callout function returns the number of Can SM base cycles to wait additionally to L1/ L2 after a Bus Off occurred.
void <User_Get Bus Off Delay>(NetworkHandleType network, uint8* delayCyclesPtr);This callback function indicates the Can If_ Check Trcv Wake Flag API process end for the notified CAN Transceiver.
void CanSM_CheckTransceiverWakeFlagIndication(uint8 Transceiver);This callback function shall indicate the Can If_ Clear Trcv Wuf Flag API process end for the notified CAN Transceiver.
void CanSM_ClearTrcvWufFlagIndication(uint8 Transceiver);This callback function indicates that the controller is running in PN communication mode. Tags: atp.Status=draft
void CanSM_ConfirmCtrlPnAvailability(uint8 ControllerId);This callback function indicates that the transceiver is running in PN communication mode.
void CanSM_ConfirmPnAvailability(uint8 TransceiverId);This callback function notifies the Can SM about a bus - off event on a certain CAN controller, which needs to be considered with the specified bus - off recovery handling for th e impacted CAN network.
void CanSM_ControllerBusOff(uint8 ControllerId);This callback shall notify the Can SM module about a CAN controller mode change.
void CanSM_ControllerModeIndication(uint8 ControllerId, Can_ControllerStateType ControllerMode);This service shall inform about the change of the Icom Configuration of a CAN network.
void CanSM_CurrentIcomConfiguration(uint8 ControllerId, IcomConfigIdType ConfigurationId, IcomSwitch_ErrorType Error);This service de - initializes the Can SM module.
void CanSM_DeInit(void);This service shall put out the current communication mode of a CAN network.
Std_ReturnType CanSM_GetCurrentComMode(NetworkHandleType network, ComM_ModeType* ComM_ModePtr);This service puts out the version information of this module (module ID, vendor ID, vendor specific version numbers related to BSW00407)
void CanSM_GetVersionInfo(Std_VersionInfoType* VersionInfo);This service initializes the Can SM module
void CanSM_Init(const CanSM_ConfigType* ConfigPtr);Scheduled function of the Can SM
void CanSM_MainFunction(void);This service shall change the communication mode of a CAN network to the requested one.
Std_ReturnType CanSM_RequestComMode(NetworkHandleType network, ComM_ModeType ComM_Mode);This service shall start an asynchronous process to change the baud rate for the configured CAN controllers of a certain CAN network. Depending on necessary baud rate modifications the controllers might have to reset.
Std_ReturnType CanSM_SetBaudrate(NetworkHandleType Network, uint16 BaudRateConfig ID); ⚠️Service Name Can SM_ Set Ecu Passive Syntax Std_ Return Type Can SM_ Set Ecu Passive ( boolean Can SM_ Passive ) Service ID [hex] 0x13 Sync/ Async Synchronous Reentrancy Non Reentrant Parameters (in) Can SM_ Passive TRUE: set all Can SM channels to passive, i.e. receive only FALSE: set all Can SM channels back to non - passive Parameters (inout) None Parameters (out) None Return value Std _ Return - E_ OK: Request accepted Type E_ NOT_ OK: Request not accepted Descr iption This function can be used to set all Can SM channels of the ECU to a receive only mode. Available via Can SM.h
Std_ReturnType CanSM_SetEcuPassive(boolean CanSM_Passive);This service shall change the Icom Configuration of a CAN network to the requested one.
Std_ReturnType CanSM_SetIcomConfiguration(NetworkHandleType Network, IcomConfigIdType ConfigurationId);This function shall be called by Ecu M when a wakeup source shall be started.
Std_ReturnType CanSM_StartWakeupSource(NetworkHandleType network);This function shall be called by Ecu M when a wakeup source shall be stopped.
Std_ReturnType CanSM_StopWakeupSource(NetworkHandleType network);This callback shall notify the Can SM module about a CAN transceiver mode change.
void CanSM_TransceiverModeIndication(uint8 TransceiverId, CanTrcv_TrcvModeType TransceiverMode);This function shall notify the Can SM module, that the Can Nm has detected for the affected partial CAN network a tx timeout exception, which shall be recovered within the respective network state machine of the Can SM module.
void CanSM_TxTimeoutException(NetworkHandleType Channel);Can specific communication modes / states notified to the Bsw M module
This type defines a data structure for the post build parameters of the Can SM. At initialization the Can SM gets a pointer to a structure of this type to get access to its configuration data, which is neces sary for initialization. Available Can SM.h via
Defines the values of the internal states of the Can SM module
CanTp
Requests cancellation of an ongoing reception of a PDU in a lower layer transport protocol module.
Std_ReturnType CanTp_CancelReceive (PduIdType RxPduId);Requests cancellation of an ongoing transmission of a PDU in a lower layer communication module.
Std_ReturnType CanTp_CancelTransmit (PduIdType TxPduId);Request to change a specific transport protocol parameter (e.g. block size).
Std_ReturnType CanTp_ChangeParameter (PduIdType id, TPParameterType parameter, uint16 value);This function returns the version information of the Can Tp module.
void CanTp_GetVersionInfo (Std_VersionInfoType* versioninfo);This function initializes the Can Tp module.
void CanTp_Init (const CanTp_ConfigType* CfgPtr);The main function for scheduling the CAN TP.
void CanTp_MainFunction (void);This service is used to read the current value of reception parameters BS and STmin for a specified N - SDU.
Std_ReturnType CanTp_ReadParameter (PduIdType id, TPParameterType parameter, uint16* value);Indication of a received PDU from a lower layer communication interface module.
void CanTp_RxIndication (PduIdType RxPduId, const PduInfoType* PduInfoPtr);This function is called to shutdown the Can Tp module.
void CanTp_Shutdown (void);Requests transmission of a PDU.
Std_ReturnType CanTp_Transmit (PduIdType TxPduId, const PduInfoType* PduInfoPtr);The lower layer communication interface module confirms the transmission of a PDU, or the failure to transmit a PDU.
void CanTp_TxConfirmation (PduIdType TxPduId, Std_ReturnType result);Data structure type for the post - build configuration parameters.
CanTrcv
Requests to check the status of the wakeup flag from the transceiver hardware.
Std_ReturnType CanTrcv_CheckWakeFlag (uint8 Transceiver);Service is called by underlying CANIF in case a wake up interrupt is detected.
Std_ReturnType CanTrcv_CheckWakeup (uint8 Transceiver);Clears the status of the timeout flag in the transceiver hardware. This API shall exist only if Can Trcv Hw Pn Support = TRUE.
Std_ReturnType CanTrcv_ClearTrcvTimeoutFlag (uint8 Transceiver);Clears the WUF flag in the transceiver hardware. This API shall exist only if Can Trcv Hw Pn Support = TRUE.
Std_ReturnType CanTrcv_ClearTrcvWufFlag (uint8 Transceiver);De - initializes the Can Trcv module.
void CanTrcv_DeInit (void);Gets the wakeup reason for the Transceiver and returns it in parameter Reason.
Std_ReturnType CanTrcv_GetBusWuReason (uint8 Transceiver, CanTrcv_TrcvWakeupReasonType* reason);Gets the mode of the Transceiver and returns it in Op Mode.
Std_ReturnType CanTrcv_GetOpMode (uint8 Transceiver, CanTrcv_TrcvModeType* OpMode);Reads the transceiver configuration/ status data and returns it through parameter Trcv Sys Data. This API shall exist only if Can Trcv Hw Pn Support = TRUE.
Std_ReturnType CanTrcv_GetTrcvSystemData (uint8 Transceiver, uint32* TrcvSysData);Gets the version of the module and returns it in Version Info.
void CanTrcv_GetVersionInfo (Std_VersionInfoType* versioninfo);Initializes the Can Trcv module.
void CanTrcv_Init (const CanTrcv_ConfigType* ConfigPtr);Service to scan all busses for wake up events and perform these event.
void CanTrcv_MainFunction (void);Reads the transceiver diagnostic status periodically and sets product/ development accordingly.
void CanTrcv_MainFunctionDiagnostics (void);Reads the status of the silence flag from the transceiver hardware. This API shall exi st only if Can Trcv Hw Pn Support = TRUE.
Std_ReturnType CanTrcv_ReadTrcvSilenceFlag (uint8 Transceiver, CanTrcv_TrcvFlagStateType* FlagState);Reads the status of the tim eout flag from the transceiver hardware. This API shall exist only if Can Trcv Hw Pn Support = TRUE.
Std_ReturnType CanTrcv_ReadTrcvTimeoutFlag (uint8 Transceiver, CanTrcv_TrcvFlagStateType* FlagState);Sets the mode of the Transceiver to the value Op Mode.
Std_ReturnType CanTrcv_SetOpMode (uint8 Transceiver, CanTrcv_TrcvModeType OpMode);The API configures the wake - up of the transceiver for Standby and Sleep Mode: Either the CAN transceiver is woken up by a remote wake - up pattern (standard CAN wake - up) or by the configured remote wake - up frame.
Std_ReturnType CanTrcv_SetPNActivationState (CanTrcv_PNActivationType ActivationState);En ables, disables or clears wake - up events of the Transceiver according to Trcv Wakeup Mode.
Std_ReturnType CanTrcv_SetWakeupMode (uint8 Transceiver, CanTrcv_TrcvWakeupModeType TrcvWakeupMode);This is the type of the external data structure containing the overall initialization data for the CAN transceiver driver and settings affecting all transceivers. Furthermore it contains pointers to transceiver configuration structures. The con tents of the initialization data structure are CAN transceiver hardware specific.
Datatype used for describing whether PN wakeup functionality in Can Trcv is enabled or disabled.
Provides the state of a flag in the transceiver hardware.
Operating modes of the CAN Transceiver Driver.
This type shall be used to control the CAN transceiver concerning wake up events and wake up notifications.
This type denotes the wake up reason detected by the CAN transceiver in detail. AUTOSAR CP R20 - of Document ID : AUTOSAR_SWS_CANTransceiverDriver
CanXL
Request transmission of an Ethernet frame, where each upper layer a header part as element of a single linked list. All headers together with the payload form an entire Ethernet frame Tags: atp.Status=draft
Std_ReturnType CanXL_ImmediateTransmit(uint8 CtrlIdx, Eth_BufIdxType TxHandleId, uint8 Priority, ListElemStructType* HeaderListPtr, uint8* PayloadPtr, uint16 PayloadLength);Indication from the upper layer to release the reception buffer (ingress queue element) of the given physical Ethernet controller. Tags: atp.Status=draft
void CanXL_ReleaseRxBuffer(uint8 CtrlIdx, Eth_BufIdxType RxHandleId);Ttcan
Acknowledges the time mark interrupt by resetting the flag in the interrupt vector register.
void Can_TTAckTimeMark(uint8 Controller);Cancels the time mark.
void Can_TTCancelTimeMark(uint8 Controller);Disables the time mark interrupt.
void Can_TTDisableTimeMarkIRQ(uint8 Controller);Enables the time mark interrupt.
void Can_TTEnableTimeMarkIRQ(uint8 Controller);Gets the error level. This includes the severity of the error level (S0-S3) and the minimum and maximum value of the message status count.
void Can_TTGetErrorLevel(uint8 Controller, Can_TTErrorLevelType* Can_TTErrorLevel);Gets the master state. The master state includes the sync mode (sync_off, synchronizing, in_ gap, in_schedule) the master-slave mode (master_off, slave, backup_master, current_master) and the current value for ref trigger offset.
void Can_TTGetMasterState(uint8 Controller, Can_TTMasterStateType* Can_TTMasterState);Gets the actual value of NTU (network time unit). Together with the local oscillator period, the actual value of NTU can be derived from the actual value of TUR.
void Can_TTGetNTUActual(uint8 Controller, Can_TTTURType* Can_TTTURAct);Sets the value of "global time preset".
void Can_TTGlobalTimePreset(uint8 Controller, Can_TTTimeType Can_TTGlobalTimePreset);Polls the interrupt flags specific to TTCAN
void Can_TTMainFunction_IRQ(void);Reads received data from the controller by returning the pointer of the CanID, the DLC and the Data of the message in the requested HRH.
void Can_TTReceive(uint8 Controller, uint8 Hrh, Can_IdType* CanId, uint8* CanDlc, uint8* CanSduPtr);Signals the end of a gap.
void Can_TTSetEndOfGap(uint8 Controller);Adjusts the NTU (network time unit) according to the value given by "NTU adjust". Together with the local oscillator period, "TUR adjust" can be derived from "NTU adjust".
void Can_TTSetExtClockSyncCommand(uint8 Controller);Sets the "Next_is_Gap" bit.
void Can_TTSetNextIsGap(uint8 Controller);Sets the value of "NTU adjust". Together with the local oscillator period, "TUR adjust" can be derived from "NTU adjust".
void Can_TTSetNTUAdjust(uint8 Controller, Can_TTTURType Can_TTTURAdjust);Adjusts the global time at the beginning of the next basic cycle by the amount of "global time preset"
void Can_TTSetTimeCommand(uint8 Controller);Sets a new value for the time mark for the given time source.
void Can_TTSetTimeMark(uint8 Controller, Can_TTTimeType Can_TTTimeMark, Can_TTTimeSourceType Can_TTTimeSource);Error level (S0-S3)
TTCAN error level including min and max values of message status count
Master-Slave Mode
Master state type including sync mode, master-slave mode and current ref trigger offset
Sync mode
Time source
16 bit value representing time values of TTCAN, e.g. cycle, local or global time
TtcanIf
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.
Std_ReturnType <User_TriggerTransmit>(PduIdType TxPduId, PduInfoType* PduInfoPtr);Acknowledges the time mark interrupt by resetting the flag in the interrupt vector register.
Std_ReturnType CanIf_TTAckTimeMark(uint8 ControllerId);Reports an application watchdog error.
Std_ReturnType CanIf_TTApplWatchdogError(uint8 ControllerId);Cancels the time mark.
Std_ReturnType CanIf_TTCancelTimeMark(uint8 ControllerId);Disables the time mark interrupt.
Std_ReturnType CanIf_TTDisableTimeMarkIRQ(uint8 ControllerId);Enables the time mark interrupt.
Std_ReturnType CanIf_TTEnableTimeMarkIRQ(uint8 ControllerId);Reports the occurrence of a gap.
Std_ReturnType CanIf_TTGap(uint8 ControllerId);Gets the current values for the global, local and cycle time and the cycle count of the controller
Std_ReturnType CanIf_TTGetControllerTime(uint8 ControllerId, CanIf_TTTimeType* CanIf_TTGlobalTime, CanIf_TTTimeType* CanIf_TTLocalTime, CanIf_TTTimeType* CanIf_TTCycleTime, uint8* CanIf_TTCycleCount);Gets the error level. This includes the severity of the error level (S0-S3) and the minimum and maximum value of the message status count.
Std_ReturnType CanIf_TTGetErrorLevel(uint8 ControllerId, CanIf_TTErrorLevelType* CanIf_TTErrorLevel);Gets the master state. The master state includes the sync mode (sync_off, synchronizing, in_ gap, in_schedule) the master-slave mode (master_off, slave, backup_master, current_master) and the current value for ref trigger offset.
Std_ReturnType CanIf_TTGetMasterState(uint8 ControllerId, CanIf_TTMasterStateType* CanIf_TTMasterState);Gets the actual value of NTU (network time unit). Together with the local oscillator period, the actual value of NTU can be derived from the actual value of TUR.
Std_ReturnType CanIf_TTGetNTUActual(uint8 ControllerId, float32 CanIf_TTNTUAct);Gets the synchronization quality.
Std_ReturnType CanIf_TTGetSyncQuality(uint8 ControllerId, boolean* CanIf_TTClockSpeed, boolean* CanIf_TTGlobalTimePhase);Gets the IRQ status of the time mark.
Std_ReturnType CanIf_TTGetTimeMarkIRQStatus(uint8 ControllerId, boolean* CanIf_TTIRQStatus);Sets the value of "global time preset".
Std_ReturnType CanIf_TTGlobalTimePreset(uint8 ControllerId, CanIf_TTTimeType CanIf_TTGlobalTimePreset);Processes the job list of the TTCAN controller <Controller>.
void CanIf_TTJobListExec_<Controller>(void);Reports change of the master state between potential and current master.
Std_ReturnType CanIf_TTMasterStateChange(uint8 ControllerId, CanIf_TTMasterStateType CanIf_TTMasterState);Signals the end of a gap.
Std_ReturnType CanIf_TTSetEndOfGap(uint8 ControllerId);Adjusts the NTU (network time unit) according to the value given by "NTU adjust". Together with the local oscillator period, "TUR adjust" can be derived from "NTU adjust".
Std_ReturnType CanIf_TTSetExtClockSyncCommand(uint8 ControllerId);Sets the "Next_is_Gap" bit.
Std_ReturnType CanIf_TTSetNextIsGap(uint8 ControllerId);Sets the value of "NTU adjust". Together with the local oscillator period, "TUR adjust" can be derived from "NTU adjust".
Std_ReturnType CanIf_TTSetNTUAdjust(uint8 ControllerId, float32 CanIf_TTNTUAdjust);Adjusts the global time at the beginning of the next basic cycle by the amount of "global time preset"
Std_ReturnType CanIf_TTSetTimeCommand(uint8 ControllerId);Sets a new value for the time mark for the given time source.
Std_ReturnType CanIf_TTSetTimeMark(uint8 ControllerId, CanIf_TTTimeType CanIf_TTTimeMark, CanIf_TTTimeSourceType CanIf_TTTimeSource);Reports one of the following errors: • failed to serve appl. watchdog • config error • watch trigger reached
void CanIf_TTSevereError(uint8 ControllerId, CanIf_TTSevereErrorEnumType CanIf_TTSevereError);Reports the start of a basic cycle.
Std_ReturnType CanIf_TTStartOfCycle(uint8 ControllerId, uint8 CanIf_TTCycleCount);Reports a time discontinuity.
Std_ReturnType CanIf_TTTimeDisc(uint8 ControllerId);Reports one of the following errors: • Change of error level • Tx overflow / underflow • Synchronization failed • Init watch trigger
Std_ReturnType CanIf_TTTimingError(uint8 ControllerId, CanIf_TTTimingErrorIRQType CanIf_TTTimingErrorIRQ);Error level (S0-S3)
TTCAN error level including min and max values of message status count
Event that causes a Timing/Error IRQ
Master-Slave Mode
Master state type including sync mode, master-slave mode and current ref trigger offset
Event that causes a severe error
Sync mode
Time source of time values in TTCAN
16 bit value representing time values of TTCAN, e.g. cycle, local or global time
Combines all events that are reported by CanIf_TTTimingError (event indication and error level)
Guia do clusterGERADO POR IA
Disponibiliza drivers de hardware, abstração de interface, segmentação e controle de transceptor para CAN.
Disponibiliza drivers de hardware, abstração de interface, segmentação e controle de transceptor para CAN.
O cluster conecta o driver CAN, o CAN Interface, o protocolo de transporte conforme a ISO 15765-2 e o driver do transceptor para formar a parte inferior da pilha de comunicação CAN. Camadas superiores transmitem via CanIf_Transmit(). O CanIf mapeia as L-PDUs em objetos de hardware, bufferiza-as em caso de hardware ocupado e distribui mensagens de recepção e confirmação [SWS_CANIF_00005]. O CanTp segmenta mensagens grandes e busca os dados passo a passo via PduR [SWS_CanTp_00086]. O envio ocorre somente se o controlador estiver no estado CAN_CS_STARTED e o canal de PDU estiver pronto para transmissão; os modos são controlados pelo CanSM via CanIf.
O cluster compõe a parte inferior da pilha de comunicação CAN. Can controla o controlador e as caixas de correio, CanIf abstrai drivers, controladores e transceptores, CanTp segmenta conforme a ISO 15765-2, e CanTrcv gerencia os modos de operação do transceptor. O CanIf acessa buffers de hardware exclusivamente por meio de serviços do driver [SWS_CANIF_00023]. Para camadas superiores, ele disponibiliza faixas uniformes para ControllerId e TransceiverId [SWS_CANIF_00653] [SWS_CANIF_00655].
Diagrama de contexto: CanIf intermedeia entre PduR, CanTp, CanSM e EcuM, por um lado, e os drivers Can e CanTrcv, por outro. Fontes: [SWS_CANIF_00005] [SWS_CANIF_00006] [SWS_CANIF_00358]
Durante o envio, CanIf_Transmit() chama Can_Write() com o HTH correspondente [SWS_CANIF_00318]. Se o driver reportar CAN_BUSY, o CanIf bufferiza a L-PDU [SWS_CANIF_00381]. Durante a confirmação de transmissão, ele envia a entrada bufferizada de maior prioridade de forma subsequente [SWS_CANIF_00668]. As L-PDUs recebidas passam no CanIf por filtros de software e verificação de comprimento de dados antes de o CanIf encaminhá-las para CanTp ou PduR [SWS_CANIF_00389] [SWS_CANIF_00390]. O CanTp não bufferiza dados úteis por conta própria, mas os busca via PduR_CanTpCopyTxData() ou os entrega via PduR_CanTpCopyRxData() [SWS_CanTp_00086] [SWS_CanTp_00269].
Diagrama de sequência: envio direto ou bufferização em caso de CAN_BUSY, seguido pelo envio subsequente a partir do buffer em CanIf_TxConfirmation. Fontes: [SWS_CANIF_00381] [SWS_CANIF_00183]
Can opera acionado por interrupção ou por polling por meio de suas MainFunctions [SWS_Can_00225] [SWS_Can_00226]. CanTp_RxIndication() deve poder ser chamada em contexto de interrupção [SWS_CanTp_00235], enquanto CanTp_MainFunction() monitora os timeouts de protocolo [SWS_CanTp_00164]. CanIf protege buffers compartilhados contra acessos preemptivos [SWS_CANIF_00064].
Após a inicialização, todos os canais CanIf estão em CANIF_OFFLINE [SWS_CANIF_00864]. CanSM comuta os controladores via CanIf_SetControllerMode() [SWS_CANIF_00308]. SLEEP força CANIF_OFFLINE; STOPPED ou BusOff forçam CANIF_TX_OFFLINE [SWS_CANIF_00865] [SWS_CANIF_00866]. O CanIf reporta um BusOff ao CanSM [SWS_CANIF_00724]. Erros são direcionados ao DET; CanTrcv reporta adicionalmente CANTRCV_E_BUS_ERROR ao DEM [SWS_CanTrcv_00206]. O CanTp aborta sessões em caso de timeouts com confirmação negativa [SWS_CanTp_00310].
Arquitetura do sistema e papel do cluster
O cluster «CAN Communication» forma a parte inferior da pilha de comunicação AUTOSAR para CAN. Ele se estende desde o driver CAN de baixo nível até o protocolo de transporte, sobre o qual assentam PduR e DCM. O núcleo é o CAN Interface, que desacopla as camadas superiores dos detalhes de driver e hardware. Ele acessa buffers de comunicação específicos de hardware exclusivamente por meio dos serviços do driver [SWS_CANIF_00023]. Controladores e transceptores de múltiplas instâncias de driver são abstraídos por meio de faixas próprias para ControllerId e TransceiverId [SWS_CANIF_00653] [SWS_CANIF_00655].
| módulo | Papel no cluster | Evidência |
|---|---|---|
Can | Acesso a controladores CAN e caixas de correio, envio via Can_Write(), máquina de estados por controlador | [SWS_Can_00233] [SWS_Can_91013] |
CanIf | Mapeamento de L-PDUs em HTH/HRH, filtros de software, buffer de envio, gerenciamento dos modos de controladores, canais de PDU e transceptores | [SWS_CANIF_00662] [SWS_CANIF_00137] |
CanTp | Segmentação e remontagem conforme ISO 15765-2, controle de fluxo, múltiplas conexões paralelas | [SWS_CanTp_00033] [SWS_CanTp_00096] |
CanTrcv | Modos de operação NORMAL, STANDBY e SLEEP, fontes de despertar, diagnóstico do transceptor | [SWS_CanTrcv_00102] [SWS_CanTrcv_00107] |
O CanIf endereça o hardware por meio de dois tipos de identificadores: HTH para objetos de transmissão e HRH para objetos de recepção [SWS_CANIF_00291] [SWS_CANIF_00292]. O CanIf integra múltiplos drivers CAN por meio de ponteiros de função para cada driver [SWS_CANIF_00378]. Em callbacks, o CanIf reconhece o driver chamador pelo ControllerId na estrutura Can_HwType CanIf p. 68. Para cada tipo de hardware de transceiver, existe exatamente uma instância CanTrcv [SWS_CanTrcv_00016].
Diagrama de contexto: o CanIf é o hub central entre as camadas superiores (PduR, CanTp, CanSM, EcuM) e os drivers Can e CanTrcv. Fontes: [SWS_CANIF_00005] [SWS_CANIF_00006] [SWS_CANIF_00358] [SWS_CANIF_00724] [SWS_CanTp_00216] [SWS_CanTrcv_00206]
Interação e caminhos de interação
Transmissão: uma camada superior chama CanIf_Transmit() [SWS_CANIF_00005]. O CanIf determina o HTH para o TxPduId e chama Can_Write() com uma estrutura Can_PduType [SWS_CANIF_00318] [SWS_Can_00415]. Se Can_Write() retornar E_OK, CanIf_Transmit() também retornará E_OK [SWS_CANIF_00162]. Se nenhum objeto de transmissão estiver livre, o driver reporta CAN_BUSY [SWS_Can_00039]. Com o buffer de transmissão ativado, o CanIf armazena então a L-PDU no CanIfTxBuffer [SWS_CANIF_00381] [SWS_CANIF_00063] CanIf p. 138.
Confirmação de transmissão: após a transmissão bem-sucedida, o Can chama CanIf_TxConfirmation() [SWS_CANIF_00007]. Para isso, o driver memoriza o swPduHandle de Can_Write() Can p. 40. O CanIf verifica se há entradas em buffer para o HTH liberado. Ele transmite em seguida a entrada de maior prioridade segundo a ISO 11898-1 e a remove imediatamente do buffer [SWS_CANIF_00386] [SWS_CANIF_00070] [SWS_CANIF_00668] [SWS_CANIF_00183]. Em seguida, a camada superior recebe <User_TxConfirmation>(E_OK) [SWS_CANIF_00383].
Diagrama de sequência: solicitação de transmissão com envio direto ou buffering em caso de CAN_BUSY e retransmissão a partir do buffer durante a confirmação de transmissão. Fontes: [SWS_CANIF_00318] [SWS_CANIF_00381] [SWS_CANIF_00668] [SWS_CANIF_00183] CanIf p. 157
Recepção: o Can reporta uma L-PDU recebida via CanIf_RxIndication() [SWS_CANIF_00006]. Em HRHs BasicCAN, o CanIf executa primeiro a filtragem por software e, em seguida, a verificação do comprimento dos dados [SWS_CANIF_00389] [SWS_CANIF_00390] [SWS_CANIF_00663]. Depois, encaminha a indicação para o receptor configurado [SWS_CANIF_00415] [SWS_CANIF_00056], por exemplo, para CanTp_RxIndication [SWS_CANIF_00448] ou para PduR_CanIfRxIndication [SWS_CANIF_00442].
Protocolo de transporte: CanTp_Transmit() [SWS_CanTp_00212] inicia uma transmissão segmentada se os dados não couberem em uma N-PDU [SWS_CanTp_00232]. O CanTp não armazena os dados úteis em buffer por si próprio, mas os busca para cada SF, FF e CF via PduR_CanTpCopyTxData() [SWS_CanTp_00086] [SWS_CanTp_00298]. Ele entrega os frames via CanIf_Transmit() [SWS_CanTp_00216]. Ao receber um SF ou FF, o CanTp consulta o buffer disponível com PduR_CanTpStartOfReception() [SWS_CanTp_00079] [SWS_CanTp_00080]. Ele copia cada CF com PduR_CanTpCopyRxData() [SWS_CanTp_00269]. Se o buffer não for suficiente para o próximo bloco, o CanTp envia Flow Control WAIT [SWS_CanTp_00082] [SWS_CanTp_00325] CanTp p. 37.
Transceiver: CanIf_SetTrcvMode() repassa solicitações de modo para CanTrcv_SetOpMode() [SWS_CANIF_00358]. Após a transição, o CanTrcv chama CanIf_TrcvModeIndication() [SWS_CanTrcv_00158], e o CanIf repassa a notificação para o CanSM [SWS_CANIF_00712]. Da mesma forma, CanIf_GetTrcvWakeupReason() e CanIf_SetTrcvWakeupMode() delegam para o CanTrcv [SWS_CANIF_00368] [SWS_CANIF_00372].
Sincronização, reentrância e contextos de tarefas
CanIf_Transmit() é reentrante para diferentes PduIds, mas não para o mesmo PduId [SWS_CANIF_00005]. O CanIf deve proteger acessos preemptivos a recursos compartilhados uns contra os outros [SWS_CANIF_00064]. Isso afeta particularmente os buffers de transmissão [SWS_CANIF_00033], o CanId de L-PDUs dinâmicas durante CanIf_SetDynamicTxId() [SWS_CANIF_00673] e o buffer de recepção durante CanIf_ReadRxPduData() [SWS_CANIF_00199].
O Can suporta operação por interrupção e por polling. Conforme a configuração, as MainFunctions realizam o polling de confirmações de transmissão, recepção, BusOff, Wakeup e modo do controlador [SWS_Can_00225] [SWS_Can_00226] [SWS_Can_00227] [SWS_Can_00228] [SWS_Can_00368] CanIf p. 152. Callbacks como CanIf_ControllerBusOff() são executados, portanto, opcionalmente em nível de interrupção ou em nível de tarefa CanIf p. 119. Can_DisableControllerInterrupts() e Can_EnableControllerInterrupts() atuam de forma aninhada: cada bloqueio requer uma liberação própria [SWS_Can_00231] [SWS_Can_00232] Can p. 61.
CanTp_RxIndication() e CanTp_TxConfirmation() devem poder ser chamados em contexto de interrupção [SWS_CanTp_00235] [SWS_CanTp_00236]. CanTp_MainFunction() atende ciclicamente os temporizadores N_As, N_Bs, N_Cs, N_Ar, N_Br, N_Cr e STmin [SWS_CanTp_00213] [SWS_CanTp_00164]. O ciclo deles segue o parâmetro CanTpMainFunctionPeriod [SWS_CanTp_00300]. Interpretação: esse período provavelmente determina a resolução alcançável dos timeouts. Pergunta Q-6ee587d8a8f38bff (aberta) Cada conexão utiliza buffers, temporizadores e uma máquina de estados próprios [SWS_CanTp_00122] CanTp p. 42. CanTrcv_MainFunction() busca ciclicamente por eventos de despertar em barramentos em STANDBY e SLEEP [SWS_CanTrcv_00013] [SWS_CanTrcv_00112].
Ciclos de vida e modos operacionais
O EcuM inicializa o CanIf com CanIf_Init() e os drivers Can e CanTrcv separadamente CanIf p. 40 [SWS_Can_00223] [SWS_CanTrcv_00001]. CanTrcv_Init() coloca cada transceiver em SLEEP ou STANDBY, dependendo da configuração [SWS_CanTrcv_00148]. Os drivers utilizados pelo CanTrcv devem estar prontos previamente [SWS_CanTrcv_00099]. Após a inicialização, o CanIf espera que os controladores estejam no estado STOPPED e comuta todos os canais para CANIF_OFFLINE [SWS_CANIF_00864]. O CanIf rejeita chamadas de serviço antes da inicialização [SWS_CANIF_00661]. Interpretação: Can e CanTrcv devem, portanto, ser inicializados antes do CanIf. Pergunta Q-4af03fca13da9a5b (aberta) O CanTp comuta de CANTP_OFF para CANTP_ON com CanTp_Init() [SWS_CanTp_00027] [SWS_CanTp_00170]. A segmentação só é realizada no estado CANTP_ON [SWS_CanTp_00238] CanTp p. 27.
A mudança de modo é controlada pelo CanSM: CanIf_SetControllerMode() chama Can_SetControllerMode() [SWS_CANIF_00003] [SWS_CANIF_00308]. O Can reporta a conclusão de forma assíncrona via CanIf_ControllerModeIndication(), e o CanIf a repassa ao CanSM [SWS_CANIF_00699] [SWS_CANIF_00711]. Os estados do controlador são UNINIT, STOPPED, STARTED e SLEEP [SWS_Can_91013] Can p. 38. Acima deles estão os modos de canal de PDU do CanIf [SWS_CANIF_00137]. CanIf_SetPduMode() só é aceito no estado CAN_CS_STARTED [SWS_CANIF_00874]. SLEEP força CANIF_OFFLINE; STOPPED ou BusOff forçam CANIF_TX_OFFLINE [SWS_CANIF_00865] [SWS_CANIF_00866].
Diagrama de estados: os modos de canal de PDU do CanIf são determinados por CanIf_SetPduMode e por mudanças do modo do controlador. Fontes: [SWS_CANIF_00137] [SWS_CANIF_00864] [SWS_CANIF_00865] [SWS_CANIF_00866] [SWS_CANIF_00874] CanIf p. 61
Para o despertar, CanIf_CheckWakeup() consulta os drivers via Can_CheckWakeup() ou CanTrcv_CheckWakeup() [SWS_CANIF_00395] [SWS_Can_00360] [SWS_CanTrcv_00143]. CanIf_CheckValidation() só reporta um evento de despertar para <User_ValidateWakeupEvent> se uma recepção válida tiver sido armazenada desde o despertar [SWS_CANIF_00178] [SWS_CANIF_00179] [SWS_CANIF_00286] CanIf p. 102. No Partial Networking, o PnTxFilter bloqueia todas as transmissões após CAN_CS_SLEEP, exceto as PDUs de filtro PN. Somente uma confirmação de transmissão ou uma recepção desfaz o bloqueio [SWS_CANIF_00749] [SWS_CANIF_00750] [SWS_CANIF_00751] [SWS_CANIF_00896]. Antes da transição para um modo de baixo consumo, o CanSM limpa o flag WUF via CanIf_ClearTrcvWufFlag() para que nenhum despertar por frame seja perdido [SWS_CANIF_00766] [SWS_CanTrcv_00194] [SWS_CanTrcv_00195] CanTrcv p. 57. Os módulos são encerrados com Can_DeInit(), CanIf_DeInit() e CanTrcv_DeInit() [SWS_Can_91002] [SWS_CANIF_91002] [SWS_CanTrcv_91001].
Tratamento de erros, rastreamento pelo DET e degradação
Todos os módulos do cluster reportam erros de desenvolvimento ao DET. O CanIf faz isso, por exemplo, em caso de TxPduId inválido ou ponteiro nulo [SWS_CANIF_00319] [SWS_CANIF_00320]. O CanTp, além disso, retorna E_NOT_OK [SWS_CanTp_00294]; Can e CanTrcv utilizam códigos de erro próprios [SWS_Can_91019] [SWS_CanTrcv_00050]. Erros de tempo de execução referem-se, entre outros, a comprimentos de dados rejeitados [SWS_CANIF_00168], tentativas de transmissão em canais no modo CANIF_OFFLINE [SWS_CANIF_00382], mensagens de recepção perdidas [SWS_Can_91020] e falha de comunicação com o transceiver [SWS_CanTrcv_00113].
Das evidências consideradas, apenas o CanTrcv menciona uma entrada DEM: CanTrcv_MainFunctionDiagnostics() define CANTRCV_E_BUS_ERROR como FAILED ou PASSED, dependendo do flag BUSERR [SWS_CanTrcv_00218] [SWS_CanTrcv_00206] [SWS_CanTrcv_00227] CanTrcv p. 48.
O Can reporta um BusOff via CanIf_ControllerBusOff() [SWS_CANIF_00218]. O CanIf define então o canal como CANIF_TX_OFFLINE e informa o CanSM [SWS_CANIF_00866] [SWS_CANIF_00724] CanIf p. 147. Ao entrar em CAN_CS_STOPPED, o CanIf esvazia os buffers de transmissão e confirma negativamente transmissões pendentes [SWS_CANIF_00485] [SWS_CANIF_00739]. Para a recuperação, o CanSM pode consultar com CanIf_GetTxConfirmationState() se houve uma confirmação de transmissão desde a última inicialização do controlador [SWS_CANIF_00734] [SWS_CANIF_00740] CanIf p. 103. O estado de erro e os contadores de erro podem ser consultados via CanIf [SWS_CANIF_91001] [SWS_Can_91003] [SWS_CANIF_91003]. Se o Security-Event-Reporting estiver ativado, o CanIf reporta erros de barramento, bem como eventos Error-Passive e BusOff ao IdsM [SWS_CANIF_00913] [SWS_CANIF_00915] [SWS_CANIF_00917] [SWS_CANIF_00918].
Diagrama de sequência: a notificação de BusOff flui do controlador via Can e CanIf para o CanSM; o CanIf bloqueia nesse processo o caminho de transmissão e reinicializa os buffers de transmissão. Fontes: [SWS_CANIF_00218] [SWS_CANIF_00724] [SWS_CANIF_00866] [SWS_CANIF_00918] [SWS_CANIF_00734] CanIf p. 147
O CanTp aborta sessões em caso de timeouts e notifica a camada superior negativamente, por exemplo, em N_As, N_Bs ou N_Cr [SWS_CanTp_00310] [SWS_CanTp_00316] [SWS_CanTp_00313]. O CanTp procede da mesma forma após WFTmax FC(WAIT) consecutivos [SWS_CanTp_00223] ou em caso de FC com overflow [SWS_CanTp_00309]. Como modo de degradação, o CanIf confirma transmissões para as camadas superiores no modo CANIF_TX_OFFLINE_ACTIVE, sem transmitir para o barramento [SWS_CANIF_00072].
Guia gerado por IA com base nas especificações AUTOSAR dos módulos Can, CanIf, CanTp e CanTrcv (Classic Platform R20-11). Apenas os requisitos com links são normativos; declarações identificadas como interpretação não são comprovadas pelas fontes.
Module im Cluster
CAN Driver (Can)
The CAN driver provides hardware-dependent access to the internal and external CAN controllers (CAN 2.0B, CAN FD, CAN XL).
CAN Interface (CanIf)
The CanIf abstracts CAN hardware details and provides uniform access to multiple CAN controllers and transceivers for higher-layer modules (PduR, CanTp, CanNm, CanSM).
CAN Network Management (CanNm)
AUTOSAR Classic Communication Services-Modul CAN Network Management (CanNm, Spezifikation: AUTOSAR_CP_SWS_CANNetworkManagement.pdf, AUTOSAR_SWS_CANNetworkManagement.pdf, AUTOSAR_SWS_CAN_Generic_NM.pdf, AUTOSAR_SWS_CAN_NM.pdf).
CAN State Manager (CanSM)
AUTOSAR Classic Communication Services-Modul CAN State Manager (CanSM, Spezifikation: AUTOSAR_CP_SWS_CANStateManager.pdf, AUTOSAR_SWS_CANStateManager.pdf, AUTOSAR_SWS_CAN_StateManager.pdf).
CAN Transport Layer (CanTp)
Provides segmentation and reassembly of CAN messages up to 4095 bytes (ISO 15765-2).
CAN Transceiver Driver (CanTrcv)
Controls physical bus transceiver states and wakeup detection on CAN lines.
CAN XL Driver (CanXL)
AUTOSAR Classic Communication Drivers-Modul CAN XL Driver (CanXL, Spezifikation: AUTOSAR_CP_SWS_CANXLDriver.pdf, AUTOSAR_SWS_CANXLDriver.pdf).
CAN XL Transceiver Driver (CanXLTrcv)
AUTOSAR Classic Communication HW Abstraction-Modul CAN XL Transceiver Driver (CanXLTrcv, Spezifikation: AUTOSAR_CP_SWS_CANXLTransceiverDriver.pdf, AUTOSAR_SWS_CANXLTransceiverDriver.pdf).
TTCAN Driver (Ttcan)
AUTOSAR Classic Communication Drivers-Modul TTCAN Driver (Ttcan, Spezifikation: AUTOSAR_CP_SWS_TTCANDriver.pdf, AUTOSAR_SWS_TTCANDriver.pdf).
TTCAN Interface (TtcanIf)
AUTOSAR Classic Communication HW Abstraction-Modul TTCAN Interface (TtcanIf, Spezifikation: AUTOSAR_CP_SWS_TTCANInterface.pdf, AUTOSAR_SWS_TTCANInterface.pdf).
gemini-3.8-flash-low· 2026-10-13 · Original em alemão