Hi @anagha12,
The MBDT application demonstrating how CAN messages can be received on an S32K344-Q257 processor is implemented inside the s32k3xx_can_receive_s32ct.mdl which can be found under the toolbox_root/S32K3_Examples/can folder.
Now, to provide an overview of the application, inside the Initialize subsystem, the CanController_0 and the on-board transceiver are initialized, with the following mentions:
1. The correspondence between the CanController_0 and the physical Can instance on the board can be found by pressing the Configure button of any MBDT Simulink blocks.
This action will open the configuration associated to the model, in this case an S32 Configuration Tools .mex file, which contains the settings of the peripherals, pins and clocks which will be initialized on the board. MBDT for S32K3 uses external configuration tools (S32 Configuration Tools and EB Tresos) for allowing the board configuration.
2. The model allows the selection of two different transceivers (TJA1153 or TJA1043) to be initialized by the application, selection which can be enabled by clicking one of the buttons inside the Simulink top model.
By default, the model is configured to enable TJA1153, initializing the transceiver's on-board connections for an S32K3x4EVB-Q257 evaluation board.
The model also provides the initialization settings for TJA1153 on an S32K3X4EVB-Q172 evaluation board. In order to enable that one, you would need to change the processor targeted by the application by following the steps described in the section Prepare the demo of the help file associated to this model (s32k3xx_can_receive_s32ct_example_readme.html).
In case you are using a different board, or a different transceiver, you would need to make the necessary adjustments to this implementation to ensure a correct initialization sequence.
Moving back to the top model, the execution of the CanIf_RxIndication callback is interrupt driven, the function being executed whenever a Can frame is received. The function is called inside the logic implemented by the drivers MBDT generates code on top of (MBDT blocks generate code on top of RTD - Real-Time Drivers APIs), so there is no explicit call of this function inside the application generated code. However, the implementation of this callback can be found inside the s32k3xx_can_receive_s32ct.c file.
For more information on the RTD Can API, you could check the following documents:
- <toolbox_root>\S32K3_RTD\SW32K3_RTD_4.4_R21-11_3.0.0\eclipse\plugins\Can_43_FLEXCAN_TS_T40D34M30I0R0\doc\RTD_CAN_43_FLEXCAN_UM.pdf
- https://www.autosar.org/fileadmin/standards/R21-11/CP/AUTOSAR_SWS_CANDriver.pdf
Hope this description provides a clearer overview of MBDT for S32K3 applications and of this Can model implementation.
Considering all these, could you please let us know:
- What evaluation board you are using for testing this example?
- Are you using MBDT for S32K3 v1.4.0 or a different one?
Thank you,
Irina
.png){kind=link}