解決済! 解決策の投稿を見る。
Hello @Silvano
Indeed, the current MBDT for S32K3 version 1.4.0 integrates the RTD 3.0.0, and provides support for the S32K396 BGA289 MCU. The future MBDT for S32K3 release, version 1.5.0, will integrate RTD 4.0.0. For being able to conduct an analysis with respect to adding support for S32K396 LQFP176, it would be useful for us to know what is the hardware that is being targeted for this design.
To provide some context, as part of offering support for a processor, or a derivative, MBDT delivers default configuration projects (EB Tresos and S32 Configuration Tools) targeting specific MCUs. The default projects contain comprehensive configurations of Pins, Clocks and Peripherals, according to the NXP evaluation boards that were available for development and testing. For example, the S32K396 BGA289 configuration, and the S32K396 example models delivered inside our toolbox, are addressing the hardware resources on the S32K396-BGA-DC evaluation board.
In case of a custom hardware design, specific on-board configurations can be created starting from the default ones (the default ones we enable are targeting only NXP hardware). Yet, we offer the possibility of customizing these configurations and use MBDT with customer specific designs - there are some steps that could be performed for updating, for example, the S32K396 BGA289 configuration project to target S32K396 LQFP176. For this, we could provide the necessary guidance on how to modify the existing settings to target specific Peripherals, Pins, and other on-board configuration settings.
Given this context, could you please let us know more details on the use case and setup that you would like to achieve, so that we could provide support in accordance to your needs?
Thank you,
Irina
Hello @Silvano
Indeed, the current MBDT for S32K3 version 1.4.0 integrates the RTD 3.0.0, and provides support for the S32K396 BGA289 MCU. The future MBDT for S32K3 release, version 1.5.0, will integrate RTD 4.0.0. For being able to conduct an analysis with respect to adding support for S32K396 LQFP176, it would be useful for us to know what is the hardware that is being targeted for this design.
To provide some context, as part of offering support for a processor, or a derivative, MBDT delivers default configuration projects (EB Tresos and S32 Configuration Tools) targeting specific MCUs. The default projects contain comprehensive configurations of Pins, Clocks and Peripherals, according to the NXP evaluation boards that were available for development and testing. For example, the S32K396 BGA289 configuration, and the S32K396 example models delivered inside our toolbox, are addressing the hardware resources on the S32K396-BGA-DC evaluation board.
In case of a custom hardware design, specific on-board configurations can be created starting from the default ones (the default ones we enable are targeting only NXP hardware). Yet, we offer the possibility of customizing these configurations and use MBDT with customer specific designs - there are some steps that could be performed for updating, for example, the S32K396 BGA289 configuration project to target S32K396 LQFP176. For this, we could provide the necessary guidance on how to modify the existing settings to target specific Peripherals, Pins, and other on-board configuration settings.
Given this context, could you please let us know more details on the use case and setup that you would like to achieve, so that we could provide support in accordance to your needs?
Thank you,
Irina