Hello all,
Sorry if this got already answered, but our project team is a little concerned at the moment. And I could not find anything about this on a quick look.
We recently decided for S32K3 for our project and are switching from MPC574 to S32K3 dev kits at the moment.
A colleague installed MBDT for s32k3 and reported he also had to install some autosar drivers and the EBTresos tool. From a technical view this is not a problem. But we might get into problems with our management if we have to apply for an autosar license.
Is this really needed and there is no way around this?
My own installation experience is different, but so is my MathWorks installation. I do not have Embedded Coder, and maybe this makes the difference?
Thx for any answers,
Markus
解決済! 解決策の投稿を見る。
Hi @mweiss ,
MBDT for S32K3 provides a library of blocks that allow hardware access and peripheral control by generating code on top of the RTD (Real Time Drivers) which is a software solution suitable for both AUTOSAR and non-AUTOSAR applications. The drivers are delivered within the MBDT package and there is no need to install them separately.
For configuring the peripherals, MBDT for S32K3 provides integration with external tools, specialized on such tasks and there are 2 options we provide support for: S32 Configuration Tools and EB Tresos.
S32 Configuration Tool is delivered within the MBDT package and can be used without any additional installations. On the other hand, if you would like to use EB Tresos, you would have to install it separately. You can find inside the S32K3_Examples folder applications targeting both of the available configuration tools. The selection of the used tool can be made from the Hardware Settings of any model, as illustrated below.
Please note that EB Tresos installation is not mandatory for using MBDT. S32 Configuration Tools is an already included solution which provides the same set of capabilities in terms of hardware configuration. Moreover, if you would like to build one of our simple applications configured for EB Tresos, we already provide a default configuration project, containing also the generated configuration code. Hence, you can build and test some of the applications designed for EB Tresos as well.
For more details on the tools required/delivered by MBDT for S32K3, I am attaching here a link to a thread where more details were provided - with the only note that for the latest MBDT for S32K3 release (version 1.2.0) we offer support for Matlab versions 2020a-2022a.
Hope this helps,
Irina
Hi @mweiss ,
MBDT for S32K3 provides a library of blocks that allow hardware access and peripheral control by generating code on top of the RTD (Real Time Drivers) which is a software solution suitable for both AUTOSAR and non-AUTOSAR applications. The drivers are delivered within the MBDT package and there is no need to install them separately.
For configuring the peripherals, MBDT for S32K3 provides integration with external tools, specialized on such tasks and there are 2 options we provide support for: S32 Configuration Tools and EB Tresos.
S32 Configuration Tool is delivered within the MBDT package and can be used without any additional installations. On the other hand, if you would like to use EB Tresos, you would have to install it separately. You can find inside the S32K3_Examples folder applications targeting both of the available configuration tools. The selection of the used tool can be made from the Hardware Settings of any model, as illustrated below.
Please note that EB Tresos installation is not mandatory for using MBDT. S32 Configuration Tools is an already included solution which provides the same set of capabilities in terms of hardware configuration. Moreover, if you would like to build one of our simple applications configured for EB Tresos, we already provide a default configuration project, containing also the generated configuration code. Hence, you can build and test some of the applications designed for EB Tresos as well.
For more details on the tools required/delivered by MBDT for S32K3, I am attaching here a link to a thread where more details were provided - with the only note that for the latest MBDT for S32K3 release (version 1.2.0) we offer support for Matlab versions 2020a-2022a.
Hope this helps,
Irina