KeyDerivation Copy parameters issue

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

KeyDerivation Copy parameters issue

Jump to solution
679 Views
kerti1
Contributor III

Hi @lukaszadrapa ,

 

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

Tags (2)
0 Kudos
Reply
1 Solution
612 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @kerti1 

This is original function from HSE Demo Examples:

lukaszadrapa_0-1748871362133.png

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:

lukaszadrapa_1-1748871454198.png

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

lukaszadrapa_2-1748871502302.png

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

View solution in original post

0 Kudos
Reply
5 Replies
634 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

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

0 Kudos
Reply
630 Views
kerti1
Contributor III

Hi @lukaszadrapa,

 

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

0 Kudos
Reply
613 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @kerti1 

This is original function from HSE Demo Examples:

lukaszadrapa_0-1748871362133.png

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:

lukaszadrapa_1-1748871454198.png

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

lukaszadrapa_2-1748871502302.png

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

0 Kudos
Reply
553 Views
kerti1
Contributor III
Thank you
0 Kudos
Reply
643 Views
kerti1
Contributor III

Hi,

 

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

 

0 Kudos
Reply