S32G Pmic Standby

[won0020]

Hello,
I use S32G-VPN-GDLBOX3 53071 REV F with S32G_RTD_4.4_4.0.2_D2306. I am testing in the S32 Design Studio 3.5 Pmic_Configuration_Autosar_Example_S32G399A_M7.

When I try Pmic_SetMode(Pmic_Device_0, Pmic_Mode_Shutdown), PMIC_STDBY_PGOOD goes low and then PMIC_STDBY goes also low and the consumption drops to 10 mA (quite a lot, but ok). Is it possible to wake up with CAN bus WKPU configured in Port MCAL driver component? (I tried to find out in AN12952 and I think it is impossible, but I am not sure)

Furthermore, when I try Pmic_SetMode(Pmic_Device_0, Pmic_Mode_Standby), PMIC_STDBY_PGOOD goes down and then PMIC_STDBY goes also low and the current cycles around 10 mA and then 400 mA for a few seconds (power and reset LEDs are blinking). I looked at the VR5510 state machine in AN12880 and I can not figure out what could be causing this behavior.

Eventually , when I try Mcu_SetMode(Mcu_Mode_Standby), the whole application freeze and the current is still 400 mA. PMIC_STDBY_PGOOD and PMIC_STDBY are still high. Do I also need configure the EcuM or Icu MCAL driver components?

Thanks in advance for any reply.

Best regards
won0020

[alejandro_e]

Hello @won0020,

Thanks for reaching out to us. For now lets focus on the first part of your problem. You mentioned that you checked AN12952 which describes power saving techniques, for a CAN wakeup I can recommend you check S32G_Standby_Demo_V4-20221116, which describes exactly what you need:

Please do a quick review of the contents and let me know if this demo helps you with your implementation.

Thanks.

[won0020]

Hello,
According to the information in S32G_Standby_Demo, I can use Pmic_SetMode(Pmic_Device_0, Pmic_Mode_Standby) in combination with Mcu_SetMode(Mcu_Mode_Standby) and then the current consumption drops to 30mA. PMIC_STDBY_PGOOD remains high, which is strange, but PMIC_STDBY goes low.

Wake-up via CAN still doesn't work, but I'm working on it.

[alejandro_e · Accepted solution]

Hello @won0020,

The behavior you describe is unexpected as you mentioned, according to the Test section of the document you should see the following:

Have you been able to contact your FAE for the code samples mentioned in the reference materials?

Those should help you accomplish proper standby configuration. 

Also, I was able to find the original post where the document was published, it includes some more information in the attachments, M-kernel-Standby-demo-and-how-to-porting-to-Mcal/ta-p/1556313.

And for the CAN wakeup configuration, let me know if you need any help, also please let me know if you have trouble contacting your FAE.

Best regards

[won0020]

Hi,
Thanks for the attachment.
I’ll have time in about a week to look into v2-fullboot-gpio-ok and compare all the configured files in that project.
I'll let you know then.

[alejandro_e]

Hello @won0020,

I understand, please let me know if you encounter any trouble.

About the needed files, please note that the files in the post are to the complete files, they are the needed plugins and a Tresos configuration example. Please use this time you are going to work in other things to contact your FAE/NXP representative to ask for the document and code samples I mentioned earlier, since it may take some time to retrieve them.

Best regards.

[won0020]

Hello,
Based on the differences between Fig. 4 and Fig. 5 in AN13118, we have modified the example, and we are now able to enter standby mode and wake up via the CAN bus. When doing so, both PMIC_STDBY_PGOOD and PMIC_STDBY go low, and the current consumption drops from 400 mA to 190 mA — we are not able to reduce it further.

The PmicRegulatorsConfig has been updated as follows:
HVLDO: Enable Standby Mode = checked
LDO1: Enable Standby Mode = checked
LDO3: Enable Standby Mode = checked

CAN bus wake-up can also be configured as described here:
https://community.nxp.com/t5/S32G/Standby-and-Wakeup-by-RTD-on-S32G2/m-p/1522874

[alejandro_e]

Hello @won0020,

Thanks for letting me know you were able to solve your problem and thanks also for selecting one of my replies as an accepted solution. About the current consumption, since for the most part it depends on the board design, I can not give your much support. However, if you require support on that you could check the the HW design guidelines and the schematic review checklist attached with it:

Please check in particular section 4.6 and all its subsections [page 8, S32G3 Hardware Design Guidelines Rev. 3.1 — 19 January 2024]:

You could submit a private support ticket for a schematic review, however, the review we offer is only for S32G run/normal mode, since the standby depends greatly on other board components, which we do not support.

Best regards.