Hello,
I am migrating a project using the S32DS v3.5.12 relying on the RTD with version
Autosar Version : 4.4.0
Autosar Revision : ASR_REL_4_4_REV_0000
SW Version : 1.0.0
Build Version : S32K1_RTD_1_0_0_HF01_D2109_ASR_REL_4_4_REV_0000_20210907
to the latest one with version
Autosar Version : 4.7.0
Autosar Revision : ASR_REL_4_7_REV_0000
SW Version : 2.0.0
Build Version : S32K1_RTD_2_0_0_P04_D2404_ASR_REL_4_7_REV_0000_20240417
I was checking the ConfigTool but realized that there is no CSEc driver available, which can be seen in the images below
ConfigTools (RTD, AR v4.4.0, SW 1.0.0)
ConfigTools (RTD, AR v4.7.0, SW 2.0.0)
I have checked the folder of both RTDs and verified that the folder below that features the required header files in the include folder
is missing in the new RTD folder structure (no Crypto_... folder)
M_SCH
Solved! Go to Solution.
Hi @M_SCH,
Sometimes patched releases do not include all drivers/modules. If there are missing drivers, another package is released, and this one should be used on top of the previous one.
I recommend using RTD 2.0.0 P02 or P03 for the crypto driver, since P04's release notes do not mention any changes to the crypto driver.
Best regards,
Julián
Hi @M_SCH,
Sometimes patched releases do not include all drivers/modules. If there are missing drivers, another package is released, and this one should be used on top of the previous one.
I recommend using RTD 2.0.0 P02 or P03 for the crypto driver, since P04's release notes do not mention any changes to the crypto driver.
Best regards,
Julián
Hello @Julián_AragónM,
Thank you for your suggestion.
Since I use a MCU from the S32K1xx family I have downloaded the zip folder
and installed it offline inside the S32DS
I have installed the first two entries and then the Crypto driver appeared in the ConfigTool list and inside the RTD folder
Thanks again for your help!
Best regards,
M_SCH