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