S32KのトピックCSM and Crypto conflict

CSM and Crypto conflict

Kanaqw — Wed, 29 Dec 2021 09:16:06 GMT

I have a problem when executing Csm_RandomGenerate and passing resultPtr parameter as local to a main function variable, as long as it goes to func Crypto_Cse_InitRng() it changes resultPtr to OutputPtr from configuration and writes random number there, but I dont get to return anything, only somehow access this variable from config later. Is it somekind of bug or am I doing something wrong?

Re: CSM and Crypto conflict

danielmartynek — Wed, 29 Dec 2021 10:32:17 GMT

Hi @Kanaqw,

What device do you use?

Re: CSM and Crypto conflict

Kanaqw — Wed, 29 Dec 2021 10:37:13 GMT

S32K146

Re: CSM and Crypto conflict

namnguyenviet — Thu, 30 Dec 2021 06:54:52 GMT

Hello @Kanaqw,

From our Crypto driver, Crypto_Cse_InitRng() function just initializes the seed, and Crypto_Cse_GenerateRnd() is the function which generates the random vector. In Crypto layer, these functions shall be called by Crypto_ProcessJob(), with the job service as CRYPTO_RANDOMGENERATE.

As a result, Csm_RandomGenerate() shall call Crypto_ProcessJob(), pass the job service as CRYPTO_RANDOMGENERATE, in order to call Crypto_Cse_GenerateRnd(). You can check the similar behavior in your stack, if Crypto_Cse_GenerateRnd(rndPtr) can be called and rndPtr has some values, then there must be some issues with Csm or the configuration, however we don't have any information of the Csm since we don't provide it.

Best Regards,

Nam