topic Re: KeyDerivation Copy parameters issue in S32K

KeyDerivation Copy parameters issue

kerti1 — Fri, 30 May 2025 06:31:27 GMT

I used the keyderiveCopyKeyReq struct to get the key for my AES encryption. I am sure that my key catalog is correct. My keyhandle points to the Shared key that i derived using the keyderiveReq and which I stored in the RAM key handle with group index as 3. The targethandle to the new RAM catalog for the AES. After all these still i get the invalid_params. Please help me in finding out the issue

Re: KeyDerivation Copy parameters issue

kerti1 — Mon, 02 Jun 2025 07:14:54 GMT

Hi,

Could someone please let me know what is the issue. It would be really helpful.

Re: KeyDerivation Copy parameters issue

lukaszadrapa — Mon, 02 Jun 2025 10:13:52 GMT

Hi @kerti1

Could you share whole project, so I can check it on my side? I can't see a problem in the parameters.

Regards,

Lukas

Re: KeyDerivation Copy parameters issue

kerti1 — Mon, 02 Jun 2025 10:26:02 GMT

Hi @lukaszadrapa,

Thanks for the response. Please find the attached project. Thank you in advance.

Re: KeyDerivation Copy parameters issue

lukaszadrapa — Mon, 02 Jun 2025 13:46:28 GMT

Hi @kerti1

This is original function from HSE Demo Examples:

The key point - whole descriptor is erased before next use. This is not implemented in your code, so there are some leftovers from previous operations. Let's compare parameters in your original version:

... with version when the descriptor was cleared at the beginning (I did that manually in my debugger):

As you can see, I got HSE_SRV_RSP_OK when the descriptor is erased before setting of parameters. Obviously HSE could not accept those messed parameters.

Regards,

Lukas

Re: KeyDerivation Copy parameters issue

kerti1 — Tue, 03 Jun 2025 06:45:59 GMT

Thank you