Verification routine for MBDT requiring s32k344+mc33664+mc3375

[zuozuo]

I am currently using official MBDT and BMS components. Please refer to the attached image for specific version information. I am currently using the installed MATLAB demo, but I am unable to send data. My hardware is fine because I modified the code in the linkhttps://community.nxp.com/t5/S32K-Knowledge-Base/S32K344-MC33664-MC33775-RTD-3-0-0-BMS-SDK-1-0-2/ta-...  and it can receive data, but I modified the MBDT demo and it still cannot. I compared the configuration differences using compare and found that they are basically the same. Can you now provide me with a verified demo of s32k344+mc33664+mc33775? If not, a similar demo of s32k344+mc33664+mc33774 can also be used. Thank you very much!

[zuozuo]

This is Figure 6 (bcc1. jpg) mentioned earlier. Only 5 can be transferred at a time, and we couldn't fit them last time

[zuozuo]

Now that I have reanalyzed my previous problem, I will explain my discovery process:
(1) At the beginning, I used the official MBDT demo, single MC33664+single MC33775, as shown in Figure 1 (init_demo. jpg) and Figure 2 (setp_demo. jpg). Therefore, I generated code for debugging. In Figure 3 (init_debug1. jpg) and Figure 4 (init_debug4. jpg), it showed that the transmission was completed, but when it reached Figure 5 (step_debug1. jpg), it remained pending and could not receive data. So I thought it was because there were fewer initialization configuration commands, so I made program modifications.
(2) Afterwards, following the link initialization method, a command is used to fill in the data and send it out. Then, the Bms_TDInsertPhyEvent function module is added between them, as shown in Figure 6 (bcc1. jpg). However, adding it and leaving it will result in sending failure, while blocking it will allow sending it.
So I would like to learn about the use of Bms_TDInsertPhyEvent and how to use continuous data command sending. It would be best to have a useful reference demo. Thank you very much!

[mariuslucianand]

Hello @zuozuo,

The MBDT example has been develop on an older board based on the MC33664, the FRDMDUAL33664EVB and this is why the example help mentions that the boards used for development were not pin compatible, and also providing a list of the old pins connections. I understand the inconvenience of not having a ready to run application, but unfortunately there is no release planned in the future to address this setup and currently, I don't have access to the FRDMDUALK3664EVB board to develop and test the example for you.

As the pins and LPSPI configuration is described in the example help document, the delivered configuration of the S32K3x4EVB uses the LPSPI1& LPSPI4& the PTD30 as TPL enablement, the pins and SPI configurations needs to be adjusted to the one to match the FRDMDUALK3664EVB described in the Chapter 6.2.2.2 of the UM11826.

So the steps would be to open the model we have provided in the MBDT for BMS, Open the external configuration tools or EB tresos, depending on which version of the model you are using, and reconfigure the TPL12TXCLK to PTE1/LPSPI0_SCK, TPL12TXDATA to PTE2/LPSPI0_SOUT, TPL1TXCSB to PTE1/LPSPI0_SCK and TPL1_EN to PTC19, and LPSPI1_PCS1 to PTC12 followed by the configuration in the SPI MCAL component from LPSPI4 to LPSPI0. I think this shall be the configuration, please also double check it inside the UM11826 Manual.

Hope this helps,
Marius

[zuozuo]

hi,@ mariuslucianand:

I would like to know more about it now Bms_TD_InsertPhyEvent(const Bms_TDType* BmsTD,Phy_EventType TypeOfPhyEvent,uint16 Operand
）The usage of functions. When TypeOfPhyEvent is PHY_TIMER and Opera gives a delay time, is it the time to block the next command?
Now I am using it as shown in picture 1(bcc1.jpg), but it failed to send. If I follow the official demo in picture 2(init_demo1.jpg), I can send it. Do you have any usage rules? Looking forward to your answer. Thank you!