topic MCAL Integration on S32G3 M7 Bootloader – Crypto Dependency in S32G

MCAL Integration on S32G3 M7 Bootloader – Crypto Dependency

Sunilap — Wed, 10 Sep 2025 14:59:25 GMT

Hi NXP team,

MCAL integration on S32G3 M7 Bootloader BLD using the GoldVIP-S32G3-1.14.0 package.

Environment:

S32 Design Studio IDE: 3.5 – Update 13
S32G RTD: AUTOSAR 4.4, v5.0.0 - D2410
EB Tresos Studio: 27.1.0 b200625-0900
Bootloader Project: M7-BLD - GoldVIP-S32G3-1.14.0
HSE Firmware: 0.2.64.0
Host Machine: Windows 10/11 - 64-bit

Issue:
- As per Bootloader User Manual - 1.14.0 and developer guide we were able to set up the build system and import the bootloader project into EB Tresos successfully.

- The project builds correctly if we keep default settings.

- However, if we enable the Crypto module, the build throws errors related to missing HSE ECU resource definitions.

- We also tried disabling Crypto in Tresos, but the bootloader source code still has Crypto dependencies.

Clarification:
In our design, we do not require Secure Boot, so we do not want to include Crypto/HSE in the bootloader build.

Question:

Is it possible to integrate MCAL with the S32G3 M7 Bootloader without enabling Crypto?
If yes, could you please provide the correct procedure to disable it and build successfully?
Or is Crypto mandatory for the M7 Bootloader project?

What we tried:

Attempted disabling Crypto in Tresos, but encountered build errors due to source code dependencies.

Please confirm if MCAL integration requires Crypto, or provide the recommended way to build the bootloader without it.

with regards,
Sunil

Re: MCAL Integration on S32G3 M7 Bootloader – Crypto Dependency

alejandro_e — Wed, 10 Sep 2025 23:34:16 GMT

Hello @Sunilap,

Thanks for reaching out to us. Regarding your problem, please allow me some time to mimic your setup, reproduce your issue and search a solution.

Thanks in advance for your patience.

Re: MCAL Integration on S32G3 M7 Bootloader – Crypto Dependency

alejandro_e — Tue, 16 Sep 2025 02:28:21 GMT

Hello @Sunilap,

Thanks a lot for your patience, I was finally able to modify the Bootloader project so that no Crypto dependencies are needed.

Here are the changes you will need:

In the Tresos GUI:

Remove the crypto modules:

After removing the modules, you should notice the change in C:\NXP\GoldVIP-S32G3-1.14.0_no_crypto\S32G3\instances\GoldVIP\eenvs\bootloader\workspace\Bootloader_S32G3XX_ASR_4.4_M7\.prefs\pref_general.xdm.

Remove the crypto dependencies from other modules, SysDal, sCheck and Bootloader:

In the file C:\NXP\GoldVIP-S32G3-1.14.0_no_crypto\S32G3\instances\GoldVIP\eenvs\bootloader\framework\swc\bootloader\platforms\S32G3XX\build\make\files.mak, remove or comment out the crypto packages:

# Collect all CRYPTO source/include folders. ifneq ($(filter ON,$(CRYPTO_ENABLED) $(SAF_ENABLED)),) INCLUDE_DIRS += $(foreach crypto_mod,$(CRYPTO_MODULE_LIST), \ $(SRC_PATH_CRYPTO)/$(crypto_mod)_$(CRY_PKG_VERSION)$\ /include) SRC_DIRS += $(foreach crypto_mod,$(CRYPTO_MODULE_LIST), \ $(SRC_PATH_CRYPTO)/$(crypto_mod)_$(CRY_PKG_VERSION)$\ /src) endif

Please be aware that you will need to include the HSE FW directory in the configuration.bat, there are some automatic checks that will prevent your compilation if it is empty.

Again, thanks for your patience. Please let me know if you are able to achieve your objective with this information.