Behavior of PMIC using external Watchdog (Wdg_43_VR5510)

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

Behavior of PMIC using external Watchdog (Wdg_43_VR5510)

194 Views
SagarZala
Contributor I

I have implemented the external watchdog (Wdg_43_VR5510) for PMIC. But it is going into endless loop in Pmic_VR5XX_TimeoutLoops_StateTransistion (refer below).

SagarZala_1-1728467272425.png

Currently it is in INIT_FS state, as per the state diagram it says we need to have a good watchdog refresh to change the state from INIT_FS to Wait_ABIST2.

 

image (7).png

To Satisfy the first good watchdog refresh within 256ms, we have called watchdog trigger API after Wdg_43_VR5510_Init function during EcuM Initialization.

image (8).png

We need to know, how and where to call the first watchdog refresh. So that the state transition happens from INIT_FS to wait_ABIST2.

 

 

Tags (1)
0 Kudos
Reply
3 Replies

139 Views
SagarZala
Contributor I

Hi,

Thanks for the reply.

I am using RTD version 4.0.2. I have already configured the I2C at high speed and WD_WINDOW is also configured at 1024ms. But still its not working.

0 Kudos
Reply

125 Views
Celeste_Liu
NXP Employee
NXP Employee

Hello SagarZala,

I wonder if you have tried the two out-of-the-box examples in S32 Design Studio (S32DS)? Will they have the same problem? May be they are very good references for you.

Celeste_Liu_0-1729049570948.png

0 Kudos
Reply

165 Views
Celeste_Liu
NXP Employee
NXP Employee

Dear @SagarZala ,

Thank you for your question. VR5510 is commonly paired with the S32G microprocessor. For this, the available drivers for VR5510 should be provided under the S32G RTD packages. Which RTD version are you using and which specific example is it?

Taking the RTD 4.0.0 version as an example, you can find the documents "RTD_WDG_43_VR5510_IM" and "RTD_WDG_43_VR5510_UM" under the path C:\NXP\SW32G_RTD_4.4_4.0.0\eclipse\plugins\Wdg_43_VR5510_TS_T40D11M40I0R0\doc. The document "RTD_WDG_43_VR5510_UM" describes more detail.

It is worth mentioning that the watchdog is triggered via the I2c command and it depends on the I2c speed. When the I2c speed is low, the watchdog may not be triggered successfully within the watchdog's window open time. To avoid this problem, we recommend that the user configure I2c with high speed and use a large window period when it is enabled.

To set the watchdog refresh, you can configure the WD_WINDOW [3:0] to obtain the refresh time. As shown in the following figure:

Celeste_Liu_0-1728636341767.png

Refer to "Document VR5510 Product data sheet", page 60, Table 45. Watchdog window period configuration, as shown in the screenshot below. And after setting the correct WD period time, you need to correctly feed the WD.

Celeste_Liu_4-1728636786838.png

Celeste_Liu_5-1728636805408.png

Hope the above information is helpful to you.

Best Regards,

Celeste

0 Kudos
Reply