S32KのトピックRe: S32K312 HSE send not response

S32K312 HSE send not response

Harryeta — Tue, 13 Jun 2023 06:32:07 GMT

Hi team,

I am using S32K312 with HSE_FW_S32K3XX_0_2_6_0. I can run HSE demo app and all crypto services were done successfully.

The problem is, when i use my own code to run HSE service, HSE_Send function stuck at

HSE_MU_ReceiveResponseBlocking and when run into, i saw it is stuck at HSE_MU_IsResponseReady(u8MuInstance, u8Channel).

Can you suggest me some of reason of this problem.

Thank you so much.

Re: S32K312 HSE send not response

petervlna — Wed, 14 Jun 2023 06:07:09 GMT

Hello,

Please rise the ticket at NXP.com

https://community.nxp.com/t5/HomeTest-Knowledge-Base/How-to-submit-a-new-question-for-NXP-Support/ta...

Security sensitive questions are not discussed on public community.

Please refer to HSE_B Firmware Reference Manual chapter 3.5.1.8 Reference HSE MU driver.

Best regards,

Peter

Re: S32K312 HSE send not response

MengWang1 — Fri, 07 Jul 2023 06:27:10 GMT

Hi,petervlna
I had a similar problem. How was this problem solved?

Re: S32K312 HSE send not response

GuanzhongWu — Tue, 07 Nov 2023 14:54:00 GMT

遇到一样的问题，请问怎么解决的

Re: S32K312 HSE send not response

ovidiubriscan — Wed, 15 Nov 2023 09:12:04 GMT

You can check where is the Hse_SrvDescriptor from RTD Crypto driver located (shall be in a location where HSE has access, not in DTCM and not in SRAM cached). What i have seen is when descriptor is in DTCM HSE does not respond, when descriptor is in SRAM with cache enabled HSE has aleatory behavior (responding "service not supported", "service not allowed" etc). Solution is to have data either in "backdoor DTCM" or in "non cached SRAM".