Difference between different HSE subsystems

[joma]

Hello everyone,

I was wondering what the difference is between the HSE subsystems HSE_H, HSE_M and HSE_B?

Is the difference just in which board they run on, or are there functional differences as well?

Thank you!

[VaneB]

Hi @joma 

The HSE subsystem exists in three variants, depending on the device in which it integrates:

- HSE_H (High) is available on Flash-less S32x product variants (such as S32G2, S32G3, S32ZE, and S32R45).
- HSE_M (Medium) is available on Flash-less S32x product variants (such as S32R41, SAF85XX, and SAF86XX).
- HSE_B (Base) is available in S32x product variants with embedded Flash (such as S32K3XX, S32M27X, and MWCT2XX3A).

Unfortunately, due to security restrictions related to working with automotive components, I am unable to share further details. The HSE reference manuals are accessible only through secure files.

If you have not previously accessed secure files, please follow the guide below to request safety documentation: How to request safety documentation: Support Information

BR, VaneB

[joma]

Hi @VaneB

thank you for your quick response.
Unfortunately, this only answers the first part of my question.

However, I am also interested in whether there are functional differences or whether the functionality is identical. I don't expect a detailed answer here, but I think you are allowed to answer yes or no

Since you also mentioned Base, Medium and High, can I assume that this refers to the security rating?
In other words, if I have a project with a high security level, then I can't use an S32K3XX, but have to use an S32G2, for example?

Kind regards
joma

[VaneB · Accepted solution]

Hi @joma 

The main differences between each version lie in the host system images required to operate on Flash-less devices or devices with embedded Flash. The HSE-H&M runs on a Cortex-M7 core, while the HSE-B runs on a Cortex-M0+ core.

All versions provide the following services, divided into the following classes:

• Administration services: installation, configuration, and testing of the HSE.
• Key management services: management of different key sets handled by the HSE, for example, through cryptographic services.
• Cryptographic services: providing the application with cryptographic primitives used by high-level security stacks in the application.
• Random number services: generating random streams that can be used in various security protocols.
• Memory verification services: allowing the application to verify different memory areas during startup (after reset) and runtime.
• Monotonic counter services: providing the application with a set of monotonic counters that can only be read and incremented.

The difference between versions lies in the feature support.