topic Re: Crypto_43_HSE wrong configuration export in S32K

Crypto_43_HSE wrong configuration export

strofald — Tue, 29 Apr 2025 08:32:48 GMT

Hello,

I am using Crypto_43_HSE RTD driver v5.0.0.

I configured the driver in EB Tresos and then I executed the exporter to generate the .arxml file to import it into an external tool (DaVinci configurator)

However, it seems that there's something wrong in the way the generator creates the export file. More specifically, the parameter HseKeyCatalogGroupRef is defined in the exported ARXML to have upper multiplicity = lower multiplicity = 1, so it means that this parameter must be always filled in.

However there are cases in which this cannot happen.

For example, when I define the KeyElements SHE Mac Proof and SHE Cipher Proof with KeyElementId=2 and 6 respectively, I do not select the 'Use Hse Key' option because those must not be linked to an HSE key slot , and thus the HseKeyCatalogGroupRef remains empty (and gives me a warning)
So, since there's this case in which the HseKeyCatalogGroupRef can be empty, I think it's wrong for the exporter to generate the parameter with multiplicity = (1,1) essentially forcing that parameter to always be defined.
In fact, when I import the configuration through the .arxml file in the DaVinci Configurator, the tool complains about the HseKeyCatalogGroupRef parameter even though it can only be empty for the reasons I explained above.

Kind regards,

Re: Crypto_43_HSE wrong configuration export

lukaszadrapa — Mon, 05 May 2025 10:27:10 GMT

Hi @strofald

I'm sorry for delayed response.

I have asked SW team about this, I will let you know their feedback later. Thanks for patience.

Regards,

Lukas

Re: Crypto_43_HSE wrong configuration export

lukaszadrapa — Fri, 23 May 2025 05:25:01 GMT

Hi @strofald

I'm sorry for delayed response. I just received following feedback:

"The development team has confirmed that in the latest codebase, the multiplicity for HseKeyCatalogGroupRef is correctly configured to allow it to be optional. This means multiplicity valid, and allowing the field to be left empty when not applicable. "

"In crypto configuration there is no multiplicity added to HseKeyCatalogGroupRef, and tool itself is adding lower and upper multiplicity to one by default."

Regards,

Lukas

Re: Crypto_43_HSE wrong configuration export

strofald — Thu, 28 Aug 2025 11:08:04 GMT

Hello,

I can tell that the issue seems not to be solved yet.
Analyzing, for example, the file Crypto_43_HSE_s32k312_hdqfp100.epd that is bundled with the latest Crypto_43_HSE module, you can see that the parameter has upper multiplicity = lower multiplicity = 1:

The DaVinci configurator extracts its definition information from this file, and as I said I am forced to have it configured.