Dear support,
Customer Aptiv is working with S32K358
RTD version: Crypto_43_HSE_TS_T40D34M60I0R0
HSE FW version: HSE_FW_S32K358_9_2_72_0
While trying to generate a Random number after integrating Crypto RTD and flashing HSE firmware on the MCU, we are observing an issue where the firmware seems to get stuck at the Hse_Ip_ServiceRequest() function, specifically while waiting for Mu_Ip_IsResponseReady(). Please find the attached screenshot of the call stack for your reference.
Could you please help us understand:
- Possible reasons why the firmware might be stuck at this point?
- Recommended solutions or debugging steps to resolve this issue?
PS: I have configured CSM_Init, CriIf_Init and Crypto_Init in BSWM configuration
CSM, CryIf configured in Vector Davinci, Init functions of the CSM, CryIF, Crypto invoked from BSWM_Init callouts. HSE was installed using Demo APP and verified by reading version number and MU status register as shown below:
Customer has asked for working AUTOSAR example based on AUTOSAR xdm configuration CSM, CriIf and Crypto drivers (not the code from DEMOAPP). Attached their Crypto xdm file.
(so far from NXP side Sunny X and Dhan Raj were involved inot a debug call, we did not find the final root course yet ...)
Best Regards,
Viktor
Hello Cuong,
we got help and [email protected] created an example.
Let us keep this ticket open till next week when customer tried it out.
I will grant you access to the example on sharepoint.
Best Regards
Viktor
Hi @viktorfellinger
I'm creating an example for you.
Meanwhile, can you let me know that:
1. How often do you get this issue? Does it alsway happen or sporadic
2. Value of pRequest and pHseSrvDesc when call to Hse_Ip_ServiceRequest()
Could you try to increase Timeout value in pRequest to see if it can pass this issue?
Hi @viktorfellinger
Do you get any feedback?
If there's no update then I would like to close this topic.
Customer later can raise another question then you can mention again to this topic