2406773_en-US

[#1]

Two Issues in S32K3 RTD 7.0.1: Unpaired Parenthesis Syntax Error and Missing Crypto XML Files

I am using RTD version S32K3_RTD_7_0_1_D2602_ASR_REL_4_9_REV_0000_20260206. The runtime log reports an unpaired parenthesis error related to featureDefined(`FEATURE_MEM_INFLS_HEADER`). Two native RTD component lines have syntax errors, where the statement getFeature(`FEATURE_MEM_INFLS_HEADER`) == `S32K388` lacks a closing parenthesis.

Error Location

Both faulty lines contain the code getFeature(`FEATURE_MEM_INFLS_HEADER`) == `S32K388` and are missing a trailing closing parenthesis:

• File Path & Line 1: eclipse/mcu_data/components/PlatformSDK_S32K3/C40_Ip/C40_Ip.component Line 603
• File Path & Line 2: eclipse/mcu_data/components/PlatformSDK_S32K3/Mem_43_INFLS/Mem_43_INFLS.component Line 905

These syntax errors exist in the official original RTD component files and cause runtime feature definition parsing failures.

Second Issue: Crypto Module File Missing Error

I am using RTD version S32K3_RTD_7_0_1_D2606_ASR_REL_4_9_REV_0000_20260814 with ArchLinux and S32DS. There is a file missing issue in the Crypto module under the eclipse/mcu_data/processors directory.

Not all MCU models contain the two required Crypto configuration files: PlatformSDK_S32K3/common/sdk_features_rtd_crypto.xml and PlatformSDK_S32K3/[MCU_MODEL]_[PACKAGE_TYPE]/resource_tables/RTD_CRYPTO/rtd_crypto_Crypto.xml.

When selecting an MCU model without the above two files and adding the Crypto_43_HSE module, it triggers S32DS UI exceptions and code generation failures. Manually copying these two complete XML files from other supported MCU model directories to the target model directory can completely resolve this error.

Re: Two Issues in S32K3 RTD 7.0.1: Unpaired Parenthesis Syntax Error and Missing Crypto XML Files

Hi @chenwilsoft 

First Issue:

Thank you for pointing this out. You are correct, there is a typo in both the C40_Ip.component and Mem_43_INFLS.component files within the `FEATURE_MEM_INFLS_HEADER` section.

Using the `FEATURE_MEM_INFLS_SUPPORTBLOCK4PIPESELECT` section as a reference, it appears that an extra opening parenthesis "(" was inadvertently added before featureDefined.

As workaround, could you please either:

• Add the missing closing parenthesis ")" at the end of the expression, or
• Remove the extra opening parenthesis before featureDefined (this will make the syntax consistent with the format used elsewhere in the file)

Sorry for the inconvenience this issue may have caused.

Second Issue:

As you are using S32K3 Real-Time Drivers AUTOSAR R23-11 Version 7.0.1 QLP05, please note that this release is intended only for S32K3x4 and S32K388 devices, as stated in the software release notes.

In the image below, I highlighted the sdk_features_rtd_crypto.xml files from two different S32DS 3.6.x installations:

• Orange: S32DS instance with RTD 7.0.1 QLP05 installed.
• Purple: S32DS instance with RTD 7.0.1 P02 installed.

VaneB_0-1787259680399.pngVaneB_0-1787259680399.png

The RTD 7.0.1 P02 package supports all S32K3 derivatives, whereas RTD 7.0.1 QLP05 was specifically designed and validated for S32K3x4 and S32K388 devices.

The same applies to the rtd_crypto_Crypto.xml file. These files are not provided for all S32K3 derivatives in the 7.0.1 QLP05 release because support for those devices is outside the scope of this package.

BR, VaneB