Crypto_43_CSEC naming convention not applied (CRYPTO_MIN_MAC_VERIFY_LEN_U32)

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

Crypto_43_CSEC naming convention not applied (CRYPTO_MIN_MAC_VERIFY_LEN_U32)

435 Views
M_SCH
Contributor III

Hello,

Currently I use the following setting

  • S32DS 3.5.12
  • RTD (AR: 4.7.0, SW 2.0.0): 
    • SW32K1_S32M24x_RTD_R21-11_2.0.0_P03_CD01_D2312_DS_Updatesite
    • SW32K1_S32M24x_RTD_R21-11_2.0.0_P04_D2404_DS_updatesite

and have eneabled and configured the Crypto_43_CSEC driver inside the ConfigTool menu.

When I build the application an error is thrown in the generated folder inside the project

  • RTD/src/Crypto_43_CSEC_Ipw.c at line 490

 

if( (CRYPTO_43_CSEC_MAX_MAC_VERIFY_LEN_U32 < u16MacBitLen) || (CRYPTO_43_CSEC_MIN_MAC_VERIFY_LEN_U32 > u16MacBitLen) )​

 

claiming undefined C macros (CRYPTO_43_CSEC_MAX_MAC_VERIFY_LEN_U32 , CRYPTO_43_CSEC_MIN_MAC_VERIFY_LEN_U32).

When I checked the generated header file inside the project folder

  • generate/include/Crypte_43_CSEC_Cfg.h at line 115 and 119

 

/* Minimum length of CMAC Verification */
#define CRYPTO_MIN_MAC_VERIFY_LEN_U32                   ((uint32)1)

/* Maximum length of CMAC Verification */
#define CRYPTO_MAX_MAC_VERIFY_LEN_U32                   (uint32)(128U)​

 

I found the macros but the naming convention is not applied here (should start with CRYPTO_43_CSEC_ instead of CRYPTO_ ).

When I checked the original header file inside the installed RTD folder at

  • S32DS.3.5\S32DS\software\PlatformSDK_S32K1_S32M24\RTD\Crypto_43_CSEC_TS_T40D2M20I0R0\generate_PC\include\Crypto_43_CSEC_Cfg.h

I found at line 124 and 127 the macros with the correct naming convention applied.

 

/* Minimum length of CMAC Verification */
#define CRYPTO_43_CSEC_MIN_MAC_VERIFY_LEN_U32                   ((uint32)[!"node:value(CryptoGeneral/MinimumMacVerificationLength)"!]U)

/* Maximum length of CMAC Verification */
#define CRYPTO_43_CSEC_MAX_MAC_VERIFY_LEN_U32                   (128U)

 

I have attached the files so you can check. If you need additional information let me know.

I have tried that with a second application where I added the respective driver but ended up with the same error. 

 

Best regards,

M_SCH

0 Kudos
Reply
1 Reply

408 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @M_SCH 

thanks for bringing this into our attention, I'm going to report this issue to SW team.

Regards,

Lukas

0 Kudos
Reply