S32G M7 cannot wake up after standby

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32G M7 cannot wake up after standby

694 Views
jack_huang1
Contributor III

Dears:

       Vehicle gateway product is being designed using S32G2 solution. Currently debugging standby startup problem. The reference material (S32G_Standby_Demo_V3-20221114.pdf) has been modified for reference to the ICU MCU part, and corresponding add or modify the pull up related bugs, channelMaskLo/Hi, WBMS register configuration and so on mentioned in the document. The final result still cannot be awakened.

        Code symptom description:

1: The STB pin of S32G to PMIC has been low, and PMIC has not been reset. It can be concluded that S32G also entered hibernation within 8ms after notifying PMIC to enter hibernation.

2: IcuWkpuStandbyWakeupSupport and McuEnableSleepOnExit critical configuration have been checked, and view the code and generate corresponding changes have also been synchronization.

3: Mcu_Init,Mcu_InitClock,Platform_Init, and Icu_Init are initialized accordingly. Icu_EnableEdgeDetection is also called before sleep.

4: Add Mcu_ResetClockConfiguration to turn off the clock and finally call Mcu_SetMode to start sleep.

5: PMIC BUCK3 LDO2 also had attempts to turn on and off, LowPowerClk configured at 600KHZ (configured for other performance). According to the documentation, this section should only be related to DDR self-refresh and standby current, and should have little to do with wake up.

6: At present, only M7 core has been run, and A53 core has not been opened, so there is no action to close A core.

7: I have checked the relevant registers of WKUP through log printing. The places that need to be configured have been configured at present.

       On these basis, After initialization, Icu_EnableEdgeDetection and Icu_EnableNotification are enabled for Wkpu. Then, the corresponding hardware line trigger level changes are performed. The interrupt trigger result is correctly received in the configured interrupt callback. (This should indicate that there is no problem with the ICU interrupt configuration?)

         

Questions:

1. Based on the first point, I still judge that the function related to wake up is still a problem. The sleep function should be correctly entered, which has little to do with PMIC. Is this understanding correct?

2: Are there any other directions or ideas for investigation that can be provided?

         Thank you very much!

 

 

Labels (1)
Tags (1)
0 Kudos
3 Replies

681 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Q1 >> Based on the first point, I still judge that the function related to wake up is still a problem. The sleep function should be correctly entered, which has little to do with PMIC. Is this understanding correct?

A1 >> Even though your explanation is really thorough, we cannot say there is a problem with the function. What RTD version are you using? The one the demo uses? Which S32 Design Studio version do you have?

Q2 >> Are there any other directions or ideas for investigation that can be provided?

A2 >> Let us do more research on this regard, we assume you are using NXP platforms. Could you tell us which one are you using? Or are you using a custom board design?

Please, let us know.

0 Kudos

676 Views
jack_huang1
Contributor III

Dear  Daniel-Aguirre

          Relevant information is as follows:

          RTD uses SW32g_rtd_4.433.0.2_HF01_d2204 and S32 Design Studio uses S32DS3.5.

          The sleep demo is not a demo, but our own engineering code. The client is using the S32G-VNP-RDB2 development board.

          Can you provide the Demo program to sleep and start? 

           Thank you very much!

 

          Best Regards!

 

 

0 Kudos

655 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Thanks for your information. We do recommend using S32DS v3.4 for the current RTD, given it is not fully supported v3.5.

Have you gone through the state machine for exiting Sandby mode shown in the AN12880 [Figure 23, Page 29, AN12880 - VR5510 low-power Standby mode, Rev 3, 10/2021]?

For the steps mentioned, when grounding R151 the system is not booting, is that correct?

As if the callback routine is being executed, as you are implying, the interruption was routed correctly.

Let us continue doing research on why you are experiencing that behavior.

Just to be sure, you are following the mentioned guide as it is intended? Or have you done any modifications that we should take into account?

Please, let us know.

0 Kudos