The issue of inconsistent versions between the MCAL version and the FLS module version in RTD4.0

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

The issue of inconsistent versions between the MCAL version and the FLS module version in RTD4.0

318 Views
gumu
Contributor IV

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!

Tags (1)
0 Kudos
7 Replies

217 Views
gumu
Contributor IV

Hi @VaneB ,

I have found an issue where the FLS module is missing in the RTD 4.0 version. I have now tried several other subversions of RTD 4.0 and have not found the FLS module in any of them.

0 Kudos

206 Views
VaneB
NXP TechSupport
NXP TechSupport

Hi @gumu 

Could you please provide more details about this situation? 

0 Kudos

183 Views
gumu
Contributor IV

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.

0 Kudos

167 Views
VaneB
NXP TechSupport
NXP TechSupport

Hi @gumu 

The Patchs of RTD version 4.0.0 compliant with AUTOSAR 4.4 are S32K3_S32M27x Real-Time Drivers AUTOSAR 4.4 Version 4.0.0 P11 and S32K3_S32M27x Real-Time Drivers Version 4.0.0 P01. 

0 Kudos

284 Views
VaneB
NXP TechSupport
NXP TechSupport

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:

VaneB_1-1716499800620.png

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

0 Kudos

264 Views
gumu
Contributor IV

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?

0 Kudos

252 Views
VaneB
NXP TechSupport
NXP TechSupport

Hi @gumu 

I am afraid that I cannot guarantee the date the next SW version will be released.

What I can suggest is to use the Automotive Software Package Manager, in these packages, it is verified that the versions work and are compatible with each other.
0 Kudos