CSEc code yields two different UID's?

gearhead1107 — Tue, 12 Jun 2018 23:15:35 GMT

I'm trying to load crypto keys into my S32 using the example project "1_Configure_part_and_Load_keys", but the "GET_UID()" function yields two different results in the example vs my project on the same part (CSE_PRAM->RAMn[11].DATA_32 is different after the operation, so this seems to be an issue with the example)

The UID generated by the example is different only in the last byte - 21120833 vs 21120865 - while the upper 3 integers are identical, as shown in the two screenshots of the debug instances.

Interestingly, the driver function "CSEC_DRV_GetID" yields something totally different than the example.. is the example just incorrect?

I have attached screenshots of

UID from the NXP example

{14, 1162432521, 909643814, 21120833}

UID from my project running NXP code

{14, 1162432521, 909643814, 21120865}

UID from the Driver function which returned "STATUS_SUCCESS"

{edit - this output is erroneous due to some pointer incompatibility - it's the same as the above in RAM}

This is a 0N57U based eval board

Re: CSEc code yields two different UID's?

gearhead1107 — Wed, 13 Jun 2018 00:10:22 GMT

It looks like the reason the example yields inconsistent results has to do with the fact "UID" is only 15 bytes.
The example pulls in a full uint32, including the lower 16th byte, while the UID is *only* those upper 15.

If someone from NXP could confirm, it would be appreciated!

Re: CSEc code yields two different UID's?

tong_zhou — Wed, 19 Dec 2018 05:37:07 GMT

in mpc5777c manual, the UID's 8 lowest significance bits are set 0.

topic Re: CSEc code yields two different UID's? in S32K

CSEc code yields two different UID's?

Re: CSEc code yields two different UID's?

Re: CSEc code yields two different UID's?