did you try twl4030_wdt instead of omap_wdt?

Hi Enrico,

Last night I went searching around for a fix on the same watchdog problem Steve
was having, but this time on a BeagleBoard XM Rev. C., using the 37xx chip. 
Using the twl4030_wdt driver instead of omap_wdt driver succeeded in rebooting
the system, but with these issues:

1. When running the watchdog from a C program (e.g. using the example code from
http://embeddedfreak.wordpress.com/2010/08/23/howto-use-linux-watchdog/), the
program executable itself has been changed such that its 0 bytes after the 
reboot.

2. It's impossible to get the cause of the last power cycle via the watchdog. 
i.e. The WDIOC_GETBOOTSTATUS is handled differently in twl4030_wdt vs. 
omap_wdt, the latter of which relies on omap_prcm_get_reset_sources().

So while the twl4030_wdt driver gets me 90% there, I still need the ability to
detect a watchdog-causes reset vs. any other reset.  So, is there a patch 
coming for the omap_wdt driver for 37xx boards?

Regards,

Tony