topic Getting started with HSE on S32K396 in S32K

Getting started with HSE on S32K396

Henrik-Wires — Tue, 17 Feb 2026 15:09:05 GMT

Trying to wrap my head around building HSE enabled applications. But how do I get started? I understand I need to
1. Enable HSE firmware installation
2. Update the SBAF?
3. install the HSE firmware

I have the S32K396-BGA-DC1 board, using the embedded debug controller.

I have the components:

HSE_FW_S32K396_0_2_50_0_D2411
HSE_DEMOAPP_S32K396_0_2_50_0_D2411
RM758227-RM00286 HSE-B Firmware Reference Manual - V2.7

However, the DEMOAPP seems to rely heavily on TRACE32 scripts, which I cannot use without a TRACE32.

Re: Getting started with HSE on S32K396

VaneB — Wed, 18 Feb 2026 16:16:33 GMT

Hi @Henrik-Wires

As an alternative to the HSE DEMO APP, there is available the S32K3 MCUs for General Purpose HSE Demo Examples. This is a port of the HSE DEMO APP, however in this case is designed to work with PEmicro and Design Studio. This provide different use-case scenarios and examples to showcase the capabilities of the HSE FW with an S32K344 device. Although it is not specifically the device you are using the HSE FW is the same so it will be a good reference and starting point.

Also, there are available some application notes and training presentations that might be useful for you to start with security in S32K3 devices. This can be access by navigating to S32K39/37/36 Microcontrollers for Electrification Applications main webpage under Documentation → Secure Files.

BR, VaneB

Re: Getting started with HSE on S32K396

Henrik-Wires — Thu, 19 Feb 2026 08:28:35 GMT

Thanks. Things are a bit clearer now after cross-referencing both examples and the reference manuals.

Still a little confused about IVT and HSE firmware. The IVT screen in the S32 Configuration Tool only seems to support QSPI flash images? Are one supposed to manually edit the boot header to build the IVT for embedded flash images? Or will it work via the configuration tool even if the screen says QSPI as the only available boot source? The DemoExamples application has from what I can tell a manually edited boot_header and link scripts, and does not seem to be using the S32 Configuration Tool at all.

Would it work to package the application with an embedded HSE firmware linked via the IVT to ensure that HSE firmware is always up to date with the main firmware. Or do the main application need to manage the HSE firmware updates? We will have sufficient space in the ~2MB app image size (AB) for both, just not 100% clear if it is OK to always include the HSE firmware in the IVT and what this means in the boot process.

And what is the recommended SBAF update process? I find conflicting information on the dependencies between SBAF and HSE firmware installations, with some sources saying that the HSE firmware should be installed before SBAF update, some saying that SBAF may need to be updated before installing the HSE image (HSE requiring a newer SBAF).

Also, what is the minimum SBAF version we can expect in S32K396 packages in new designs? Can we assume at least 0.15.0 or is there a risk that we in production may encounter chips with earlier SBAF versions?

And I assume that the newer DEMOAPP example is the proper reference for the current HSW firmware integration sources when building your own app?

Re: Getting started with HSE on S32K396

VaneB — Thu, 19 Feb 2026 16:49:27 GMT

Hi @Henrik-Wires

The IVT tool in ConfigTools does not support S32K3 devices. The IVT table content must be defined and customized manually, and the RTD does not provide a tool for configuring it.

The update process for the HSE firmware is done through an update service that must be called from the application, providing the corresponding firmware version. You can refer to the S32K344_HSE_FW_UPDATE example for guidance.

Additionally, once the HSE firmware is installed on the MCU, the memory allocated for the HSE FW remains reserved, meaning that this memory region cannot be reclaimed or used for application code.

Regarding the SBAF update process, the HSE firmware must already be installed. After that, you need to verify whether the SBAF is up to date. If it is not, you must use the service defined by the hseSbafUpdateSrv_t structure in the HSE API. For reference, please check the S32K344_SBAF_UPDATE example.

For SBAF and HSE firmware compatibility, please refer to the following table:

Finally, please note that the HSE Demo App is intended only for demonstration purposes to showcase the capabilities of the HSE firmware. Newer versions of the Demo App also include the most recent features and improvements, so the latest version will always be the best reference.