XRDC Configuration for S32K358 w/ HSE-B Enabled

[bryan-jeong]

Hello. Thanks for reading the question in advance.

Brief overview of the situation:

Currently developing on S32K358 using EB Tresos for MCAL Configurations. I installed the HSE-B firmware on-board but the Crypto functionalities such as the Random Number Generator wouldn't work (not a problem with HSE-B itself). After some debugging, I realized disabling XRDC using the T32 Lauterbach allowed the Random Number Generator to work, so I started to configure the XRDC.

2 main questions:

1. I don't understand the Xrdc_0_SIUL2_VIRTWRAPPER_PDACX_HSE_B_0 or all the other preset VIRTWRAPPERS in the RM module of EB Tresos (for XrdcPeripheralSlot). Are these predetermined sets?

2. Could you provide some guidance on how to set the XRDC so that the cores can communicate with the HSE-B core??

Thanks!

[lukaszadrapa]

Hi @bryan-jeong 

the key point is that HSE is 'hardwired' to certain domain. In case of S32K358 it is domain 3. You can find in HSE FW RM:

So, you need to configure domain 3 accordingly. It's necessary to allow access to RAM area which is used for communication with HSE.

Here is an example from my old test project for S32K344 where HSE is in domain 2. I configured full access to whole RAM for HSE. Then HSE services worked as expected.

For quick test, I used 0x0 - 0xFFFFFFFF addresses. Of course, this should be updated in the real application.

Regards,

Lukas

[bryan-jeong]

Did you end up assigning any peripherals? It says on EB that at least one must be given (error when blank)

[lukaszadrapa]

I used configuration tool in S32DS and it didn't require peripherals for the domain. And HSE then worked without that.