SNIP_CLASSIC_COMSTACK_SECTION_8_4_2_CanNm_RxIndication

8.4.2 CanNm_RxIndication [SWS_CanNm_00231] Definition of callback function CanNm_RxIndication Upstream requirements: SRS_BSW_00310, SRS_BSW_00460, SRS_BSW_00484, SRS_BSW_ 00485, SRS_BSW_00459 ⌈ Service Name CanNm_RxIndication Syntax void CanNm_RxIndication ( PduIdType RxPduId, const PduInfoType* PduInfoPtr ) Service ID [hex] 0x42 Sync/Async Synchronous Reentrancy Reentrant for different PduIds. Non reentrant for the same PduId. RxPduId ID of the received PDU. Parameters (in) PduInfoPtr Contains the length (SduLength) of the received PDU, a pointer to a buffer (SduDataPtr) containing the PDU, and the MetaData related to this PDU. Parameters (inout) None Parameters (out) None Return value None Description Indication of a received PDU from a lower layer communication interface module. Available via CanNm.h ⌋ Note: The callback function CanNm_RxIndication called by the CAN Interface and implemented by the CanNm module. It is called in case of a receive indication event of the CAN Driver. [SWS_CanNm_00285] ⌈Caveats of CanNm_RxIndication: • Until this service returns the CAN Interface will not access canSduPtr. The can SduPtr is only valid and can be used by upper layers until the indication returns. CAN Interface guarantees that the number of configured bytes for this CanNmRxPduId is valid. The call context is either on interrupt level (interrupt mode) or on task level (polling mode). This callback service is re-entrant for multiple CAN controller usage. • The CanNm module is initialized correctly. ⌋