Dear Sir,
Our project is based on the SW32K3_S32M27x_RTD_4.4_4.0.0_P20_D2403_DS_updatesite, where the MCAL version is:
#define MCAL_VENDOR_ID 43 #define MCAL_MODULE_ID 0 #define MCAL_AR_RELEASE_MAJOR_VERSION 4 #define MCAL_AR_RELEASE_MINOR_VERSION 7 #define MCAL_AR_RELEASE_REVISION_VERSION 0 #define MCAL_SW_MAJOR_VERSION 4 #define MCAL_SW_MINOR_VERSION 0 #define MCAL_SW_PATCH_VERSION 0
The FLS module corresponds to the following Autosar version:
#define FLS_VENDOR_ID 43 #define FLS_AR_RELEASE_MAJOR_VERSION 4 #define FLS_AR_RELEASE_MINOR_VERSION 4 #define FLS_AR_RELEASE_REVISION_VERSION 0 #define FLS_SW_MAJOR_VERSION 4 #define FLS_SW_MINOR_VERSION 0 #define FLS_SW_PATCH_VERSION 0
This causes an error in version checking in the fls.h file as shown below:
#ifndef DISABLE_MCAL_INTERMODULE_ASR_CHECK /* Check if header file and Mcal.h header file are of the same Autosar version */ #if ((FLS_AR_RELEASE_MAJOR_VERSION != MCAL_AR_RELEASE_MAJOR_VERSION) || \ (FLS_AR_RELEASE_MINOR_VERSION != MCAL_AR_RELEASE_MINOR_VERSION) \ ) #error "AutoSar Version Numbers of Fls.h and Mcal.h are different" #endif /* Check if header file and OsIf.h header file are of the same Autosar version */ #if ((FLS_AR_RELEASE_MAJOR_VERSION != OSIF_AR_RELEASE_MAJOR_VERSION) || \ (FLS_AR_RELEASE_MINOR_VERSION != OSIF_AR_RELEASE_MINOR_VERSION) \ ) #error "AutoSar Version Numbers of Fls.h and OsIf.h are different" #endif #endif
I would like to ask why the FLS version inconsistency issue occurred after installing the new version of RTD4.0 and how to resolve it.
Thanks!
Hi @VaneB ,
I found information about the relationship between RTD 4.0 and FLS from another post on the forum.
no fee and fls modules in RTD of s32k3x - NXP Community
According to the description in the referenced post, if you want to continue using the FLS module, you may need to wait for an official upgrade package.
Additionally, in other subversions of RTD, such as those based on ASR R21-11, the FLS module is not included according to the AUTOSAR 4.7 standard.
Hi @gumu
Other customers have experienced the same error with different modules. According to the internal team, a quick workaround is to define DISABLE_MCAL_INTERMODULE_ASR_CHECK in project settings:
With this, the compatibility check is skipped and the project can be compiled.
This situation has been reported to the corresponding team, so we expect this to be fixed in a new SW release.
B.R.
VaneB
Hi @VaneB ,
Thank you!
I am concerned that this workaround method may skip version checks for all modules and I am not sure if it will have any potential impacts. Is there a release schedule for the new version?
Hi @gumu
I am afraid that I cannot guarantee the date the next SW version will be released.