2396644_en-US

是

MCAL-XDRC Configuration of S32K358 SWAP AB

Please help me answer these three questions:
1. I currently need to use the SWAP function. In the XDRC memory configuration within the RM module, do I still need to define the flash B-block: 0x800000-0xbfffff?
2. Does the flash space 0x7D4000-0x7FFFFF occupied by HSE need to be deleted from the memory configuration?
3. I define core0 as the primary core, running the OS, and core2 as the secondary core, running algorithms. Then, I allocated CM7_0, CM7_1, GMAC, uSDHC, and eDMA in Domain_Assgnment_0; and allocated CM7_2 in Domain_Assgnment_1. Is this correct? In practical applications, can the unused master core be omitted from the configuration?

Re: S32K358 SWAP AB的MCAL-XDRC配置

Hi @scott071209

1. The application or bootloader will need to: erase, program, validate and read details about the image in passive partition. That means passive partition should be also covered by XRDC.

2. In case of AB_SWAP firmware, XRDC is automatically configured during reset to protect HSE FW active flash area, HSE FW passive flash area, HSE FW data flash and HSE UTEST area. Descriptors 12-15 are used for this purpose and this configuration is locked, so it can’t be modified by user. Details can be found in HSE Firmware reference manual in section:
“14.6.3.3 Default MRC 0 configuration (AB_SWAP)”
So, you don’t need to cover HSE resources by your own XRDC configuration.

3. Yes, you can use such setup. If a master is not used, you can omit it in the configuration.
But if you use HSE, you will need to configure also domain 3 for HSE. This is not to protect HSE resources, this is to give access rights to HSE to access user data to be able to perform cryptographic operation.
S32K358 has four domain and HSE is always assigned to highest available domain. In case of S32K358, it’s domain 3. It’s hardwired, this cannot be changed. In newer version of RTD, HSE master is not even available in the list in XRDC configuration because it can’t be reconfigured. If you want to have only HSE in domain 3, you do not need to assign any master to this domain. HSE is already there automatically.
In older RTD versions, it was possible to assign HSE to other domains but such configuration had no effect. Therefore it was removed.

Regards,
Lukas