Using the Security Engine for CRC generation

[rhaas]

I am using the LS1028A processor in a new project. We need to generate/validate CRCs very quickly. I have seen that the security engine (SEC) can be used to do this.

My concern is that we will be supporting customers that require encryption to be disabled because to US export laws. The part number of the processor specifies if encryption is enabled or disabled.

Would we be able to use the SEC to generate/validate CRCs on processor's with encryption turned off?

[StarryKnight04]

It seems that the NXP community forum discusses using the Security Engine for CRC generation in the Layerscape platform, which involves secure data handling and encryption processes. Exploring the security capabilities of such systems could offer valuable insights into optimizing data integrity and verification processes, particularly in sensitive applications. If you're diving into this area, there could be a variety of best practices and implementation considerations worth exploring further.

[ran_tang · Accepted solution]

Hi Raymond,

By saying encryption enabled and disable, which of the following cases are you referring to?

1. "E" part and "non-E" part

2. "E" part with crypto acceleration disabled via register SFP_OSPR0[NSEC] bit.

For case #1, it is not possible to use SEC on a "non-E" part, as SEC is completely power gated on such parts.

For case #2, you can enable and disable SEC with OEM Security Policy Register 0 (SFP_OSPR0) for export control, if you are using "E" part.

Thanks,

Ran

[rhaas]

We are concerned with export control, so bullet 2 is the applicable scenario.

So we are able to render the part exportable and retain the CRC engine by burning a fuse. This is good news.

Which document has the register definition of SFP_OSPR0? I can't seem to find it.

Thank you

[ran_tang]

Hi Raymond,

I will share the TAUG document with you in a separate email.

Thanks,

Ran