Hi @po1
The attached screenshots addressing the transceiver initialization in your model, and the configuration of the polling objects used for this process seem to be correct, however, there could be multiple causes for your model not displaying the expected behavior when deployed on the MR-CANHUBK344 evaluation board.
For being able to provide a complete solution to your issue, could you please help us with some details on the following items?
1. The CAN examples delivered with the MBDT for S32K3 are set to target an S32K344-Q257 processor, while the MR-CANHUBK344 is based on S32K344-Q172. Are your model, and its associated .mex file, that you have updated with CAN4 and CAN5 configurations, set for S32K344-Q172? If not, for a correct application behavior, I would recommend you to configure your Simulink model for the S32K344-Q172 Hardware Part, by opening the Model Settings, going to Target Hardware Resources -> Hardware -> Hardware Part dropdown, as illustrated below. After doing this please make sure you press the Apply button.

Also, please note that this process will replace the configuration associated to your model with the default one we provide for S32K344-Q172 processor. So, please consider backing up the .mex file that you have already modified before this process. After that, you could enable the CAN4 and CAN5 instances inside the new configuration, targeting S32K344-Q172, by pressing the Configure button of any of the MBDT blocks.
1. For a complete guide on how to enable CAN on MR-CANHUBK344, could you please check the following article (link)? It is addressing all the steps that need to be performed in terms of the hardware configuration - Pins, Peripherals, Clocks and Interrupts.
2. For the s32k344_can_fd_receive_ebt application, could you please let us know how are you testing that the messages are correctly received by the board? If the LED is not toggling at each received message, as described in the model's readme file, the problem could be related to the configuration of the LEDs inside the .mex file. The default S32K344 configuration projects MBDT delivers were developed for a different evaluation board, so the RGBLED0_BLUE (toggled inside the CanIf_RxIndication callback) configuration may not correspond to one of the LEDs on MR-CANHUBK344. For more details on how to configure the LEDs on MR-CANHUBK344, I would like to recommend to you this article (link), describing in a detailed manner all the steps that need to be performed.
3. As an additional recommendation, I would propose to you to also try running the s32k344_can_fd_send_ebt example. You can connect a CAN Analyzer to the board and set it up with the settings corresponding to your configuration. In this way we could check if the board successfully transmits messages on the CAN bus, thus validating the hardware configuration of the peripheral.
Please let us know if these inputs help you with the issue that you are currently encountering. If you are facing any other problems, please let us know so that we could perform further investigations.
Thank you,
Irina