SNIP_CLASSIC_CAN_SECTION_7_6_L_PDU_reception

7.6 L-PDU reception [SWS_Can_00279] Upstream requirements: SRS_Can_01045 ⌈On L-PDU reception, the Can module shall call the RX indication callback function CanIf_RxIndication with ID, Hoh, abstract CanIf ControllerId in parameter Mailbox, and the Data Length and pointer to the L-SDU buffer in parameter PduInfoPtr.⌋ [SWS_Can_00423] ⌈In case of an Extended CAN frame, the Can module shall convert the ID to a standardized format since the Upper layer (CANIF) does not know whether the received CAN frame is a Standard CAN frame or Extended CAN frame. In case of an Extended CAN frame, MSB of a received CAN frame ID needs to be made as ’1’ to mark the received CAN frame as Extended.⌋ [SWS_Can_00396] Upstream requirements: SRS_Can_01045 ⌈The RX-interrupt service routine of the corresponding HW resource or the function Can_MainFunction_Read in case of polling mode shall call the callback function CanIf_RxIndication.⌋ [SWS_Can_00060] Upstream requirements: SRS_SPAL_12063 ⌈Data mapping by CAN to memory is defined in a way that the CAN data byte which is received first is array element 0, the CAN data byte which is received last is array element 7 or 63 in case of CAN FD. If the presentation inside the CAN Hardware buffer differs from AUTOSAR definition, the Can module must provide an adapted SDU-Buffer for the upper layers.⌋ [SWS_Can_00501] Upstream requirements: SRS_Can_01162 ⌈CanDrv shall indicate whether the received message is a conventional CAN frame or a CAN FD frame as described in Can_IdType.⌋