S32K312 HSE send not response

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

S32K312 HSE send not response

4,907 次查看
Harryeta
Contributor I

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.
标记 (3)
0 项奖励
回复
4 回复数

4,537 次查看
GuanzhongWu
Contributor I

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

0 项奖励
回复

4,881 次查看
petervlna
NXP TechSupport
NXP TechSupport

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

0 项奖励
回复

4,806 次查看
MengWang1
Contributor I
Hi,petervlna
I had a similar problem. How was this problem solved?
0 项奖励
回复

4,500 次查看
ovidiubriscan
Contributor IV
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".
0 项奖励
回复