2409418_en-US

はい

S32K358 MBDT

Hi NXP
expert, I have a question. The S32K358-Q289 model is not listed in the MBDT tool. It's not included in any version packages from 1.5.0 to 1.8.0. How can I resolve this?

Chenxu1_0-1788095653895.pngChenxu1_0-1788095653895.pngChenxu1_0-1788095653895.pngChenxu1_0-1788095653895.png

Re: S32K358 MBDT

Hi, @Chenxu1,

Thank you for your interest into Model-Based Design Toolbox for S32K3.

The S32K358-Q289 device is not supported in the current S32K3 Toolbox releases. However, support for this device is planned for the upcoming S32K3 Toolbox v1.9.0 release, which is currently scheduled for the end of this year.

In the meantime, if you would like to start developing and evaluating software on the S32K358-Q289, you can use S32 Design Studio, which already provides support for this device.

Best regards,

Dragos

Re: S32K358 MBDT

Hi, @simon98,

Thank you for the clarification. What I meant by saying that the S32K358-Q289 is not yet supported is that the device is not currently available as a predefined hardware target in the MBDT Hardware Settings dropdown menu.

As a result, there is no default board/project configuration provided by MBDT for this specific hardware variant. In particular, we do not currently provide a preconfigured target with all pin mappings, clock settings, and board-specific documentation already defined.

That being said, as you have discovered, it is entirely possible to use the S32K358-Q289 with MBDT by creating a custom configuration and selecting the appropriate device package in S32 Configuration Tools.

The planned support in MBDT v1.9.0 is intended to address this by adding an official hardware target/configuration for the S32K358-Q289, making the setup process more straightforward and providing a validated default project configuration.

Hope this helps,

Dragos

Re: S32K358 MBDT

Hi @dragostoma,

Thank you for this clarification.

Could you please clarify what exactly is meant by the statement that the S32K358-Q289 is “not supported” by the current S32K3 MBDT releases?

I’m asking because I have actually been developing for a quite a lot of time using MBDT for an application that is specifically based on the S32K358-Q289. Throughout this development, I have been using MBDT successfully, including the S32 Configuration Tools (S32CT), where I select/change the appropriate device package.

So, from a practical point of view, I have been using MBDT with the S32K358-Q289 for quite some time.

Could you please explain which part of the S32K358-Q289 functionality is currently considered unsupported? For example, is the limitation related only to the device not being explicitly listed/selected in the MBDT configuration, or are there specific peripherals, drivers, code generation features, or other limitations that make the Q289 variant officially unsupported?

It would be very useful to understand the exact scope of the limitation, especially since we already have a significant amount of development based on this device and MBDT.

Best regards,
Simon