This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TWL6032: Watchdog not starting

Part Number: TWL6032

Hi Team,

We are unable to start the HW WD on the TWL6032, and it seems we don’t have the WD available.

Could you please advise how to enable and start it?


We have only one option to interface with the twl6032 watchdog - to read/write watchdog config register from OMAP4 console.

So, we tried to write/read different values into it. In fact, we read the same values back. But there were no other effects. 

# i2cget -f -y 1 0x48 0x2c


# i2cset -f -y 1 0x48 0x2c 0x10

# i2cget -f -y 1 0x48 0x2c


# i2cset -f -y 1 0x48 0x2c 0x00

# i2cget -f -y 1 0x48 0x2c



We also checked the DEVOFF_WDT bit. It's zero.

That means no watchdog expiration happened.

# i2cget -f -y 1 0x48 0x22


We read PHOENIX_DEV_ON just in case.

# i2cget -f -y 1 0x48 0x25


We are using the driver found here:

Please advise on what we could be missing or next steps to debug.




  • Hi Nabeel Kahn,

    Watchdog enable/disable is determined by OTP so it can’t be enabled by I2C. Also, the software interaction with battery charging whether that be hardware controlled or software controlled charging, is determined by the AUTOCHARGE bit in OTP.


  • Hi Ray,

    Can you confirm that the WD is disabled on this unit given the registers above? I don't have the full datasheet.

  • Hi Nabeel,

    The registers above do not provide any indication of watchdog being disabled. Like you stated register 0x2C (Primary_Watchdog_CFG) is used to set the primary watchdog counter. By writing 0x40 to the PHOENIX_ DEV_ON register will restart the Phoenix device and writing 0x01 starts an ACT2OFF or SLP2OFF transition. Also, like you stated the DEVOFF_WD bit will indicate whether the last reset was due to a primary watchdog expiration. You would need to know what the state of the EPROM MSK_WDT bit is to determine if the WDT is disabled or enabled.

    However, if you can read the state of the EPROM_REV register we can grasp a better understanding of whether the WDT is disabled or enabled based on the EPROM-Revision. Attempt the following in test mode:

    # i2cget -f -y 1 0x4A 0xDF