MC33774 Cell IC compatibility with NXP MBD Simulink toolchain with S32K1xx host microcontroller

[Parab_ASW]

Hi,

I am using NXP MBD toolchain for the prototyping and development of host microcontroller board S32K146 for my BMS proto application. My battery configuration consist of 16 cells in series making 48V net battery voltage.

I am planning to use NXP's MC33774 battery cell controller IC as a AFE chip for all analog signal acquisition and cell balancing which can handle up-to 18Ch. 

In NXP MBD toolchain example code I have found BMS related examples using MC33771 as a AFE for analog signal acquisition but it handles up-to 14Ch. I was hoping could I use the same battery cell controller Simulink block-set/toolchain for the development using MC33774 IC for 16S application with my S32K146 host microcontroller.

Pls guide me on my above query, feel free to ask any additional information if required.

Thanks,

Akshay

[mariuslucianand]

Hello @Parab_ASW,

Thank you for posting your question on our Community!

Unfortunately, the short answer to your question is that currently, we do not provide Simulink blocks to handle the communication between the S32K14x and the MC33774, and it is less probably to add such support in the future.

To explain why, let me present first the context. MBDT for S32K1 generates code to address the hardware on top of the S32 SDK, and for the BCCs, on top of the BCC SDK for MC3377xB and BCC SDK for MC3377xC. This means that currently, the compatibility from a software perspective on the S32K1 is between S32K14x MC3377xB and MC3377xC using the MC33664 transceiver, and MBDT provides blocks for any of these combinations.

For the MC22775A and MC33774, NXP provides only Real-Time Drivers via the BMS SDK which is only compatible with the S32K3. So for this kind of battery cell controller, both software and reference designs are meant to work with the S32K3xx MCU. In this case, we do provide the MBDT for S32K3 and its add-on, MBDT for BMS which together provide support for the HVBMS reference designs. Currently, this combo supports S32K3xx, MC33775A, and MC33772C (used as BJB) via the MC33665 transceiver. For now, we do not provide support for the MC33774, but most likely we are taking into consideration such support in Simulink but only with the S32K3xx because the Real-Time Drivers only provide such compatibility support. 

Hope this helps,

Marius

[Parab_ASW]

Hello @mariuslucianand,

Thanks for the information well understood.

Now can you pls help me with the best suitable combination of host controller and AFE that I can use for 16S cell battery control using the NXP MBDT and S32K14x and MC3377xB / MC3377xC family.

I don't want to shift from MBD approach to bare metal coding because of rapid prototyping approach provided by MBDT and Simulink.

Pls. suggest.

Thanks,

Akshay

[mariuslucianand]

Hello @Parab_ASW ,

I am sorry for my delayed response! Do your requirements constrain you to use the S32K146 as your main controller for your application, or you could switch to the S32K344? I am asking this because you could address the 16-cell battery pack using the S32K344 in combination with the MC33774 as the main Battery Cell Controller and the MC33772C as the main Battery junction box. You could basically use the RD-HVBMSCTBUN but instead of using the MC33775 use the MC33774.

https://www.nxp.com/design/design-center/designs/hvbms-reference-design-bundle-using-etpl:RD-HVBMSCT... 

An alternative would be to use the S32K146 connected to the MC33664 as a TPL transceiver and use 2x MC33771C to control the cells and one of them to measure the current of the entire pack.

https://www.nxp.com/products/power-management/battery-management/battery-cell-controllers/14-channel...

Another alternative would be to use the S32K146 connected to the MC33664 as a TPL transceiver and use 3 x MC33772C in the same configuration as the one with the MC33771C.

For the first proposal, the MBDT for S32K3 together with the MBDT for BMS are required to be installed, but for the others you could use the MBDT fro S32K1 TBX.

Regards,

Marius

[berg0vic1]

Hello @mariuslucianand,

I wanted to clarify your statement regarding the MC33774. When you say that using it with a non-S32K3 MCU is "not recommended," do you mean it's entirely hard to implement, or just not the preferred approach?

This is important for me as I’m selecting components for my project. I know there’s existing driver code for the S32K3, but I was considering modifying it to work with the S32K144 instead. From my perspective, adapting the driver shouldn’t be too challenging, but I want to make sure I’ve considered all potential issues.

So, in summary:

1-Would you recommend using the S32K3 over the S32K1 for this application? Their features seem quite similar, but I already have an S32K1 evaluation board, so I’d prefer to use it if possible.

2-If I go with the S32K1, am I likely to face significant implementation challenges?
Looking forward to your insights. Thanks!

Best regards,